From owner-freebsd-ipfw@FreeBSD.ORG  Tue Sep 20 10:04:53 2005
Return-Path: <owner-freebsd-ipfw@FreeBSD.ORG>
X-Original-To: freebsd-ipfw@freebsd.org
Delivered-To: freebsd-ipfw@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 1665916A420
	for <freebsd-ipfw@freebsd.org>; Tue, 20 Sep 2005 10:04:53 +0000 (GMT)
	(envelope-from vladone@spaingsm.com)
Received: from mail.spaingsm.com (llwb135.servidoresdns.net [217.76.137.82])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A8DB043D46
	for <freebsd-ipfw@freebsd.org>; Tue, 20 Sep 2005 10:04:52 +0000 (GMT)
	(envelope-from vladone@spaingsm.com)
Received: from xeon.mshome.net (unknown [84.243.99.132])
	(using TLSv1 with cipher AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.spaingsm.com (Postfix) with ESMTP id 11F7624C7C6
	for <freebsd-ipfw@freebsd.org>; Tue, 20 Sep 2005 11:46:38 +0200 (CEST)
Date: Tue, 20 Sep 2005 13:04:53 +0300
From: vladone <vladone@spaingsm.com>
X-Mailer: The Bat! (v3.0.1.33) Professional
X-Priority: 3 (Normal)
Message-ID: <477488950.20050920130453@spaingsm.com>
To: freebsd-ipfw@freebsd.org
In-Reply-To: <20050919122154.GM51142@obiwan.tataz.chchile.org>
References: <97663975.20050917141303@spaingsm.com>
	<20050919122154.GM51142@obiwan.tataz.chchile.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re[2]: dummynet patch
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: vladone <vladone@spaingsm.com>
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
	<mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
	<mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Sep 2005 10:04:53 -0000

Yes, thanks! But is a little redundant and confused to pass packets to
multiple pipe and queue. Isn't more elegant to put an option on queue
that limit maximum bandwitdth to that queue (like "bw" option for pipe)?
I dont know programming (not well), but i think that, can do the job,
if is put an supplementary condition, to verify if bandwidth
allocated for that queue is less or great than an "bw" parameter.
An queue declaration like:
  ipfw queue 1 config weight 10 pipe 1 bw 128kbits/s
  ipfw queue 2 config weight 20 pipe 1 bw 256kbits/s
is more clear and efficiently.
This mean that an queue receive bandwidth according with they weight
but no more that value indicated by "bw" parameter.
Someone with experience and that know code for dummynet, can make easy
(i think) an patch for that.