From owner-freebsd-ipfw Sun Jun 9 3:19:24 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [217.156.25.2]) by hub.freebsd.org (Postfix) with ESMTP id 66DEA37B436 for ; Sun, 9 Jun 2002 03:19:00 -0700 (PDT) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id NAA45940; Sun, 9 Jun 2002 13:18:17 +0300 (EEST) (envelope-from ady@freebsd.ady.ro) X-RAV-AntiVirus: This e-mail has been scanned for viruses on host: ady.warpnet.ro Date: Sun, 9 Jun 2002 13:18:17 +0300 (EEST) From: Adrian Penisoara X-Sender: ady@ady.warpnet.ro To: Luigi Rizzo Cc: ipfw@FreeBSD.ORG, freebsd-altq list Subject: Re: New ipfw code available In-Reply-To: <20020608201909.A41807@iguana.icir.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi, On Sat, 8 Jun 2002, Luigi Rizzo wrote: > [Bcc to -current because it is relevant there as well -- sorry for the > crosspost] > > > Hi, > over the past 2-3 weeks I have done an extensive rewrite of the > ipfw code (userland + kernel) in an attempt to make it faster and > more flexible. > > The idea (which I discussed a few times on the mailing lists) was > to replace the current ipfw rules (macroinstructions) with a set > of microinstructions, each of them performing a single operation > such as matching an address, or a port range, or a protocol flag, > etc. -- much in the spirit of BPF and derivatives -- and to let > the userland front-end compile ipfw(8) commands into an appropriate > set of microinstructions. This is very good news! I hope you will integrate the MAC address filtering feature too, it will be pretty important for our cable clients who will be able to control the ARP table. From another point of view (more specifically, the integration of ALTQ QoS framework into FreeBSD -current), cold you please think about the possibility of integrating into ipfw a classifier mechanism who will be able to "tag" the packets into specific classes, information which will be used by the ALTQ queueing disciplines to perform their QoS packet scheduling. This will probably imply the addition of a class attribute field to the struct mbuf structure -- so this will probably be a future deveopment direction for -current. However, "there is more than way to do it" (as Perl taught us), so there might be other solutions. References: [1] ALTQ webpage http://www.csl.sony.co.jp/person/kjc/kjc/software.html#ALTQ [2] ALTQ integration in FreeBSD project http://www.rofug.ro/projects/freebsd-altq/ [3] FreeBSD-ALTQ mailing list -- to subscribe send a "subscribe freebsd-altq" command to listar@rofug.ro http://www.rofug.ro/mailarchive/ Adrian Penisoara Ady (@freebsd.ady.ro) FreeBSD-ALTQ project ____________________________________________________________________ | An age is called Dark not because the light fails to shine, but | | because people refuse to see it. | | -- James Michener, "Space" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message