On Fri, 31 Oct 2014 18:28:28 -0700, Freddie Cash wrote:
> On Oct 31, 2014 12:12 PM, "John-Mark Gurney" wrote:
> >
> > Can any one think of a good reason not to enable IPDIVERT sockets in
> > the ipfw module?
Yes, two. Nowadays people are just as or perhaps mo
On Oct 31, 2014 12:12 PM, "John-Mark Gurney" wrote:
>
> Can any one think of a good reason not to enable IPDIVERT sockets in
> the ipfw module?
>
> And possibly enabling default to accept? That way you don't have to
> go to the console when you load the ipfw mo
John-Mark Gurney wrote this message on Fri, Oct 31, 2014 at 12:12 -0700:
> Can any one think of a good reason not to enable IPDIVERT sockets in
> the ipfw module?
sorry, ignore this... didn't realize ipdivert was loadable as a
separate module, ipdivert...
--
John-
Can any one think of a good reason not to enable IPDIVERT sockets in
the ipfw module?
And possibly enabling default to accept? That way you don't have to
go to the console when you load the ipfw module because you forgot to
auto add the accept all rule? :)
something like:
//depot/pro
put 'options IPFIREWALL' into my
>:kernel configuration file. After installing all I try to 'kldload ipfw' which
>:complains that ipfw module is already in kernel, but kldstat reports that
>:module is being loaded! Then I've decided to kldunload it Kernel panic
On Fri, Nov 09, 2001 at 09:12:49AM +0200, Dimitar Peikov wrote:
>
> This morning I've cvsuped to STABLE and put 'options IPFIREWALL' into my
> kernel configuration file. After installing all I try to 'kldload ipfw' which
> complains that ipfw module is a
l configuration file. After installing all I try to 'kldload ipfw' which
:complains that ipfw module is already in kernel, but kldstat reports that
:module is being loaded! Then I've decided to kldunload it Kernel panic
: reboot!
:
:It is regular to kernel crash if ipfw is loa
This morning I've cvsuped to STABLE and put 'options IPFIREWALL' into my
kernel configuration file. After installing all I try to 'kldload ipfw' which
complains that ipfw module is already in kernel, but kldstat reports that
module is being loaded! Then I've deci
