"richardvoigt@xxxxxxxxx" <richardvoigt@xxxxxxxxx> wrote on 13/06/2009 17:57:55: > > On Sat, Jun 13, 2009 at 10:03 AM, Joakim > Tjernlund<joakim.tjernlund@xxxxxxxxxxxx> wrote: > > Benny Amorsen <benny+usenet@xxxxxxxxxx> wrote on 13/06/2009 01:58:53: > >> > >> Joakim Tjernlund <Joakim.Tjernlund@xxxxxxxxxxxx> writes: > >> > >> > Currently the bridge does not impl. split horizon which will easily > >> > cause loops when 2 or more VLANs are added from the same physical interface. > >> > >> Why would they cause loops? If your topology isn't loop free, run > >> spanning tree in the VLAN's. Yet another thing most hardware switches > >> can't do, incidentally. > > > > ehh, connect two Linux bridges that have 2 VLANs in common on the interswitch connection. > > For example, here is a configuration that meets your problem > description and has no loops: > > host A eth0 connected to hostB eth0 > > host A: > brctl add br0 > brctl addif br0 eth0.1 > brctl addif br0 eth1 > brctl add br1 > brctl addif br1 eth0.2 > brctl addif br1 eth2 Yes, but eth1 and eth2 don't talk. > > host B: > brctl add br0 > brctl addif br0 eth0.1 > brctl addif br0 wlan0.1 > brctl add br1 > brctl addif br1 eth0.2 > brctl addif br1 wlan0.2 > > Let's compare this to your complaint: > Two Linux hosts.... check > Two VLANs in common.... check > Both VLANs on the inter-switch connection.... check > > Nope, there are no loops. Of course not. You can always fix what you want somehow but that doesn't mean that there may be better ways of doing things. > > You need to stop calling "a machine running bridging" a "Linux > bridge". A "bridge", in Linux, is a virtual interface inside a > machine with the bridging module loaded. There can be more than zero, > one, or multiple bridges in a single Linux machine. I think that when > you understand that, all your problems will go away with a simpler > configuration and no changes to the Linux kernel. Aha, I had/have the impression that one bridge instance should mimic a real bridge, if not you are making some sense. But now I start asking myself what are the semantics for a Linux bridge instance? I would really like to know in what situation you would use the current behavior to forward back VLAN pkgs over the same interface it was received on? Also, I am trying to find where it states that a VLAN is considered its own physical port. Any pointers? Jocke _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
