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/12/2005 17:56: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: Patrick Welche <prlw1@newn.cam.ac.uk>, gnats-bugs@NetBSD.org
Subject: Re: bin/30400: ipf log dup-to bug
Date: Sun, 12 Jun 2005 18:55:05 +0100

 On Sun, Jun 12, 2005 at 12:26:20AM +0200, Bernd Ernesti wrote:
 > On Sat, Jun 11, 2005 at 11:12:27PM +0100, Patrick Welche wrote:
 > [..]
 > 
 > > 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)
 > 
 > RTFM.
 
 Read the PR
 
 > To quote the part which you missed again:
 > 
 > .. and has no effect on whether the packet will be allowed through the filter.
 
 To quote the part which you missed again:
 
   log out on rtk0 dup-to xi0 all
                   ^^^^^^^^^^
 > log as an action just does logging and nothing more.
 
 Of course the above rule doesn't say anything about whether or not a packet
 leaves rtk0, and just logs the packet to /dev/ipl.
 
 You haven't explained to me why no packet leaves xi0.
 
 Patrick