From owner-freebsd-ipfw Wed Aug 29 12:20:54 2001 Delivered-To: freebsd-ipfw@freebsd.org Received: from iguana.aciri.org (iguana.aciri.org [192.150.187.36]) by hub.freebsd.org (Postfix) with ESMTP id E571F37B403 for ; Wed, 29 Aug 2001 12:20:50 -0700 (PDT) (envelope-from rizzo@iguana.aciri.org) Received: (from rizzo@localhost) by iguana.aciri.org (8.11.3/8.11.1) id f7TJISr23873; Wed, 29 Aug 2001 12:18:28 -0700 (PDT) (envelope-from rizzo) From: Luigi Rizzo Message-Id: <200108291918.f7TJISr23873@iguana.aciri.org> Subject: Re: DUMMYNET In-Reply-To: from "Patrick O'Reilly" at "Aug 28, 2001 11:29:21 am" To: patrick@mip.co.za (Patrick O'Reilly) Date: Wed, 29 Aug 2001 12:18:28 -0700 (PDT) Cc: freebsd-ipfw@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Now I have changed cron to simply change the pipe config on the fly :"ipfw > pipe x config bw 32Kbit/s" to open it up, and :"ipfw pipe x config bw > 1bit/s" to shut it down. This way my counter values continue to > accumulate - GREAT! > > The problem is that the pipe seems to dislike the idea of running at 1 bit > per second. Obviously this is rather extreme! Any suggestions on how I as someone suggested, adding a rule in front of the pipe solves your problem more elegantly. But what is wrong with the pipe at 1 bit/s other than leaving packets go out albeit veeeeeery slooooooowly ? BTW changing HZ has no observable effect as such low speeds. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message