Date: Mon, 14 Feb 2000 12:55:27 -0500 From: "C. Stephen Gunn" <csg@dustdevil.waterspout.com> To: freebsd-net@freebsd.org Cc: wollman@freebsd.org, csg@waterspout.com Subject: Re: 802.1Q VLANs Message-ID: <20000214125527.A14822@dustdevil.waterspout.com> In-Reply-To: <200002141625.LAA65769@khavrinen.lcs.mit.edu> References: <Pine.OSF.4.21.0002031711230.1338-100000@haddock.euitt.upm.es> <Pine.BSF.4.21.0002031236160.479-100000@sasami.jurai.net> <200002031847.NAA62013@khavrinen.lcs.mit.edu> <20000214002142.A12511@dustdevil.waterspout.com> <200002141625.LAA65769@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Right now untagged traffic (on a mixed link) is presented to the > > upper protocol layers by the parent device. This isn't quite > > kosher since 802.1Q states this should be routed to the "default" > > VLAN for the given interface. > > 802.1Q defines how bridges work, not how operating systems work. Your FreeBSD box is hooked to 802.1Q compliant bridge. It's still true that you could see tagged and untagged frames on the same wire. The only point of running the VLAN code (currently, note- priority support would be nice as well) is to have the lower protocol layers function as a VLAN aware bridge. They forward frames to the correct logical network interface. I believe it appropriate to make the lower protocol layers on FreeBSD comply with the specification for a bridge. This means associating a native VLAN with any trunk interface. Then, routing untagged packets to the specified VLAN interface. This approach unifies the way you should configure your bridge/switch and your FreeBSD Box. This could also force traffic to be routed through the VLAN interfaces not the physical "trunk" device. - 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000214125527.A14822>