does bridging work in -current ?

I tried to enable bridging to test a multiport ethernet card (www.napatech.com)
and I can see packets going into the bridge code when I enable debugging
but nothing seems to get sent out.

Anyone know if bridging actually works these days ?

	hex-i386# sysctl net.link.ether.bridge
	net.link.ether.bridge.version: 031224
	net.link.ether.bridge.debug: 2
	net.link.ether.bridge.ipf: 0
	net.link.ether.bridge.ipfw: 0
	net.link.ether.bridge.copy: 0
	net.link.ether.bridge.ipfw_drop: 0
	net.link.ether.bridge.ipfw_collisions: 0
	net.link.ether.bridge.packets: 301
	net.link.ether.bridge.dropped: 0
	net.link.ether.bridge.predict: 0
	net.link.ether.bridge.enable: 1
	net.link.ether.bridge.config: nt3,nt7

bdg_timeout: flushing stale entry 7212
bridge_in: 00.00.24.c3.4c.7b ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bridge_in: 00.00.24.c3.4c.7b ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bridge_in: new addr 00.e0.81.01.9d.2d at 7212 for nt3
bridge_in: 00.e0.81.01.9d.2d ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bdg_timeout: flushing stale entry 2232
bridge_in: 00.e0.81.01.9d.2d ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bridge_in: 00.e0.81.01.9d.2d ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bridge_in: 00.e0.81.01.9d.2d ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bridge_in: 00.e0.81.01.9d.2d ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bridge_in: new addr 00.00.24.c3.4c.7b at 2232 for nt7
bridge_in: 00.00.24.c3.4c.7b ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bridge_in: 00.00.24.c3.4c.7b ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bdg_timeout: flushing stale entry 7212
bridge_in: 00.00.24.c3.4c.7b ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bridge_in: 00.00.24.c3.4c.7b ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bridge_in: 00.00.24.c3.4c.7b ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
bdg_timeout: flushing stale entry 2232
bridge_in: new addr 00.e0.81.01.9d.2d at 7212 for nt3
bridge_in: 00.e0.81.01.9d.2d ->ff.ff.ff.ff.ff.ff ty 0x0806 dst BDG_BCAST   
Expensive timeout(9) function: 0xc067dfb8(0) 0.213431874 s
bdg_timeout: flushing stale entry 7212

nt0: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ether 00:0d:e9:01:01:c0
nt1: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ether 00:0d:e9:01:01:c1
nt2: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ether 00:0d:e9:01:01:c2
nt3: flags=8903<UP,BROADCAST,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        ether 00:0d:e9:01:01:c3
nt4: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ether 00:0d:e9:01:01:c4
nt5: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ether 00:0d:e9:01:01:c5
nt6: flags=8803<UP,BROADCAST,SIMPLEX,MULTICAST> mtu 1500
        ether 00:0d:e9:01:01:c6
nt7: flags=8903<UP,BROADCAST,PROMISC,SIMPLEX,MULTICAST> mtu 1500
        ether 00:0d:e9:01:01:c7




-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk_at_FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.