I believe it's harmless, and while not aesthetically pleasing, it's a necessary
work-around. The stop command to rc.d/ipfilter uses -D to disable ipfilter, so
it's necessary to use -E with the start command because there's no way to know
how/when/why/in-what-environment it's being called. If
Hello there,
I recently ran into a slight issue with ipfilter running on
5.1-RELEASE. My machine serves the simple purpose as a nat gateway, so
ipfilter is always going to be necessary on it. Due to this fact, i
decided to include options IPFILTER in the kernel config, instead of
On 16 Jun 2003 21:35:44 -0400
Mike Bohan [EMAIL PROTECTED] wrote:
Hello there,
I recently ran into a slight issue with ipfilter running on
5.1-RELEASE. My machine serves the simple purpose as a nat gateway, so
ipfilter is always going to be necessary on it. Due to this fact, i
That's actually how I interpreted the man page too (the way you did),
but rc.conf says the inverse, and my testing corresponds to this as
well...
ipfilter_flags= # should be *empty* when ipf is _not_ a
module
# (i.e. compiled into the kernel) to
