Subject: Re: bin/30400: ipf log dup-to bug
To: None <gnats-admin@netbsd.org, netbsd-bugs@netbsd.org>
From: Patrick Welche <prlw1@newn.cam.ac.uk>
List: netbsd-bugs
Date: 06/11/2005 22:13:02
The following reply was made to PR bin/30400; it has been noted by GNATS.
From: Patrick Welche <prlw1@newn.cam.ac.uk>
To: Bernd Ernesti <netbsd@lists.veego.de>
Cc: gnats-bugs@NetBSD.org, prlw1@cam.ac.uk
Subject: Re: bin/30400: ipf log dup-to bug
Date: Sat, 11 Jun 2005 23:12:27 +0100
On Sat, Jun 11, 2005 at 09:26:56PM +0200, Bernd Ernesti wrote:
> On Thu, Jun 02, 2005 at 09:51:00AM +0000, prlw1@cam.ac.uk wrote:
> [..]
>
> > man 5 ipf
>
> ACTIONS
> [..]
> log causes the packet to be logged (as described in the LOGGING sec-
> tion below) and has no effect on whether the packet will be
> allowed through the filter.
>
> IMHO, this pr should be closed.
>
> If you want these packages to be logged then use this:
>
> pass out log on rtk0 dup-to xi0 all
> pass in log on rtk0 dup-to xi0 all
IMO there are many work arounds, but at worst the documentation needs
clarification. Nowhere does it say that "log" is different from "pass" or
"block" as an action. (cf BNF - log is an action as in my rule as well
as an option as in your rule)
It may well be that my rule is not expected to work. However, that would
"expected by the author" as opposed to "expected by someone who read the
man pages".
Patrick