From owner-freebsd-net Mon Aug 7 15:32:56 2000 Delivered-To: freebsd-net@freebsd.org Received: from smtp.whitebarn.com (Spin.WhiteBarn.Com [216.0.13.113]) by hub.freebsd.org (Postfix) with ESMTP id 411EE37B8DF for ; Mon, 7 Aug 2000 15:32:52 -0700 (PDT) (envelope-from Bob@WhiteBarn.Com) Received: from WhiteBarn.Com (BarnStorm.WhiteBarn.Com [216.0.13.81]) by smtp.whitebarn.com (8.9.3/8.9.3) with ESMTP id RAA31597; Mon, 7 Aug 2000 17:32:14 -0500 (CDT) (envelope-from Bob@WhiteBarn.Com) Message-ID: <398F38ED.776E84E2@WhiteBarn.Com> Date: Mon, 07 Aug 2000 17:32:14 -0500 From: Bob Van Valzah Organization: WhiteBarn Web Works X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: freebsd-net@FreeBSD.ORG Subject: Re: VLAN MTU? 1500? 1504? Why? References: <398A3549.902A31F5@WhiteBarn.Com> <200008040434.AAA41523@whizzo.transsys.com> <398AB99C.9D5938B9@WhiteBarn.Com> <200008041446.KAA27928@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, it looks to me like some code is needed that doesn't exist. I'd be glad to help make it happen if I had a sample. Can anybody help get me started? Here's the state of the world as I understand it based on comments here and my own experimentation. Please set me straight if I'm off base. 1) A 1500-byte IPv4 MTU on an Ethernet VLAN is desirable. Things sometimes things break over VLAN interfaces that only support 1496-byte IPv4 MTUs. 2) 4.1-RELEASE contains a working vlan pseudo device driver, but only the ti driver is capable of running a 1500-byte IPv4 MTUs with it "as shipped." 3) A patch is available (http://www.euitt.upm.es/~pjlobo/fxp-mtu-patch-4.x) for the fxp driver of 4.0-RELEASE that allows a 1500-byte IPv4 MTU. However, this patch doesn't "negotiate" with the physical device--it just assumes that all physical devices can handle the larger link-layer headers. 4) It is possible (see below) for such negotiation to take place. I haven't been able to find an example of it yet. If somebody could provide me with a sample of this negotiation, I'd be happy to port it to the fxp and all the other capable cards I have around here. Bob Garrett Wollman wrote: > < said: > > > Is there any existing mechanism for "negotiation" of MTU between the > > physical layer and virtual layer? > > Yes. In FreeBSD's implementation, the network interface driver > indicates its ability to handle 802.1p-enacapsulated frames (as used > in 802.1Q) by advertising a header length of 18 rather than the > standard (no encapsulation) 14 octets. (The current implementation > does not, however, have a mechanism for rejecting 1518-byte > *unencapsulated* packets, as should officially be done. I don't think > this is a serious problem.) > > -GAWollman > > -- > Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same > wollman@lcs.mit.edu | O Siem / The fires of freedom > Opinions not those of| Dance in the burning flame > MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message