Date: Wed, 13 Oct 1999 08:59:02 -0700 (PDT) From: John Polstra <jdp@polstra.com> To: tstromberg@rtci.com Cc: current@freebsd.org Subject: Re: ipfilter no longer in -CURRENT, whats the direction? (off to ipfw?) Message-ID: <199910131559.IAA04379@vashon.polstra.com> In-Reply-To: <38047FB1.D7B282AD@rtci.com> References: <38047FB1.D7B282AD@rtci.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <38047FB1.D7B282AD@rtci.com>, Thomas Stromberg <tstromberg@rtci.com> wrote: > For why I feel ipfilter is better then ipfw (this post was written back > in December '98, ipfw may have changed greatly since): > > http://www.freebsd.org/cgi/getmsg.cgi?fetch=117538+122112+/usr/local/www/db/text/1998/freebsd-current/19981227.freebsd-current > (the big 'wanton atticizing discussion') > > A summary of it being: > > - Multiplatform. Runs on IRIX, Solaris, Linux. Comes shipped with > FreeBSD, OpenBSD, and NetBSD. Keeps us in sync with the other BSD's. > - Better logging then ipfw (has ipfw improved? Thats why I switched to > ipfilter in the first place) And: - IP filter does NAT completely inside the kernel - IP filter has stateful filtering I'd like to see it come back. But that means it has to be brought up to date first. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199910131559.IAA04379>