Repository : ssh://git@diktynna/doc On branches: backup-redmine,main
commit 69428fa7233f05eed96477bdb27de9ce911024e8 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Sat Aug 31 20:57:52 2024 +0000
doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding
69428fa7233f05eed96477bdb27de9ce911024e8 batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index 3ea88cec..cc918632 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -144,8 +144,9 @@ Answer: yes
4) Bridged-in host B sends a multicast packet to the multicast address <MC-LL-A> 4.1) br0 on node X has heard of <MC-LL-B> and will forward the multicast packet towards bat0, as required by RFC4541 -... -Packet arrives at bridged-in host A +4.2) batman-adv on node X had previously learned through the TT that <MC-LL-A> has a listener on node X and batman-adv will therefore forward the multicast packet to node X +4.3) br0 on node X has previously learned about <MC-LL-A> through the MLD Report, so it forwards the multicast packet on eth0 to host A +4.4) Host A successfully receives the multicast packet from host B!
h3. Scenario E: Multicast to host on node with a bridged-in querier