Date: Thu, 31 May 2012 23:52:19 -0700 From: John-Mark Gurney <jmg@funkthat.com> To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net> Cc: freebsd-net@freebsd.org Subject: Re: if_em and large mtu bug? Message-ID: <20120601065219.GF91292@funkthat.com> In-Reply-To: <BEEA95C1-FFC4-467A-ACC9-64A420EE8D7A@lists.zabbadoz.net> References: <4FC5FA0B.5010609@cran.org.uk> <4FC6062A.3010002@rdtc.ru> <BEEA95C1-FFC4-467A-ACC9-64A420EE8D7A@lists.zabbadoz.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Bjoern A. Zeeb wrote this message on Wed, May 30, 2012 at 22:26 +0000:
> 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.
Just to comment, this isn't a bug.. it's that FreeBSD allows you to
control the mtu to a host via the routing table... Previously it would
always max out the routes MTU meaning that you could never reduce the
MTU to a problematic host, while keeping the mtu larger for others i.e.
have a mixed network w/ jumbo and normal frames...
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120601065219.GF91292>