Date: Fri, 14 Feb 1997 09:23:52 -0800 (PST) From: "Tom Mueller" <trm@i-planet.com> To: FreeBSD-gnats-submit@freebsd.org Subject: misc/2733: TUNMTU limits MRU in tun device even if mtu set Message-ID: <199702141723.JAA18235@i-planet.i-planet.com> Resent-Message-ID: <199702141720.JAA16835@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 2733 >Category: misc >Synopsis: TUNMTU limits MRU in tun device even if mtu set >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Feb 14 09:20:01 PST 1997 >Last-Modified: >Originator: "Tom Mueller" >Organization: i-Planet, Inc. >Release: FreeBSD 2.1-STABLE i386 >Environment: 2.1 kernel built with the tun driver (if_tun.c) >Description: The TUNMTU variable in if_tun.h is used to initialize the value of if_mtu in the tun driver and to limit the size of incoming packets in the tunwrite function. The TUNSIFINFO ioctl can be used to set the value of if_mtu to something different from TUNMTU, but TUNMTU is still used to limit the size of incoming packets. It seems that the tunwrite function should use if_mtu to limit incoming packet size rather than TUNMTU. >How-To-Repeat: This problem can be seen using the user level ppp program (iij-ppp) when the mru is set to greater than the value of TUNMTU. >Fix: Change TUNMTU to ifp->if_mtu in the tunwrite function. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702141723.JAA18235>