Hello All, I do not want to insist too muich further about this problem, but I need to find an issue in order to implement that feature properly.
I can't resolve how to do it considering I am looking to do a NAT and not a bridged connection. For this reason the bridge drops packets. If you have any idea in order to help me to try something new it would be helpful. Thanks. Le Jeudi 04 Mars 2010 19:17:00, Jean-Francois a icrit : > Le Mercredi 03 Mars 2010 21:38:18, vous avez icrit : > > > 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. > > Yet I expected that provided interfaces are marked with "-learn" and the > bridge is flushed, the following behaviour would happen, which is'nt. > > From bridge(4) > If the bridge has no knowledge about where the destination is to be found, > the bridge will forward he frame to all attached segments. > > # brconfig bridge0 addr > # brconfig > bridge0: flags=141<UP,RUNNING,PROMISC> > priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto > rstp sis0 flags=2<DISCOVER> > port 1 ifpriority 0 ifcost 0 > gif0 flags=3<LEARNING,DISCOVER> > port 7 ifpriority 0 ifcost 0 > re0 flags=2<DISCOVER> > port 2 ifpriority 0 ifcost 0 > pass in on re0 src 00:22:b0:bd:32:61 tag server > pass in on re0 src 00:1f:d0:a0:db:49 tag client > Addresses (max cache: 100, timeout: 240):
