As it turns out, it's a bug in the igmp snooping code in the kernel that's the problem with multicast traffic not being forwarded.
This seems to affect recent versions. To check if it's turned on, run cat /sys/devices/virtual/net/<bridgename>/bridge/multicast_snooping If it's 1, it's highly this is the culprit causing the non-propagation of the multicast traffic. The solution is to turn it off by setting it 0. echo 0 > /sys/devices/virtual/net/<bridge name>/bridge/multicast_snooping On Sat, May 14, 2016 at 2:54 PM, Liang Guo <[email protected]> wrote: > > tap0 Link encap:Ethernet HWaddr ae:a2:e1:cd:aa:68 > > inet6 addr: fe80::aca2:e1ff:fecd:aa68/64 Scope:Link > > UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:2336 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:500 > > RX bytes:0 (0.0 B) TX bytes:1015186 (991.3 KiB) > > > > bridge name bridge id STP enabled interfaces > > br0 8000.7a22d71b042e no eth0 > > tap0 > > > > tap0 RX packets is 0, can you double check your tinc config is correct? > > You'd better remove tap0 from br0, configure sufficient ip address on > tap0, then check the connection with other tinc nodes. > > -- > Liang Guo > http://guoliang.me/ > _______________________________________________ > tinc mailing list > [email protected] > https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc >
_______________________________________________ tinc mailing list [email protected] https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
