Sorry, that's was in another mistakenly off-list reply. Kernel is 2.6.24, been seeing this problem since 2.6.16 when I started the setup. richardvoigt@xxxxxxxxx wrote: > > You still didn't tell us any version numbers, and I've got a similar > setup which "works for me". The only real difference is that my box > routes between two logical bridges, and the bridged interfaces are > multiple vlans in the same trunk. I can even protect individual vlans > from each other with netfilter rules. > > What if you routed "out" as a new vlan on the same cable as "in"? > > That's an interesting idea which I haven't tried yet. An interesting tidbit is that there is a handful of machines in the lot which are affected right away (as soon as I add a second vlan interface to the bridge). It may just be that they just have a very short arp timeout. I tried to find a pattern in their MAC addresses or hardware but there isn't really one. I first assumed there was a problem with those machines but given that the ARP reply never gets to the trunk cable going their way, I concluded otherwise. Thanks a lot for the help. The fact that you have a setup that works gives me some confidence that I'm not just trying to do something insane ;) Jonathan _______________________________________________ Bridge mailing list Bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/bridge
