From owner-freebsd-ipfw@FreeBSD.ORG Fri Feb 6 12:31:03 2004 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 08F3016A4CE for ; Fri, 6 Feb 2004 12:31:03 -0800 (PST) Received: from franklin-belle.com (adsl-65-68-247-73.dsl.crchtx.swbell.net [65.68.247.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5F27543D54 for ; Fri, 6 Feb 2004 12:30:46 -0800 (PST) (envelope-from jacks@sage-american.com) Received: from sagea (sagea.sage-american [10.0.0.3]) by franklin-belle.com (8.12.8p2/8.12.8) with SMTP id i16KTu0k003668; Fri, 6 Feb 2004 14:29:57 -0600 (CST) (envelope-from jacks@sage-american.com) Message-Id: <3.0.5.32.20040206142953.01ea93b0@10.0.0.15> X-Sender: jacks@10.0.0.15 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 06 Feb 2004 14:29:53 -0600 To: "Vasenin Alexander aka BlackSir" , "Luigi Rizzo" , "Don Bowman" From: "Jack L. Stone" In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, hits=0.5 required=4.5 tests=AWL,J_CHICKENPOX_41,TW_PF autolearn=ham version=2.63-sageame.rules_v3.1 X-Spam-Checker-Version: SpamAssassin 2.63-sageame.rules_v3.1 (2004-01-11) on franklin-belle.com cc: freebsd-ipfw@freebsd.org Subject: RE: Syntax to block 38 IPs X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 Feb 2004 20:31:03 -0000 Vasenin: Thanks again! My other email crossed with this and looks like RedAlert may fix the problem themselves -- would be nice and I can forget this one. I want to get busy moving on up to IPFW2 and make use of some of the great new syntax.... At 11:10 PM 2.6.2004 +0300, Vasenin Alexander aka BlackSir wrote: >Mmmm.... of course >2. ipfw deny ip from 209.102.202.0/24 to any > ipfw deny ip from 65.194.51.0/24 to any > >or >2. ipfw deny ip from 209.102.202.0/24 to me > ipfw deny ip from 65.194.51.0/24 to me > >> > A follow-up question is that, if I do upgrade, will IPFW2 still >> use my old >> > rules until I can get around to tuning/tweaking...?? >In my case(i using ipfw rules to count traffic from our clients. small ISP >company) - everything works perfect after upgrade ipfw1->ipfw2 with the same >ruleset. > > Best regards, Jack L. Stone, Administrator Sage American http://www.sage-american.com jacks@sage-american.com