Date: Wed, 30 May 2012 22:26:04 +0000 From: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> To: Eugene Grosbein <egrosbein@rdtc.ru> Cc: Bruce Cran <bruce@cran.org.uk>, freebsd-net@freebsd.org Subject: Re: if_em and large mtu bug? Message-ID: <BEEA95C1-FFC4-467A-ACC9-64A420EE8D7A@lists.zabbadoz.net> In-Reply-To: <4FC6062A.3010002@rdtc.ru> References: <4FC5FA0B.5010609@cran.org.uk> <4FC6062A.3010002@rdtc.ru>
index | next in thread | previous in thread | raw e-mail
On 30. May 2012, at 11:36 , Eugene Grosbein wrote: > 30.05.2012 17:44, Bruce Cran пишет: >> Are there any known problems with if_em and jumbo packets? I've found >> that my ssh connection breaks (when running dmesg etc.) if I configure >> the mtu to 9216 via rc.conf - but if I initially use a 1500 byte mtu and >> then manually configure it to 9216 then no problems occur. >> That is due to another known bug; if you check netstat -rn and the mtu there on your routes you'll figure. if you remove your addresses/routes and re-add them after changing the mtu, you'll see it as well. >> I'm running the latest -current: the hardware is: >> >> em0: <Intel(R) PRO/1000 Network Connection 7.3.2> port 0xdc00-0xdc1f mem >> 0xfbde0000-0xfbdfffff,0xfbd00000-0xfbd7ffff,0xfbddc000-0xfbddffff irq 16 >> at device 0.0 on pci1 >> em0: Using MSIX interrupts with 3 vectors > > I confirm this with FreeBSD 8.2-STABLE/amd64, > em(4) 7.3.2, Intel PRO/1000 EB. > > There is a workaround, though: ifconfig em0 -rxcsum -txcsum mtu 9000 > work from the beginning. > > Eugene Grosbein > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" -- Bjoern A. Zeeb You have to have visions! It does not matter how good you are. It matters what good you do!home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BEEA95C1-FFC4-467A-ACC9-64A420EE8D7A>