Date: Tue, 21 Sep 1999 16:00:01 -0700 (PDT) From: Doug <Doug@gorean.org> To: freebsd-bugs@FreeBSD.org Subject: Re: bin/13818: `ipfw' doesn't grok "log" keyword Message-ID: <199909212300.QAA35333@freefall.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR bin/13818; it has been noted by GNATS.
From: Doug <Doug@gorean.org>
To: hohmuth@inf.tu-dresden.de
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: bin/13818: `ipfw' doesn't grok "log" keyword
Date: Tue, 21 Sep 1999 15:55:14 -0700 (PDT)
On Sun, 19 Sep 1999 hohmuth@inf.tu-dresden.de wrote:
> Since I last cvsup'd and made world, `ipfw' doesn't grok anymore the
> log keyword described in the manual. Previously, invoking `ipfw' like
> this would have the desired effect:
>
> # ipfw add deny log tcp from any to any in via ppp0 setup
>
> Now, strangly, it prints:
>
> ipfw: sysctlbyname("net.inet.ip.fw.verbose_limit")
Since my -Stable is newer than yours and working as advertised I
suspect that when you rebuilt your kernel you modified or left out the
VERBOSE_LIMIT option. Try this command:
sysctl net.inet.ip.fw.verbose_limit
and you should get a number. I suspect you will get nothing or zero. If
so, as a temporary measure you can (as root) do:
sysctl -w net.inet.ip.fw.verbose_limit=2000
You may also choose another value instead of 2000. Then if all works as it
should try rebuilding your kernel with the appropriate firewall options
from the LINT file.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
home |
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909212300.QAA35333>