Repository : ssh://git@diktynna/doc On branches: backup-redmine,main
commit ca63f48879269fb240dfea354c0230f417cabfa1 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Sat Aug 31 20:24:29 2024 +0000
doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding
ca63f48879269fb240dfea354c0230f417cabfa1 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 1b13114e..3d6074e0 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -11,7 +11,7 @@ h2. Introduction
Currently batman-adv forwards/floods an IGMP/MLD Report to all other nodes by default. The _multicast_mld_rtr_only_ option allows to change this behavior to only forward IGMP/MLD Reports to nodes with a multicast router, to reduce IGMP/MLD overhead in the mesh while still enabling layer 3 multicast routing. However this option is not always safe to use, so this page illustrates the scenarios where this option can and cannot be used.
-tl;dr: Scenario C is the potentially unsafe scenario for a _multicast_mld_rtr_only_ option. +_tl;dr:_ Scenario C is the potentially unsafe scenario for a _multicast_mld_rtr_only_ option.
h3. Scenario A: Multicast to host on node without querier