From owner-freebsd-net Tue Jan 2 6:57:19 2001 From owner-freebsd-net@FreeBSD.ORG Tue Jan 2 06:57:15 2001 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from popcs.cs.tin.it (unknown [194.243.155.125]) by hub.freebsd.org (Postfix) with SMTP id 1241837B402 for ; Tue, 2 Jan 2001 06:57:14 -0800 (PST) Received: (qmail 10984 invoked from network); 2 Jan 2001 14:57:20 -0000 Received: from knute-fe.cs.tin.it (HELO cs.tin.it) (212.216.172.40) by popcs.cs.tin.it with SMTP; 2 Jan 2001 14:57:20 -0000 Sender: andrea@FreeBSD.ORG Message-ID: <3A51EB1C.32140225@cs.tin.it> Date: Tue, 02 Jan 2001 15:52:12 +0100 From: Andrea Franceschini X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "C. Stephen Gunn" Cc: Garrett Wollman , Ferdinand Goldmann , "freebsd-net@FreeBSD.ORG" Subject: Re: Problems with VLAN and natd. References: <200012312258.RAA53006@tsunami.waterspout.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "C. Stephen Gunn" wrote: > > On Sun, 31 Dec 2000 15:33:36 EST, Garrett Wollman wrote: > > > Actually, no, it's not what you want (although the underlying code is > > broken enough to let it ``work'' anyway). What you want is to fix the > > parent network interface driver to indicate its readiness to receive > > 1522-octet frames by setting its if_data.ifi_hdrlen field to 18 rather > > than 14. > > Garrett is correct. My confirmation was intended to tell you it > would work, not that you're in an ideal situation. Then again, you're > applying miscellaneous patches to your ethernet drivers to get vlans > to work, so you're probably aware you're in the weeds. > > I'm not sure that the solution is simply a fix to the parent ethernet > device driver, since it's legitimate (but perhaps not advisable) > to have tagged and untagged frames on the same wire. Setting the > ifi_hdrlen for the entire physical interface seems incomplete also. > > The current VLAN (and Ethernet) implementaiton in FreeBSD needs work. > FreeBSD should should handle multiple ethernet encapsulations on > the same physical interface, and relay packets to/from some subordinate > interface. This support would factor-out the need for current > work-arounds like if_vlan, and if_ef, and perhaps even if_tap. > Let me explain. Vlan interfaces works perfectly to me. The only problem i got is related to natd between vlan. So the problem is not the MTU 'per se',but the if it is involved in someway with the problem with natd explained before. Thank you! > - Steve > > -- > C. Stephen Gunn URL: http://www.waterspout.com/ > WaterSpout Communications, Inc. Email: csg@waterspout.com > 427 North 6th Street Phone: +1 765.742.6628 > Lafayette, IN 47901 Fax: +1 765.742.0646 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message