From owner-freebsd-questions@FreeBSD.ORG Wed Feb 8 23:11:04 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 795E816A420 for ; Wed, 8 Feb 2006 23:11:04 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B42843D48 for ; Wed, 8 Feb 2006 23:11:03 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 6385B5D90; Wed, 8 Feb 2006 18:11:03 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 49309-09; Wed, 8 Feb 2006 18:11:02 -0500 (EST) Received: from [192.168.1.3] (pool-68-161-67-226.ny325.east.verizon.net [68.161.67.226]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 6886B5D54; Wed, 8 Feb 2006 18:11:02 -0500 (EST) Message-ID: <43EA7A89.7090501@mac.com> Date: Wed, 08 Feb 2006 18:11:05 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: Drew Tomlinson References: <43EA75C6.4010204@mykitchentable.net> In-Reply-To: <43EA75C6.4010204@mykitchentable.net> X-Enigmail-Version: 0.94.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com Cc: FreeBSD Questions Subject: Re: Best Way To Block Range of Addresses with ipfw2? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Feb 2006 23:11:04 -0000 Drew Tomlinson wrote: > I want to deny access to addresses in this range: > > 84.57.113.0 - 84.61.96.255 > > What is the best way to specify this range for ipfw2? There must be a > better way than listing a whole bunch of individual networks. deny ip from 84.56.0.0/13 to any ...comes pretty close. Use finer-grained allow rule before that if you need to pass stuff in 84.56.0.0/16, for example. -- -Chuck