On Mon, Nov 15, 1999 at 01:59:55PM -0500, spork wrote:
I noticed that ipfilter is still gone... Was there any resolution here,
or is ipfilter gone for good?
All other concerns/features aside, I find the stateful inspection stuff
much easier to setup than the ipfw filtering... I only touch
http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/ipnat/Attic/Makefile
1.2 Sun Oct 10 15:08:35 1999 UTC by peter
CVS Tags: HEAD
Diffs to 1.1
FILE REMOVED
Nuke the old antique copy of ipfilter from the tree. This is old
Well, if someone had of answered my question (to cvs-committers)
about getting an account fixed up on freefall(?) so I could use
cvs again, it might not have been forgotten about for quite so
long. Maybe I sent the question to the "wrong place", but I
received no answer to even indicate that!
In article [EMAIL PROTECTED],
Thomas Stromberg [EMAIL PROTECTED] wrote:
For why I feel ipfilter is better then ipfw (this post was written back
in December '98, ipfw may have changed greatly since):
Darren Reed writes:
Well, if someone had of answered my question (to cvs-committers)
about getting an account fixed up on freefall(?) so I could use
cvs again, it might not have been forgotten about for quite so
long. Maybe I sent the question to the "wrong place", but I
received no answer
Thomas Stromberg wrote:
It's a shame that no one seems to want to maintain ipfilter in our tree.
As far as a 'port building kld', I think this may not be the 'smartest'
way, seeing as anyone who is running a serious firewall would disable
kld's immediately anyhow.
Your concerns
I also must agree for many tasks, IP filter proves superior than IPFW and
NATD for many things which I do.
It seems much more straightforward, more configurable, and also in many
respects more stable and reliable.
It would not bother me in the least if they simply yanked ipfw and natd
from the
