Date: Wed, 04 Dec 1996 19:56:49 +0100 From: Poul-Henning Kamp <phk@critter.tfs.com> To: Bill Fenner <fenner@parc.xerox.com> Cc: Poul-Henning Kamp <phk@freefall.freebsd.org>, CVS-committers@freefall.freebsd.org, cvs-all@freefall.freebsd.org, cvs-sys@freefall.freebsd.org Subject: Re: cvs commit: src/sys/net if_tun.h Message-ID: <4197.849725809@critter.tfs.com> In-Reply-To: Your message of "Wed, 04 Dec 1996 10:10:21 PST." <96Dec4.101026pst.177711@crevenia.parc.xerox.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <96Dec4.101026pst.177711@crevenia.parc.xerox.com>, Bill Fenner write s: >In message <199612031549.HAA23417@freefall.freebsd.org>you write: >> Branch: sys/net RELENG_2_2 >> Modified: sys/net if_tun.h > >I'm a little uncomfortable with this; merging a default-tunnel-device-MTU-chan >ge into 2.2 without any testing outside of whistle probably has more implicati >ons than we want. Notably, peoples' ppp connections are going to start out wi >th an interface MTU of 1600, where most paths on the Internet have an MTU of 1 >500. This will exercise the PMTU discovery code a lot more and is probably no >t something we want to do without testing in -current for longer. > >I'd like to change the default back to 1500, and modify if_tun.c so that it re >spects the MTU of the interface instead of using the constant. That way, appl >ications can set the MTU with TUNSIFINFO or SIOCSIFMTU and get whatever MTU th >ey want, and the default stays a conservative 1500. Sorry I misunderstood then. I thought it was the max allowed, not the default MTU. Yes, this is backing out then. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4197.849725809>