From owner-freebsd-pf@FreeBSD.ORG Sat Oct 15 14:39:12 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 07B0016A41F; Sat, 15 Oct 2005 14:39:12 +0000 (GMT) (envelope-from max@love2party.net) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by mx1.FreeBSD.org (Postfix) with ESMTP id 635CC43D45; Sat, 15 Oct 2005 14:39:10 +0000 (GMT) (envelope-from max@love2party.net) Received: from p54A3D1B7.dip.t-dialin.net [84.163.209.183] (helo=donor.laier.local) by mrelayeu.kundenserver.de with ESMTP (Nemesis), id 0MKxQS-1EQnBl084Y-0001RS; Sat, 15 Oct 2005 16:39:09 +0200 From: Max Laier To: freebsd-pf@freebsd.org Date: Sat, 15 Oct 2005 16:39:37 +0200 User-Agent: KMail/1.8.2 References: <20051015142431.GC14542@cell.sick.ru> In-Reply-To: <20051015142431.GC14542@cell.sick.ru> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3620562.Y0OnfmycZB"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200510151639.51156.max@love2party.net> X-Provags-ID: kundenserver.de abuse@kundenserver.de login:61c499deaeeba3ba5be80f48ecc83056 Cc: Brian Fundakowski Feldman Subject: Re: ALTQ and PPP access concentrator 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: Sat, 15 Oct 2005 14:39:12 -0000 --nextPart3620562.Y0OnfmycZB Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Saturday 15 October 2005 16:24, Gleb Smirnoff wrote: > I've got two problems when running ALTQ on PPP access > concentrator. May be you have ideas on how to solve them > in a nice way. > > - When pf.conf is parsed at boot time, the p2p interfaces > (ng_iface(4) in my case) do not exist, so the ALTQ queues > are not created. The PPP software (mpd in my case) usually > starts at later stage of boot. Moreover, some programs like > ppp(8) create interfaces dynamically, not at boot time. > > - The PPP access concentrator may have a lot of interfaces. > Why isn't it possible to specify same ALTQ policy on all > interfaces of given type, like this: > > altq on ng* priq bandwidth 56Kb queue { cvsup def dns ack ssh } > > Instead, one needs to copy and paste a lot of lines differing > only in interface unit number. I agree that ALTQ configuration (esp for big setups) has some limitations a= nd=20 gotchas as is. I'd like to take the opportunity to start a discussion abou= t=20 what features are required to make it more useable. It is certainly=20 interesting to look at decoupling /dev/pf and altq configuration. The end= =20 result would be a (in-kernel) lookup service that allows pf (or any other=20 end-user of ALTQ) to lookup QIDs by interface:qname. In order to keep thin= gs=20 in sync I am thinking of a eventhandler of some kind. This would allow us to keep the inlined configuration as it happens right n= ow=20 (just a little rewriting in pfctl), but enable easy changes for interfaces= =20 coming late. mpd would just trigger necessary altq-configuration from its= =20 UP-script. I talked about this with green some time ago - CCed. =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 --nextPart3620562.Y0OnfmycZB Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQBDURS3XyyEoT62BG0RAs1mAJ9nnQDQrZuMzjo6LJ/luMhcbgUw7gCfWzLp jXAQ6etPUKNvvK3rh4GnTN4= =6Q5c -----END PGP SIGNATURE----- --nextPart3620562.Y0OnfmycZB--