From owner-freebsd-net@FreeBSD.ORG Mon Feb 19 12:07:10 2007 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 30FFE16A408 for ; Mon, 19 Feb 2007 12:07:10 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from gaia.nimnet.asn.au (nimbin.lnk.telstra.net [139.130.45.143]) by mx1.freebsd.org (Postfix) with ESMTP id 8C6A813C471 for ; Mon, 19 Feb 2007 12:07:08 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from localhost (smithi@localhost) by gaia.nimnet.asn.au (8.8.8/8.8.8R1.5) with SMTP id WAA27901; Mon, 19 Feb 2007 22:43:02 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Mon, 19 Feb 2007 22:43:00 +1100 (EST) From: Ian Smith To: admin In-Reply-To: <45D95C07.9060409@azuni.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: freebsd-net@freebsd.org, freebsd-questions@freebsd.org, Andre Santos Subject: Re: ipfw limit src-addr woes 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, 19 Feb 2007 12:07:10 -0000 On Mon, 19 Feb 2007, admin wrote: > Andre Santos wrote: > > On 2/18/07, admin wrote: > > > >> Hi, I'm trying to use ipfw's limit clause to limit the number of > >> connections a single IP can have at the same time in a transparent > >> web-proxy environment: > >> > >> 00350 skipto 401 tcp from x.x.x.x/x,y.y.y.y/y,z.z.z.z/z to any dst-port > >> 80 in via if0 setup limit src-addr 10 > >> 00401 fwd local.ip.ad.dr,8080 tcp from x.x.x.x/x to any dst-port 80 > >> ... the rest fwd... > >> > >> as I understand the manpage, when the current number of connectiions is > >> below 10, the action "skipto" is performed, else, the packet is dropped > >> and the search terminates. But... No, a packet is not dropped on a condition that fails a skipto test. skipto number Skip all subsequent rules numbered less than number. The search continues with the first rule numbered number or higher. You'll need a specific allow or deny rule; skipto does neither, it just branches to 401 if the condition is matched, otherwise proceeds to the next rule, which is also 401. This runs rule 401 and on, either way. > >> the problem is that the src-addr limit is not enforced as some clients > >> somehow open a huge number (3-5 times the prescribed value) of > >> www-connections to some single address Out There, forcing you to bump up > >> certain sysctl variables (such as kern.ipc.nmbclusters, > >> kern.ipc.maxsockets, etc.) to mitigate the DOS effects. What might be > >> going on? Is ipfw broken, or am I misusing it? You've misread skipto, is all. As it stands, the counts will show how many packets passed the test, but all packets proceed to the next rule. I'd rephrase rules to use skipto only for branching on condition, or !condition, past specific allow and/or deny rules to deal with this. > >> OS: FreeBSD 6.2 > > > > > > The following command worked here (6.2-RC1). Only one connection was > > allowed to 1.2.3.4. > > # ipfw add 1 allow tcp from any to 1.2.3.4 22 out via rl1 limit dst-addr 1 > > > > Use the command "ipfw -d show" to see what connections are matching > > your dynamic rules. > > > > # ipfw -d show | fgrep x.x.x.x | wc -l > 20 > $ netstat -na|fgrep x.x.x.x|fgrep ESTABLISHED|wc -l > 113 > > Why is it that only 20 connections have been accounted for by ipfw's > dynamic rules but there are actually 113 active connections from that IP > at the moment? The limit src-addr is 75. See above. Sorry I didn't notice this when you first posted it. I've not yet used limit src-addr myself, but use skipto a lot :) Cheers, Ian