From owner-freebsd-net@FreeBSD.ORG Fri Jan 21 05:47:31 2005 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ADE5216A4CE for ; Fri, 21 Jan 2005 05:47:31 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7EE6743D49 for ; Fri, 21 Jan 2005 05:47:31 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id j0L5lXuo032345; Thu, 20 Jan 2005 21:47:33 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id j0L5lWQw032342; Thu, 20 Jan 2005 21:47:32 -0800 Date: Thu, 20 Jan 2005 21:47:32 -0800 From: Brooks Davis To: Boris Kovalenko Message-ID: <20050121054732.GA30766@odin.ac.hmc.edu> References: <41EF9495.5080601@ntmk.ru> <20050120190516.GA12156@odin.ac.hmc.edu> <41F07622.5040102@ntmk.ru> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline In-Reply-To: <41F07622.5040102@ntmk.ru> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu cc: freebsd-net@freebsd.org Subject: Re: [PATCH] 802.1p priority (fixed) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 Jan 2005 05:47:31 -0000 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Jan 21, 2005 at 08:25:22AM +0500, Boris Kovalenko wrote: > Brooks Davis wrote: > >>Because of my little BSD network infrastructure knowledge I hope that= =20 > >>guru will look at it and point me to the right way :) > > > >This lets you create vlans, but I'm not sure what the point is if > >nothing is done with the priority. Is it simply that it lets you handle > >traffic that is tagged this way and that your output packets have > >priority one on the network? I'm not sure what the intent of 802.1p > >priority is. > Yes, the outgoing packets are tagged with specified priority. Then next= =20 > device (Cisco Catalyst for example) will assign traffic to different=20 > queues according to 802.1p header information. The only thing (IMHO)=20 > that may be coded for FreeBSD is to allow PF & IPFW assign packets to=20 > ALTQ or DUMMYNET according 802.1p information. OK, that makes sense. Hmm, do we actually want to be using seperate interfaces for this? I'm sure it's very useful in some applications, but if the real point is to get packets on the wire with the priority tags, won't IPFW, PF, or maybe even the application be the best place for this tagging rather then effectivly using the source address to set it? Again, I'm not familiar with the way 802.1p is intended to work, so this may be a dumb question. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFB8Jd0XY6L6fI4GtQRAuDuAJ9qWoMgvsCxhZPWvsl8I3WCPf4AmgCcCPpU 7+xCjUk/Hm5L1ugRLfnGSmQ= =N9Ci -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw--