From owner-freebsd-net@FreeBSD.ORG Sat Jul 23 02:07:20 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org 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 C860F16A41F for ; Sat, 23 Jul 2005 02:07:20 +0000 (GMT) (envelope-from gtsang@lnxw.com) Received: from smtp.lnxw.com (smtp.lnxw.com [207.21.185.24]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8426E43D4C for ; Sat, 23 Jul 2005 02:07:20 +0000 (GMT) (envelope-from gtsang@lnxw.com) Received: from pop.lnxw.com (pop.lnxw.com [207.21.185.6]) by smtp.lnxw.com (8.13.1/8.13.1) with ESMTP id j6N27JFU018539; Fri, 22 Jul 2005 19:07:19 -0700 Received: from [207.21.185.19] (cerebrus.Lynuxworks.com [207.21.185.19]) by pop.lnxw.com (8.12.8/8.12.8) with ESMTP id j6N27IHD030467; Fri, 22 Jul 2005 19:07:18 -0700 Message-ID: <42E1A655.1080505@lynuxworks.com> Date: Fri, 22 Jul 2005 19:07:17 -0700 From: Gilbert Tsang Organization: LynuxWorks Inc. User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en To: Max Laier , freebsd-net@freebsd.org References: <16911.51264.86063.604597@canoe.dclg.ca> <200502140157.36085.max@love2party.net> In-Reply-To: <200502140157.36085.max@love2party.net> Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter 0.1 (newbast) (http://www.amavis.org/) MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Re: altq for vlans? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jul 2005 02:07:20 -0000 I believe the solution is not patching ALTQ to the VLAN driver, but rather make ALTQ recognize rules that classify according to fields in Layer 2 header (fields such as VLANid and Priority, other than just src/dst addr/port and protocol in IP header). For example, build filter rules that specify priority tracking according to the 3-bit field in the VLAN tag as per 802.1p. For example in /etc/altq.conf: interface vx0 bandwidth 100M cbq class cbq vx0 root_class NULL pbandwidth 100 class cbq vx0 vlan1_class root_class pbandwidth 80 filter vx0 cs1_class vlan1_class vlanprio 6 # priority 6 takes more bandwidth class cbq vx0 vlan2_class root_class pbandwidth 15 filter vx0 cs2_class vlan2_class vlanprio 4 # priority 4 takes less bandwidth The discussion (patch) back then is good for a FreeBSD configured as end-host, but not as a MAC bridge: [1]http://lists.freebsd.org/pipermail/freebsd-net/2005-January/006240. html Regards, Gilbert Tsang. Max Laier wrote: On Sunday 13 February 2005 22:36, David Gilbert wrote: Has anyone considered patching the vlan driver to support altq? I gather that since tun works, so should vlan. This should be a FAQ. Anyway, here is the story: While you can do ALTQ queueing on vlan interfaces the usefulness of this is very little. If the physical interface supports ALTQ it is *always* better to do the queueing there. If the physical interface does not support ALTQ it must be patched. [snipped] References 1. http://lists.freebsd.org/pipermail/freebsd-net/2005-January/006240.html