Date: Thu, 30 May 2002 00:44:33 -0600 From: Ian <freebsd@damnhippie.dyndns.org> To: freebsd-stable <freebsd-stable@freebsd.org> Subject: Re: Server won't boot after recompile the kernel with ipfw support Message-ID: <B91B2671.D6B3%freebsd@damnhippie.dyndns.org> In-Reply-To: <20020530052533.175243E2D@CRWdog.demon.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 05/29/02 23:25, Andy Sparrow wrote: > >> Setting firewall_type to a file name will just ensure that no rules are >> added at all, it won't match any cases in /etc/rc.firewall. > > Scanning rc.network quickly, it looks like you're correct for recent -STABLE. > > In which case the following comments in rc.firewall should be reaped, surely?: > > ############ > # Define the firewall type in /etc/rc.conf. Valid values are: > # open - will allow anyone in > # client - will try to protect just this machine > # simple - will try to protect a whole network > # closed - totally disables IP services except via lo0 interface > # UNKNOWN - disables the loading of firewall rules. > # filename - will load the rules in the given filename (full path required) > # > > > > Look at rc.firewall, the * case in the switch checks to see if the firewall_type is a file that can be read and if so it uses it. I think the comments are still valid. Certainly it still works that way for me, and I'm sync'd up with -STABLE as of about a week ago. -- Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?B91B2671.D6B3%freebsd>