Repository : ssh://git@diktynna/doc On branches: backup-redmine,main
commit 9f0690dd605452d2ed367809e0e851ab9409c2e3 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Fri Apr 19 21:04:16 2024 +0000
doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding
9f0690dd605452d2ed367809e0e851ab9409c2e3 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 33934310..ab439b9a 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -104,7 +104,7 @@ Answer: **no!** 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 from host A!
-Potential Workarounds: +**Potential Workarounds:**
A) Set bridge port _multicast_router_ setting for bat0 to 2 (e.g.: _$ echo 2 > /sys/class/net/bat0/brport/multicast_router_) => always forwards multicast packets to bat0 B) Send report not just to multicast routers, but also to queriers (not implemented)