From owner-freebsd-stable Wed Feb 28 11:08:05 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA02981 for stable-outgoing; Wed, 28 Feb 1996 11:08:05 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA02881 Wed, 28 Feb 1996 11:07:57 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id MAA08395; Wed, 28 Feb 1996 12:10:42 -0700 Date: Wed, 28 Feb 1996 12:10:42 -0700 From: Nate Williams Message-Id: <199602281910.MAA08395@rocky.sri.MT.net> To: Bill Fenner Cc: Nate Williams , Poul-Henning Kamp , stable@freebsd.org, current@freebsd.org Subject: Re: IPFW (was: Re: -stable hangs at boot) In-Reply-To: <96Feb28.110530pst.177480@crevenia.parc.xerox.com> References: <199602261926.MAA00360@rocky.sri.MT.net> <96Feb28.110530pst.177480@crevenia.parc.xerox.com> Sender: owner-stable@freebsd.org Precedence: bulk > >That reminds me. I haven't looked yet, but does the new code also > >filter out routing information? The old code didn't (and other firewall > >code I have used does). > > Sorry, this doesn't make much sense to me -- shouldn't "filtering routing > information" just be another firewall rule? Seems like policy to me. The routing code didn't go through the firewall code in the previous implementation, so there was no way for it to filter out routing information. Nate