From owner-freebsd-net@FreeBSD.ORG  Fri Dec 12 15:24:03 2014
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
Delivered-To: net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id F2D92E0B
 for <net@freebsd.org>; Fri, 12 Dec 2014 15:24:03 +0000 (UTC)
Received: from mail.lariat.net (mail.lariat.net [66.62.230.51])
 by mx1.freebsd.org (Postfix) with ESMTP id BE029823
 for <net@freebsd.org>; Fri, 12 Dec 2014 15:24:03 +0000 (UTC)
Received: from Toshi.lariat.net (IDENT:ppp1000.lariat.net@localhost
 [127.0.0.1]) by mail.lariat.net (8.9.3/8.9.3) with ESMTP id IAA03923;
 Fri, 12 Dec 2014 08:23:53 -0700 (MST)
Message-Id: <201412121523.IAA03923@mail.lariat.net>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Fri, 12 Dec 2014 08:23:24 -0700
To: Luigi Rizzo <rizzo@iet.unipi.it>
From: Brett Glass <brett@lariat.net>
Subject: Re: Can DUMMYNET handle weighting of traffic according to
 firewall rules?
In-Reply-To: <CA+hQ2+g40aZO+6JJsvDU8GG_UGp=rO1tQQoaETRe+Bc-iyBNKA@mail.g
 mail.com>
References: <201412120711.AAA00622@mail.lariat.net>
 <CA+hQ2+g40aZO+6JJsvDU8GG_UGp=rO1tQQoaETRe+Bc-iyBNKA@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: "freebsd-net@freebsd.org" <net@freebsd.org>
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Dec 2014 15:24:04 -0000

At 03:06 AM 12/12/2014, Luigi Rizzo wrote:

>you can set the limit for the pipe, create two queues with different
>weights attached to the pipe, and then schedule.
>
>ipfw pipe 12 config bw 3456 Kbit/s
>ipfw queue 34 config weight 2 pipe 12
>ipfw queue 56 config weight 1 pipe 12
>ipfw add queue 34 in recv halfduplexlink0
>ipfw add queue 56 out xmit halfduplexlink0

Alas, as I understand it (and also based on my empirical tests), 
this will give downstream traffic priority but will still let the 
same amount of upstream traffic through per second if there is no 
downstream traffic... because the capacity of the pipe is still the 
same. What I want to do is have the pipe, not the queue, weight the 
upstream traffic twice as heavily.

--Brett Glass