From owner-freebsd-net@FreeBSD.ORG Mon Feb 14 00:57:41 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 1EE2316A4CE for ; Mon, 14 Feb 2005 00:57:41 +0000 (GMT) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.176]) by mx1.FreeBSD.org (Postfix) with ESMTP id D7EF043D55 for ; Mon, 14 Feb 2005 00:57:39 +0000 (GMT) (envelope-from max@love2party.net) Received: from [212.227.126.206] (helo=mrelayng.kundenserver.de) by moutng.kundenserver.de with esmtp (Exim 3.35 #1) id 1D0UYU-0001KH-00; Mon, 14 Feb 2005 01:57:38 +0100 Received: from [84.128.141.74] (helo=donor.laier.local) by mrelayng.kundenserver.de with asmtp (TLSv1:RC4-MD5:128) (Exim 3.35 #1) id 1D0UYU-0003Sh-00; Mon, 14 Feb 2005 01:57:38 +0100 From: Max Laier To: freebsd-net@freebsd.org Date: Mon, 14 Feb 2005 01:57:29 +0100 User-Agent: KMail/1.7.2 References: <16911.51264.86063.604597@canoe.dclg.ca> In-Reply-To: <16911.51264.86063.604597@canoe.dclg.ca> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1123904.DZRPjeplGl"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200502140157.36085.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de auth:61c499deaeeba3ba5be80f48ecc83056 cc: David Gilbert Subject: Re: altq for vlans? 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: Mon, 14 Feb 2005 00:57:41 -0000 --nextPart1123904.DZRPjeplGl Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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= =20 very little. If the physical interface supports ALTQ it is *always* better= =20 to do the queueing there. If the physical interface does not support ALTQ = it=20 must be patched. To configure queueing on physical interfaces you do the following: Suppose we have the following VLAN: vlan0: flags=3D8842 mtu 1500 inet 192.168.10.1 netmask 0xffffff00 ether [---] media: Ethernet autoselect (100baseTX ) status: active vlan: 1 parent interface: xl0 pf.conf: phy_if =3D xl0 vlan_if =3D vlan0 slow_peers =3D "{ 192.168.10.23, 192.168.10.42 }" # QUEUE on physical interface: altq on $phy_if cbq bandwidth 10Mb queue { default, limited } queue default bandwidth 75% cbq(borrow default) queue limited bandwidth 25% cbq block all # CLASSIFY on virtual interface: pass on $vlan_if from $vlan_if:network to any keep state queue default pass on $vlan_if from $slow_peers to any keep state queue limited #EOF If that does not help you, please try to explain what exactly you try to=20 achieve and why it is not possible with this method. Thanks. =2D-=20 /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News --nextPart1123904.DZRPjeplGl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCD/eAXyyEoT62BG0RAlWLAJ9adI1KH7qzA7etSeWtQUf1GKf95QCdH9Zn YhUC4f2rLOGz4nNdOSwlobc= =aOzt -----END PGP SIGNATURE----- --nextPart1123904.DZRPjeplGl--