From owner-freebsd-pf@FreeBSD.ORG Tue Nov 8 19:23:10 2005 Return-Path: X-Original-To: freebsd-pf@FreeBSD.org Delivered-To: freebsd-pf@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B9BD816A41F; Tue, 8 Nov 2005 19:23:10 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (ns1.pittgoth.com [216.38.206.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4ED2C43D48; Tue, 8 Nov 2005 19:23:10 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from localhost (ip68-105-180-11.dc.dc.cox.net [68.105.180.11]) (authenticated bits=0) by pittgoth.com (8.13.4/8.13.4) with ESMTP id jA8JbFub073162 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 8 Nov 2005 14:37:15 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Tue, 8 Nov 2005 14:22:48 -0500 From: Tom Rhodes To: Max Laier Message-Id: <20051108142248.5745d091.trhodes@FreeBSD.org> In-Reply-To: <200511081946.19860.max@love2party.net> References: <436FDC90.3020108@cuk.nu> <4370AA76.8000309@cuk.nu> <20051108171544.GI37350@green.homeunix.org> <200511081946.19860.max@love2party.net> X-Mailer: Sylpheed version 1.0.5 (GTK+ 1.2.10; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: green@FreeBSD.org, freebsd-doc@FreeBSD.org, freebsd-pf@FreeBSD.org Subject: Re: Tun and ALTQ X-BeenThere: freebsd-pf@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Technical discussion and general questions about packet filter \(pf\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Nov 2005 19:23:10 -0000 On Tue, 8 Nov 2005 19:45:59 +0100 Max Laier wrote: > 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 > packet has to go through userland (i.e. userland PPPoE). During this detour > the packet loses the ALTQ mbuf_tag and thus can no longer be stuck into the > right queue. That is why there is ALTQ support on tun(4) eventhough it > doesn't make that much sense to introduce "unnatural" queueing in the pseudo > interface. For vlan(4) there is no such problem (VLANs are handled in the > kernel all the way) so it's easy to stick the ALTQ tags on the packet and > 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? ] I'll work with Max on this. -- Tom Rhodes