Date: Tue, 23 Mar 1999 17:20:32 -0600 From: "Jimbo Bahooli" <griffin@blackhole.iceworld.org> To: freebsd-hackers@FreeBSD.ORG Subject: Re: NAT/SKIP/MTU Message-ID: <199903231720320920.08996462@192.168.0.99> In-Reply-To: <19990323102434.B9273@orbit.flnet.com> References: <lists.freebsd.hackers.19990322144600.A17340@orbit.flnet.com> <36F6D023.1925D6D5@vpop.net> <001301be74ce$d63efdd0$23b197ce@ezo.net> <19990323100221.D8398@orbit.flnet.com> <001301be755a$0eed6d20$23b197ce@ezo.net> <19990323102434.B9273@orbit.flnet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/23/99 at 10:24 AM Charles Henrich wrote: >On the subject of Re: NAT/SKIP/MTU, Jim Flowers stated: > >> Skip definitely alters the mtu downward that it presents for discovery= in >> order to allow for the increased size of the outbound encapsulated= packets >> without causing fragmentation. This is described in one of the white= papers >> that comes with it. Have you tried setting the mtu of the skip= interface >> down to something like 756? I had to do this for cvsup (< 1300) to work >> reliably although I didn't ascribe the problem to SKIP at the time= because >> it goes through the NAT path but it still has to go through the SKIP ACL= in >> cleartext. - might have been. This should have the effect of causing >> smaller packets to be received. > >I've completely removed skip from all interfaces and I still see the= problems >with NAT or FreeBSD when I alter the mtu.. > >-Crh I have noticed this with NAT also, if the internal and external mtu's are= not equal bad things happen to your packets. The only real solution I= have found is to keep the mtu's the same. Jimbo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199903231720320920.08996462>