Date: Fri, 13 Jul 2007 13:08:41 -0500 From: David DeSimone <fox@verio.net> To: freebsd-net@freebsd.org Subject: Re: 6.2 mtu now limits size of incomming packet Message-ID: <20070713180840.GB8392@verio.net> In-Reply-To: <20070713130402.ed2f79ce.wmoran@collaborativefusion.com> References: <46967C5C.5040505@seclark.us> <469772DA.1000700@gmail.com> <46977741.8090301@seclark.us> <20070713093408.b8a92c23.wmoran@collaborativefusion.com> <4697A60C.4090409@seclark.us> <20070713130402.ed2f79ce.wmoran@collaborativefusion.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bill Moran <wmoran@collaborativefusion.com> wrote: > > Let's flip the question around a bit: why would you _want_ the TCP > stack to accept frames larger than the stated MTU? If I receive a 64K frame and the TCP checksum checks out, and the sequence numbers match, and it passes my firewall state, why NOT receive it? It is obviously valid, even if I cannot understand how my interface could have received it. The packet is here, so do something useful with it. I agree with others that MTU means "limit what I transmit". It does not mean "limit what someone else can transmit to me." - -- David DeSimone == Network Admin == fox@verio.net "It took me fifteen years to discover that I had no talent for writing, but I couldn't give it up because by that time I was too famous. -- Robert Benchley -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFGl7+oFSrKRjX5eCoRAg/IAKCjpErjfEMx33emhDqtNs327Hi1vQCfQnpC i+33Od/k39MaAF/1LZyxj4I= =xtlB -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070713180840.GB8392>