From owner-freebsd-ipfw  Sun Jun  9 13:39: 7 2002
Delivered-To: freebsd-ipfw@freebsd.org
Received: from iguana.icir.org (iguana.icir.org [192.150.187.36])
	by hub.freebsd.org (Postfix) with ESMTP id 5744B37B403
	for <ipfw@FreeBSD.ORG>; Sun,  9 Jun 2002 13:39:04 -0700 (PDT)
Received: (from rizzo@localhost)
	by iguana.icir.org (8.11.6/8.11.3) id g59Kcx050144;
	Sun, 9 Jun 2002 13:38:59 -0700 (PDT)
	(envelope-from rizzo)
Date: Sun, 9 Jun 2002 13:38:59 -0700
From: Luigi Rizzo <rizzo@icir.org>
To: Adrian Penisoara <ady@freebsd.ady.ro>
Cc: ipfw@FreeBSD.ORG, freebsd-altq list <freebsd-altq@rofug.ro>
Subject: Re: New ipfw code available
Message-ID: <20020609133859.A49793@iguana.icir.org>
References: <20020608201909.A41807@iguana.icir.org> <Pine.BSF.4.10.10206091301580.44932-100000@ady.warpnet.ro>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <Pine.BSF.4.10.10206091301580.44932-100000@ady.warpnet.ro>; from ady@freebsd.ady.ro on Sun, Jun 09, 2002 at 01:18:17PM +0300
Sender: owner-freebsd-ipfw@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-ipfw.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-ipfw>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-ipfw>
X-Loop: FreeBSD.ORG

On Sun, Jun 09, 2002 at 01:18:17PM +0300, Adrian Penisoara wrote:
...
>   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

this is what ipfw already does. The "pipe" and "queue" actions,
among others, just tag a packet with an integer, which is then used
by a separate mechanism (dummynet in this case) to perform the
scheduling as appropriate.

Have a look at ip_input.c and ip_output.c on how these attributes
are handled.

It would be trivial to add additional actions, e.g. to pass classified
packets to ALTQ, assuming they are necessary at all.

	cheers
	luigi


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ipfw" in the body of the message