From owner-freebsd-ipfw@FreeBSD.ORG Wed Jan 21 21:51:00 2004 Return-Path: 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 32EDD16A4CE; Wed, 21 Jan 2004 21:51:00 -0800 (PST) Received: from smtp3.adl2.internode.on.net (smtp3.adl2.internode.on.net [203.16.214.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5846643D3F; Wed, 21 Jan 2004 21:50:57 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from midget.dons.net.au (ppp37-107.lns1.adl1.internode.on.net [150.101.37.107])i0M5ooPv076655; Thu, 22 Jan 2004 16:20:51 +1030 (CST) Received: from chowder.gsoft.com.au (root@localhost.dons.net.au [127.0.0.1]) by midget.dons.net.au (8.12.9/8.12.9) with ESMTP id i0M5omnY028700; Thu, 22 Jan 2004 16:20:48 +1030 (CST) (envelope-from doconnor@gsoft.com.au) From: "Daniel O'Connor" To: Matthew Dillon Date: Thu, 22 Jan 2004 16:20:46 +1030 User-Agent: KMail/1.5.4 References: <6.0.1.1.2.20040122120552.0293bd20@202.179.0.80> <200401221512.49260.doconnor@gsoft.com.au> <200401220546.i0M5kkPf018458@apollo.backplane.com> In-Reply-To: <200401220546.i0M5kkPf018458@apollo.backplane.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401221620.46740.doconnor@gsoft.com.au> X-Spam-Score: -5 () IN_REP_TO,QUOTED_EMAIL_TEXT,REFERENCES,SIGNATURE_SHORT_DENSE,SPAM_PHRASE_00_01,USER_AGENT,USER_AGENT_KMAIL X-Scanned-By: MIMEDefang 2.26 (www . roaringpenguin . com / mimedefang) cc: freebsd-ipfw@freebsd.org cc: Ganbold cc: freebsd-hackers@freebsd.org Subject: Re: Bandwidth limiting for eMule ports X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2004 05:51:00 -0000 On Thursday 22 January 2004 16:16, Matthew Dillon wrote: > Oops... sorry, I gave bad advise. I'm looking at the code. It > recognizes 'K' or 'k' so your specification was right. It's the 'b' verses > 'B' that it's sensitive to, so if you say: kbytes/sec it will think it's > kbits/sec, and if you say kBits/sec it will think it's kBytes/sec. eww :( > One thing I have noticed, however, is that the ipfw pipes seem rather > sensitive to configuration changes, especially if there are packets > already in the pipe. I've never been able to pin it down. Yeah, I found some hangs in situations like that (which I believe are fixed now) so I turn the limits on an off by adding/removing the firewall rules rather than reconfiguring the pipes. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 9A8C 569F 685A D928 5140 AE4B 319B 41F4 5D17 FDD5