From owner-freebsd-net Mon Nov 5 8:24:15 2001 Delivered-To: freebsd-net@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 6E3B737B405 for ; Mon, 5 Nov 2001 08:24:13 -0800 (PST) Received: (qmail 29710 invoked by uid 1000); 5 Nov 2001 16:23:42 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 5 Nov 2001 16:23:42 -0000 Date: Mon, 5 Nov 2001 10:23:42 -0600 (CST) From: Mike Silbersack To: Guido van Rooij Cc: Subject: Re: patch regarding icmp bandwidth limiting In-Reply-To: <20011105144330.A29038@gvr.gvr.org> Message-ID: <20011105102130.H29695-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 5 Nov 2001, Guido van Rooij wrote: > Does anyone mind the followning patch? The reason for it is that if > I ping flood localhost I get the following messages: > Limiting icmp ping response from 250 to 200 packets per second > Limiting icmp ping response from 249 to 200 packets per second > Limiting icmp ping response from 249 to 200 packets per second > Limiting icmp ping response from 249 to 200 packets per second > Limiting icmp ping response from 249 to 200 packets per second > Limiting icmp ping response from 248 to 200 packets per second > > This doesn't make much sense because it seems that the limiting is > trying to be set to 200 but somehow is stuck at 250. > > -Guido The first number is the rate at which the machine would be responding without limiting enabled. The second number tells you the rate at which it is responding. Changing from a pre to a post increment isn't going to change what you're seeing. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message