Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Dec 1996 10:10:21 PST
From:      Bill Fenner <fenner@parc.xerox.com>
To:        Poul-Henning Kamp <phk@freefall.freebsd.org>
Cc:        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:  <96Dec4.101026pst.177711@crevenia.parc.xerox.com>
In-Reply-To: Your message of "Tue, 03 Dec 1996 07:49:25 PST." <199612031549.HAA23417@freefall.freebsd.org> 

next in thread | previous in thread | raw e-mail | index | archive | help
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-change into 2.2 without any testing outside of whistle probably has more implications than we want.  Notably, peoples' ppp connections are going to start out with an interface MTU of 1600, where most paths on the Internet have an MTU of 1500.  This will exercise the PMTU discovery code a lot more and is probably not 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 respects the MTU of the interface instead of using the constant.  That way, applications can set the MTU with TUNSIFINFO or SIOCSIFMTU and get whatever MTU they want, and the default stays a conservative 1500.

  Bill





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?96Dec4.101026pst.177711>