From owner-freebsd-net@FreeBSD.ORG Mon Nov 14 22:02:43 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9419516A420; Mon, 14 Nov 2005 22:02:43 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mail.localelinks.com (web.localelinks.com [65.170.254.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 41BB143D45; Mon, 14 Nov 2005 22:02:42 +0000 (GMT) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-157-21-134.jan.bellsouth.net [70.157.21.134]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.localelinks.com (Postfix) with ESMTP id 283232A; Mon, 14 Nov 2005 16:02:40 -0600 (CST) Received: by mortis.over-yonder.net (Postfix, from userid 100) id 348C020FFA; Mon, 14 Nov 2005 16:02:38 -0600 (CST) Date: Mon, 14 Nov 2005 16:02:37 -0600 From: "Matthew D. Fuller" To: Carlos Silva aka|Danger_Man| Message-ID: <20051114220237.GG20846@over-yonder.net> References: <4378F126.5090602@csilva.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4378F126.5090602@csilva.org> X-Editor: vi X-OS: FreeBSD User-Agent: Mutt/1.5.9i-fullermd.2 Cc: freebsd-net@freebsd.org Subject: Re: Pipe config bw... X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Nov 2005 22:02:43 -0000 [ Crossposting bcc'd; followup to -net ] On Mon, Nov 14, 2005 at 08:18:46PM +0000 I heard the voice of Carlos Silva aka |Danger_Man|, and lo! it spake thus: > > I've set "ipfw add pipe 1 ip from any to any 80;ipfw pipe 1 config > bw 2Kbyte/s" but ipfw don't limit the bw of the port 80. Yes, it does, just now how you probably want. It limits the bandwidth of all packets _DESTINED_ to port 80. Packets _FROM_ port 80 don't hit that rule, therefore don't go through the pipe. Limiting traffic TO port 80 to 2kB/s probably isn't all that useful unless people are posting some really big forms 8-} -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream.