From owner-freebsd-hackers@FreeBSD.ORG  Wed Jan 21 21:43:05 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id ABE7616A4CE; Wed, 21 Jan 2004 21:43:05 -0800 (PST)
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 6D6CF43D54; Wed, 21 Jan 2004 21:43:04 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: from apollo.backplane.com (localhost [127.0.0.1])
	i0M5h282018423;	Wed, 21 Jan 2004 21:43:03 -0800 (PST)
	(envelope-from dillon@apollo.backplane.com)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.12.9p2/8.12.9/Submit) id i0M5h2dv018422;
	Wed, 21 Jan 2004 21:43:02 -0800 (PST)
	(envelope-from dillon)
Date: Wed, 21 Jan 2004 21:43:02 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <200401220543.i0M5h2dv018422@apollo.backplane.com>
To: Ganbold <ganbold@micom.mng.net>
References: <6.0.1.1.2.20040122120552.0293bd20@202.179.0.80>
cc: freebsd-ipfw@freebsd.org
cc: rizzo@icir.org
cc: freebsd-hackers@freebsd.org
Subject: Re: Bandwidth limiting for eMule ports
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2004 05:43:05 -0000


:Hi,
:
:I'm still having trouble limiting bandwidth for emule ports using dummynet 
:features.
:I'm using FreeBSD 5.2-current machine for firewall. It has 2 Intel pro 100 
:cards and it is configured as a bridge.
:
:I'm doing bandwidth limiting in the following way:
:
:# eMule
:${fwcmd} pipe 59 config bw 256kbit/s
:${fwcmd} pipe 60 config bw 256kbit/s
:${fwcmd} pipe 61 config bw 128kbit/s

    The ipfw pipe command is *EXTREMELY* sensitive to case and capitalization.
    It only looks at the first few characters.

    Try 256Kbit/s instead of 256kbit/s.  See the difference?

    256kb...	-> not recognized properly
    256Kb...	-> bits per second
    256KB...	-> bytes per second.

    I've always been annoyed by that.  I think I'll go fix it in DFly.

						-Matt