On Mon, 29 Nov 1999, O'Shaughnessy Evans wrote:
> "Mikhail A. Sokolov" <[EMAIL PROTECTED]> wrote:
> > No, it can't. He was refering to ipf -V; I managed to reproduce the
> > behaviour several days ago, but since I remade the devices it's ok in
> > my case, but in his. Again, no other rules/whatever is being used in
> > the test, just ipf -V.
>
> Makes sense. I get the same message, BTW, on my Solaris 7 box when the
> ipf kernel module isn't loaded and I run "ipf -V".
>
> --
> O'Shaughnessy Evans
But I'm not using a loadable kernel module. I compiled IPFilter in my
kernel from the FreeBSD source tree with:
options IPFILTER
options IPFILTER_LOG
#options IPFILTER_LKM
And bootup did show:
Nov 28 20:02:34 /kernel: IP Filter: initialized. Default = pass all, Logging = enabled
Nov 28 20:02:34 /kernel: IP Filter: v3.3.3
Unfortunately I've only been using FreeBSD for about a year and a half now
(excellent platform for program development btw) so I still do not know all the
internal workings. But how would I know, aside from /var/log/messages, that
IPFilter is loaded and running when not existing as a lkm?
--
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
