Date: Fri, 06 Feb 2004 14:29:53 -0600 From: "Jack L. Stone" <jacks@sage-american.com> To: "Vasenin Alexander aka BlackSir" <blacksir@number.ru>, "Luigi Rizzo" <rizzo@icir.org>, "Don Bowman" <don@sandvine.com> Cc: freebsd-ipfw@freebsd.org Subject: RE: Syntax to block 38 IPs Message-ID: <3.0.5.32.20040206142953.01ea93b0@10.0.0.15> In-Reply-To: <NKEJKOHEKMBIMCCEHEPKKEJKCCAA.blacksir@number.ru> References: <NKEJKOHEKMBIMCCEHEPKOEJJCCAA.blacksir@number.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20040206142953.01ea93b0>