Repository : ssh://git@diktynna/doc On branches: backup-redmine,main

commit 809cbae7b2db7f15ac7dcedc7417c8899fadc1e0 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Fri Apr 19 20:50:05 2024 +0000

doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding

809cbae7b2db7f15ac7dcedc7417c8899fadc1e0 batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 10 ++++++++++ 1 file changed, 10 insertions(+)

diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index 6285721b..209686c5 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -55,6 +55,16 @@ Answer: yes

!mld-to-mcast-routers-only-scenario-B.png!

+**Learning:** + +1) Bridged-in host B listens to a link-local multicast address <MC-LL-B> +2) Node Y floods an MLD Query through the mesh +3) Host B replies to the MLD query with an MLD Report for <MC-LL-B> +3.1) br0 on node Y learns that a listener for <MC-LL-B> is behind eth0 and then forwards the MLD Report further towards the querier on br0 - but not to bat0 - as required by RFC4541 +3.2) batman-adv on node Y learns about the listener for <MC-LL-B> through the export of the bridge and then adds it to TT, which gets distributed to other nodes. +3.3) No matter if enabling or disabling the batman-adv multicast_rtr_only option node bat0 on node Y will not have received an MLD Report +3.4) batman-adv on nodes X learns about <MC-LL-B> through the TT + h3. Scenario C: Multicast from host on node with a querier

h4. Scenario C, Overview: