Repository : ssh://git@diktynna/doc On branches: backup-redmine,main
commit a663bfd5c68a95fcb5894c23b81beefd6f257c83 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Fri Apr 19 20:45:41 2024 +0000
doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding
a663bfd5c68a95fcb5894c23b81beefd6f257c83 batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index 590d7f0a..6285721b 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -40,7 +40,7 @@ Answer: yes 4.1) br0 on node X has not heard of <MC-LL-B>, but will forward the multicast packet towards the MLD Querier, as required by RFC4541 4.2) batman-adv on node X had previously learned through the TT that <MC-LL-B> has a listener on node Y and batman-adv will therefore forward the multicast packet to node Y 4.3) br0 on node Y has previously learned about <MC-LL-B> through the MLD Report, so it forwards the multicast packet on eth0 to host B -4.4) host B successfully receives the multicast packet! +4.4) Host B successfully receives the multicast packet from host A!
h3. Scenario B: Multicast to host on node with a querier