From owner-freebsd-net  Mon Feb 14  8:25:52 2000
Delivered-To: freebsd-net@freebsd.org
Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193])
	by builder.freebsd.org (Postfix) with ESMTP id E23E2499F
	for <freebsd-net@freebsd.org>; Mon, 14 Feb 2000 08:25:33 -0800 (PST)
Received: (from wollman@localhost)
	by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA65769;
	Mon, 14 Feb 2000 11:25:23 -0500 (EST)
	(envelope-from wollman)
Date: Mon, 14 Feb 2000 11:25:23 -0500 (EST)
From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu>
Message-Id: <200002141625.LAA65769@khavrinen.lcs.mit.edu>
To: "C. Stephen Gunn" <csg@dustdevil.waterspout.com>
Cc: freebsd-net@freebsd.org
Subject: Re: 802.1Q VLANs
In-Reply-To: <20000214002142.A12511@dustdevil.waterspout.com>
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>
Sender: owner-freebsd-net@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

<<On Mon, 14 Feb 2000 00:21:42 -0500, "C. Stephen Gunn" <csg@dustdevil.waterspout.com> said:

> 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.

-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