From owner-freebsd-hackers  Thu Jan 16 17:43:17 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id RAA01812
          for hackers-outgoing; Thu, 16 Jan 1997 17:43:17 -0800 (PST)
Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA01789;
          Thu, 16 Jan 1997 17:43:14 -0800 (PST)
Message-Id: <199701170143.RAA01789@freefall.freebsd.org>
Received: by cheops.anu.edu.au
	(1.37.109.16/16.2) id AA054825345; Fri, 17 Jan 1997 12:42:25 +1100
From: Darren Reed <avalon@coombs.anu.edu.au>
Subject: Re: ipfw patches to test
To: brian@awfulhak.demon.co.uk (Brian Somers)
Date: Fri, 17 Jan 1997 12:42:25 +1100 (EDT)
Cc: proff@suburbia.net, phk@freebsd.org, hackers@freebsd.org
In-Reply-To: <199701162209.WAA01624@awfulhak.demon.co.uk> from "Brian Somers" at Jan 16, 97 10:09:08 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In some mail from Brian Somers, sie said:
> 
> > > 
> > > Well, I needed this badly, so I looked at it, if somebody wants to
> > > try out this little patch, please report how it goes.
> > > 
> > > Basically you can now say
> > > 
> > > 	ipfw add deny !from 192.168.23.0/30 to 140.145.230.0/24
> > > 
> > > or "!to" for that matter.  Give it a whirl...
> > > 
> > > Poul-Henning
> > 
> > This is a good addition. When I was playing with the code I was
> > quite puzzeled about the lack of this negative logic.
> 
> What's the difference between the above and
> 
> ipfw add allow from 192.168.23.0/30 to 140.145.230.0/24
> ipfw add deny from any to 140.145.230.0/24

Logically, none.

>From the technical side, more memory, longer list, etc.

Darren