IPFW1->2 regression: "in/out/via any" ignored

2006-03-23 Thread Dmitry Pryanishnikov
Hello! I've found a serious regression during the IPFW1->2 transition. I'm using "recv any" construction to match transit packets only. Manpage ipfw(8) clearly says: recv | xmit | via {ifX | if* | ipno | any} Matches packets received, transmitted or going through, respec-

Re: IPFW1->2 regression: "in/out/via any" ignored

2006-03-23 Thread Luigi Rizzo
On Thu, Mar 23, 2006 at 02:03:20PM +0200, Dmitry Pryanishnikov wrote: > > Hello! > > I've found a serious regression during the IPFW1->2 transition. I'm using > "recv any" construction to match transit packets only. Manpage ipfw(8) clearly > says: > > recv | xmit | via {ifX | if* | ipno

Re: IPFW1->2 regression: "in/out/via any" ignored

2006-03-23 Thread Dmitry Pryanishnikov
Hello! On Thu, 23 Mar 2006, Luigi Rizzo wrote: Matches packets received, transmitted or going through, respec- tively, the interface specified by exact name (ifX), by device name (if*), by IP address, or through some interface. .

Re: IPFW1->2 regression: "in/out/via any" ignored

2006-03-23 Thread Luigi Rizzo
On Thu, Mar 23, 2006 at 04:47:17PM +0200, Dmitry Pryanishnikov wrote: ... > > For locally generated packets i admit 'recv any' may be of some use, > > and this is unsupported. There are probably workaround such as 'src-ip me' > > Oops! How can one know that feature which is documented from the b

Re: IPFW1->2 regression: "in/out/via any" ignored

2006-03-29 Thread Dmitry Pryanishnikov
Hello! On Thu, 23 Mar 2006, Luigi Rizzo wrote: For locally generated packets i admit 'recv any' may be of some use, and this is unsupported. There are probably workaround such as 'src-ip me' Oops! How can one know that feature which is documented from the beginning, which worked in ipfw1 -