From owner-freebsd-stable@FreeBSD.ORG Tue Nov 8 18:46:28 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3E3B16A41F; Tue, 8 Nov 2005 18:46:28 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id C205743D48; Tue, 8 Nov 2005 18:46:23 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3E050.dip.t-dialin.net [84.163.224.80] (helo=donor.laier.local) by mrelayeu.kundenserver.de (node=mrelayeu1) with ESMTP (Nemesis), id 0MKwpI-1EZYU91ree-0002U6; Tue, 08 Nov 2005 19:46:21 +0100 From: Max Laier To: Marko Cuk Date: Tue, 8 Nov 2005 19:45:59 +0100 User-Agent: KMail/1.8.2 References: <436FDC90.3020108@cuk.nu> <4370AA76.8000309@cuk.nu> <20051108171544.GI37350@green.homeunix.org> In-Reply-To: <20051108171544.GI37350@green.homeunix.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2460443.PiCAeWLt4t"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200511081946.19860.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 X-Mailman-Approved-At: Wed, 09 Nov 2005 05:43:30 +0000 Cc: Brian Fundakowski Feldman , freebsd-doc@freebsd.org, freebsd-pf@freebsd.org Subject: Re: Tun and ALTQ X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 18:46:29 -0000 --nextPart2460443.PiCAeWLt4t Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Tuesday 08 November 2005 18:15, Brian Fundakowski Feldman wrote: > On Tue, Nov 08, 2005 at 02:39:02PM +0100, Marko Cuk wrote: > > It seems that it work. Thanks. > > > > Damn, for vlan's ( 802.1Q) you should specify "em", for "tun", vice > > versa... what a mess, hehe. > > No prob; I don't see why using the em(4) backing the tun(4) wouldn't > work for ALTQ _IF_ you actually tagged the (PPPoE?) traffic on em(4). > I think that might be really hard, though, so for ALTQ you should > probably just specify the "logical" interface that you intend to > limit (that would be the IP tun(4) rather than the PPPoE em(4)). The problem with tun(4) in contrast to vlan(4) is that in some cases the=20 packet has to go through userland (i.e. userland PPPoE). During this detou= r=20 the packet loses the ALTQ mbuf_tag and thus can no longer be stuck into the= =20 right queue. That is why there is ALTQ support on tun(4) eventhough it=20 doesn't make that much sense to introduce "unnatural" queueing in the pseud= o=20 interface. For vlan(4) there is no such problem (VLANs are handled in the= =20 kernel all the way) so it's easy to stick the ALTQ tags on the packet and=20 queue on the hardware interface underneath. > Do you have suggestion on what would be good text to go into pf.conf(5) > so that this particular case is documented? [-> doc@, maybe somebody is interested/creative? ] =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 --nextPart2460443.PiCAeWLt4t Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDcPJ7XyyEoT62BG0RAi1GAJ9aJ9EPEA9c/7xy48qC9zcp/JRQoACeJhMP 2bPguV7gqyhXE95EWNLwp3w= =PCrd -----END PGP SIGNATURE----- --nextPart2460443.PiCAeWLt4t--