> 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?:
On Wednesday, May 29, 2002, at 12:46 PM, Ian wrote:
> Have a look at /etc/rc.firewall and see if one of the standard named
> configurations it supports is right for you. If so, set it in
> firewall_type
> in rc.conf. Otherwise use firewall_type="/etc/ipfw.conf" and put your
> own
> ruleset i
On Tue, May 28, 2002 at 02:39:03PM -0600, Jeff Jirsa wrote:
> On Tue, 28 May 2002, Irwan Hadi wrote:
>
> > Dear All,
> >
> > compiled successfully. But why after I recompile the kernel for the
> > second time, with
> > options IPFIREWALL
> > options IPFIREWALL_VERBOSE
> > options IPFIREWALL_VERB
On Tue, 28 May 2002, Irwan Hadi wrote:
> Dear All,
>
> compiled successfully. But why after I recompile the kernel for the
> second time, with
> options IPFIREWALL
> options IPFIREWALL_VERBOSE
> options IPFIREWALL_VERBOSE_LIMIT=10 according to
> http://www.freebsd.org/handbook/firewalls.html, the
Dear All,
I just upgraded one of my FreeBSD server remotely from 4.3 current to
4.6 RC1 (I cvsup-ed from the freebsd-stable tree last night). The make
buildworld, and make installworld worked just fine, and the new kernel
configuration
compiled successfully. But why after I recompile the kernel f
