tinc - May 2016 - Bridge not forwarding multicast traffic to the tap interface

yes, ip_forward was turned on.

iptables is defaulted to ACCEPT policy on all the 3 chains.

On Sat, May 14, 2016 at 1:24 AM, Guus Sliepen <guus at tinc-vpn.org>
wrote:
> On Sat, May 14, 2016 at 12:06:51AM +0800, Terry T wrote:
>
> > I have a Debian 8 64-bit machine set up as a server and apt-got the
tinc
> > package. I configured tinc as a bridge and everything seems normal
except
> > that the tunnel does not forward multicast traffic.
>
> Did you enable forwarding (echo 1 >/proc/sys/net/ipv4/ip_forward) and
> allow forwarding in your iptables rules?
>
> --
> Met vriendelijke groet / with kind regards,
>      Guus Sliepen <guus at tinc-vpn.org>
>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20160514/3f381b11/attachment.html>

On Sat, May 14, 2016 at 01:27:10AM +0800, Terry T wrote:
> yes, ip_forward was turned on.
> 
> iptables is defaulted to ACCEPT policy on all the 3 chains.
Hm. What is generating the multicast traffic? Could it be that the TTL
on the pacets is set to 1, so it will not be forwarded?

-- 
Met vriendelijke groet / with kind regards,
     Guus Sliepen <guus at tinc-vpn.org>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20160513/77aecf05/attachment-0001.sig>

no. the multicast packets were generated by a remote server that has a TTL
of 3.

There was a blog which talks about multicast on tap. I made those changes
that he suggested, but it was in vain.

http://blog.michael.kuron-germany.de/2015/07/arp-and-multicast-packets-lost-with-openvpn-in-tap-mode/

On Sat, May 14, 2016 at 1:32 AM, Guus Sliepen <guus at tinc-vpn.org>
wrote:
> On Sat, May 14, 2016 at 01:27:10AM +0800, Terry T wrote:
>
> > yes, ip_forward was turned on.
> >
> > iptables is defaulted to ACCEPT policy on all the 3 chains.
>
> Hm. What is generating the multicast traffic? Could it be that the TTL
> on the pacets is set to 1, so it will not be forwarded?
>
> --
> Met vriendelijke groet / with kind regards,
>      Guus Sliepen <guus at tinc-vpn.org>
>
> _______________________________________________
> tinc mailing list
> tinc at tinc-vpn.org
> https://www.tinc-vpn.org/cgi-bin/mailman/listinfo/tinc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://www.tinc-vpn.org/pipermail/tinc/attachments/20160514/fcbb04b3/attachment.html>