Date: Sun, 19 Sep 1999 15:35:16 +0200 (CEST) From: hohmuth@inf.tu-dresden.de To: FreeBSD-gnats-submit@freebsd.org Subject: bin/13818: `ipfw' doesn't grok "log" keyword Message-ID: <199909191335.PAA01468@olymp.sax.de>
next in thread | raw e-mail | index | archive | help
>Number: 13818 >Category: bin >Synopsis: `ipfw' doesn't grok "log" keyword >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Sep 19 06:40:00 PDT 1999 >Closed-Date: >Last-Modified: >Originator: Michael Hohmuth >Release: FreeBSD 3.3-STABLE i386 >Organization: none >Environment: FreeBSD olymp.sax.de 3.3-STABLE FreeBSD 3.3-STABLE #0: Sun Sep 19 02:14:59 CEST 1999 root@olymp.sax.de:/usr/src/sys/compile/OLYMPISDN i386 This is FreeBSD-stable as of Sep 18, 1999. >Description: 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") Also, when a rule containing the "log" keyword is in a command file, and `ipfw' is invoked like "ipfw commandfile", then reading the command file aborts at the line containing the "log" keyword, and all lines after that line are ignored. >How-To-Repeat: # ipfw add deny log tcp from any to any >Fix: Workaround: Leave out the "log" keyword. >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909191335.PAA01468>