You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
router2 receives PIM Join/Prune from router1 and receives ICMPv6 multicast messages from client2 but does not forward these to router1.
Details:
Ignoring the issues discovered for router0 in #13 for now, router2 should still forward to router1 as at least router1 sends correct pim-join-prune messages to router2 due to the listener on client2. However:
Packets are received on lan0 of router2 from client2 fine:
So I'm a bit confused why the ICMPv6 multicast packets are not forwarded from router2 to router1. The Linux kernel in use is a 4.19.28 kernel as provided by Debian Sid. (I'm probably missing something obvious?)
The text was updated successfully, but these errors were encountered:
Sorry, had read your excellent blog posts on multicast several times and you did mention to watch the TTL... but I forgot :-).
Now the ping6 from client2 arrives on client1 via router2->router1 fine and this echo request is then replied to via unicast and arrives back on client2 again.
Setup:
Same as in #13.
Issue:
router2
receives PIM Join/Prune fromrouter1
and receives ICMPv6 multicast messages fromclient2
but does not forward these torouter1
.Details:
Ignoring the issues discovered for
router0
in #13 for now,router2
should still forward torouter1
as at leastrouter1
sends correct pim-join-prune messages torouter2
due to the listener onclient2
. However:Packets are received on lan0 of
router2
fromclient2
fine:However they are not forwarded to
router1
on wan0:The pim6sd internal routing table on
router2
looks like this:And there is an entry in "ip -6 mroute show":
Also, multicast forwarding seems to be correctly enabled in the kernel:
So I'm a bit confused why the ICMPv6 multicast packets are not forwarded from router2 to router1. The Linux kernel in use is a 4.19.28 kernel as provided by Debian Sid. (I'm probably missing something obvious?)
The text was updated successfully, but these errors were encountered: