ng_netflow and bridging firewall

[Gleb Smirnoff]

On Thu, Sep 01, 2005 at 01:02:01PM +0900, Ganbold wrote:
G> I also tried to create graph like following way:
G> 
G> ngctl mkpeer xl1: tee lower left
G> ngctl connect xl1: xl1:lower upper right
G> ngctl mkpeer xl1:lower one2many left2right many0
G> ngctl connect xl1:lower.left2right xl1:lower many1 right2left
G> ngctl name xl1:lower.right2left o2m
G> ngctl mkpeer o2m: netflow one iface0
G> ngctl name o2m:one netflow
G> ngctl mkpeer netflow: ksocket export inet/dgram/udp
G> ngctl msg netflow:export connect inet/127.0.0.1:8818
G> 
G> I got above from http://www.unix.lviv.ua/index_rus.html?art/nf.html site.
G> 
G> Right after it firewall didn't work again. How can I solve this problem?
G> I don't know yet why ipfw started not to work.  Is this bug of ipfw or 
G> something else?

You can try 6.0-BETA3. The bug betwee ng_ether(4) and bridge(4) interaction
has been fixed here.

-- 
Totus tuus, Glebius.
GLEBIUS-RIPN GLEB-RIPE