On Mon, Jul 30, 2012 at 7:31 AM, Simon Wunderlich simon.wunderlich@s2003.tu-chemnitz.de wrote:
Hello Guido,
Thanks for working that out. I've just tried out VLANs on Ethernet with BATMAN myself, and it worked well here - so I can't reproduce it by simply using VLANs.
Another cause of the fault may be the VLAN stuff in OpenWRT, as this is not a "real" VLAN but just a way to address the ports on your box. I have not much experience with that, but I've heard funny things about it. ;) Have you tried changing the VLAN config? E.g. changing ports '0t 2t' for eth0.2 to '0t 2' (to remove tagging)?
Do you have the same problem on other types of devices? (Maybe the internal switch is acting weird)
Sorry for necrotizing the thread, but i just wanted to leave a quick note in case anyone else stumps on this.
you were right once again Simon, TP-Link TL-MR3220 (and MR3420) has, in fact, "true" VLAN capability in the hardware switch, but unfortunately that capability has limitations.
notably, it can't send tagged and untagged frames through the same port, and falling back to software tagging doesn't give meaningful results either (switch is broken: packets aren't forwarded between ports)
I just dumped the whole vlan thing altogether on this hardware.
Thanks as always!
Gui