From owner-freebsd-net@FreeBSD.ORG Tue Sep 14 18:52:06 2004 Return-Path: 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 29ABF16A4CE for ; Tue, 14 Sep 2004 18:52:06 +0000 (GMT) Received: from vineyard.net (k1.vineyard.net [204.17.195.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id D5EC843D41 for ; Tue, 14 Sep 2004 18:52:05 +0000 (GMT) (envelope-from ericx_lists@vineyard.net) Received: from localhost (loopback [127.0.0.1]) by vineyard.net (Postfix) with ESMTP id 947C89160C for ; Tue, 14 Sep 2004 14:52:04 -0400 (EDT) Received: from vineyard.net ([127.0.0.1]) by localhost (king1.vineyard.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 63352-02-4 for ; Tue, 14 Sep 2004 14:52:04 -0400 (EDT) Received: from vineyard.net (cheesenip.vineyard.net [204.17.195.113]) by vineyard.net (Postfix) with ESMTP id 249F091608 for ; Tue, 14 Sep 2004 14:52:04 -0400 (EDT) Message-ID: <41473DD3.7030007@vineyard.net> Date: Tue, 14 Sep 2004 14:52:03 -0400 From: "Eric W. Bates" User-Agent: Mozilla Thunderbird 0.5 (X11/20040208) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-king1 at Vineyard.NET Subject: To many dynamic rules created by infected machine X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2004 18:52:06 -0000 Friends run an IT business and I helped build them a firewall using ipfw. The box has multiple interfaces; one of which is untrusted and it is where they put suspect machines (customer boxes with high likelihood of viruses and other evil Windoze ailments). Their network is well protected; however there is now an inadvertent DOS when a particularly virulent machine performs a sweep attack on some block of IP, because we have a check-state/keep-state. Sep 11 16:00:01 hostname /kernel: ipfw: install_state: Too many dynamic rules Is there a way to limit the number of rules a given host can create in x number of minutes? Thanks for your time. -- Eric W. Bates