Date: Tue, 28 Jan 1997 11:27:43 -0600 From: Hal Snyder <hal@vailsys.com> To: hackers@freebsd.org Cc: pete@sms.fi Subject: best mtu for lo0? Message-ID: <32EE370F.7CDD@vailsys.com>
next in thread | raw e-mail | index | archive | help
While searching FreeBSD archived mail items, I found that Petri Helenius <pete@sms.fi> wrote: > What's your lo0 MTU? If it's the 16384 that some > non-tcp-knowledgeable person put in sometime in the past > I think what you are seeing is called "TCP deadlock" which appears when > window size is equal or smaller than the MTU. This makes TCP to be > stop-and-go protocol (remember XMODEM? or non-windowing kermit) and thus > the troughput of the protocol is pretty horrible. This happens on ATM also > if you are running with 4096 or 8192 window sizes and the RFC1577 default > MTU of 9180. > Fortunately not too many applications use the 127.0.0.1 address but use > the loopback provided by the ethernet-interface. (and thus get the MTU of > 1500) Is this correct? I notice 2.1.6-R sets MTU for lo0 to 16384. Should this be reduced to 1500? Will it affect performance of aliased IP addresses, for which a static route through lo0 is usually specified?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32EE370F.7CDD>