> > What is the reason why some packets passing on re0 will not be seen on > > bridge0 > > > > given I set up the following configuration : > > bridgename.bridge0 > > add re0 > > up > > > > I expected to see all the packets passing on re0 on bridge0 too which is > > obviously not the case. > > That would be wrong. The bridge is a bridge, not a virtual software > switch. > > It decides not to forward packets which don't need to hit the other > segments. > > This is described very well in the manual page. > > > # brconfig > > bridge0: flags=141<UP,RUNNING,PROMISC> > > > > priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto > > rstp re0 flags=3<LEARNING,DISCOVER> > > > > port 2 ifpriority 0 ifcost 0 > > > > Addresses (max cache: 100, timeout: 240): > > 00:1f:d0:d0:db:59 re0 1 flags=0<> > > 00:22:b0:de:32:60 re0 1 flags=0<> > > > > # ifconfig > > re0: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> > > mtu 1500 > > > > lladdr 00:09:55:a9:72:81 > > priority: 0 > > groups: egress > > media: Ethernet autoselect (1000baseT > > full-duplex,rxpause,txpause) status: active > > inet6 fe80::208:55ff:aea8:7281%re0 prefixlen 64 scopeid 0x2 > > inet 10.0.1.44 netmask 0xffffff00 broadcast 10.0.1.255 > > > > enc0: flags=0<> mtu 1536 > > > > priority: 0 > > > > bridge0: flags=141<UP,RUNNING,PROMISC> mtu 1500 > > > > priority: 0 > > groups: bridge > > > > pflog0: flags=141<UP,RUNNING,PROMISC> mtu 33200 > > > > priority: 0 > > groups: pflog > > > > Regards.
I think it's just my mistake, I used to listen to bridge0 and therefore could see only broadcast packets. #tcpdump -i bridge0 Is the rule : #brconfig bridge0 rule pass in on fxp0 src 9:8:7:6:5:4 tag boss working in case bridge0 has only one member which means packets have nowhere to be forwarded ? Or do I need to make a virtual device in order that packets will be forwarded to it for the taggin rule to work ? Regards
