From owner-freebsd-net Wed Feb 3 13:22:28 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24553 for freebsd-net-outgoing; Wed, 3 Feb 1999 13:22:28 -0800 (PST) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24547 for ; Wed, 3 Feb 1999 13:22:26 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id PAA13561; Wed, 3 Feb 1999 15:38:12 -0500 (EST) (envelope-from wollman) Date: Wed, 3 Feb 1999 15:38:12 -0500 (EST) From: Garrett Wollman Message-Id: <199902032038.PAA13561@khavrinen.lcs.mit.edu> To: Julian Elischer Cc: net@FreeBSD.ORG Subject: Re: Patch to add Netgraph to all ethernet interfaces. In-Reply-To: <36B8A870.52BFA1D7@whistle.com> References: <895942.3127040484@d206.promo.de> <36B8A870.52BFA1D7@whistle.com> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > What do these do? I've seen soem VLAN code in the kernel.. what is it? > and ToS (Type of Service?).. what does it require? Nothing -- just stick on the right header and go. (Of course, that won't do you much good unless you have fancy queueing going on to make sure that your priority packets actually get out the door...) The if_vlan driver implements precisely this for 1Q (and 1p would use the same encapsulation header, just setting different bits). I chose this implementation approach because it was easier than introducing the (IMHO preferable) notion of subinterfaces everywhere. -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