Repository : ssh://git@open-mesh.org/doc
On branches: backup-redmine/2019-09-14,master
commit 4b558be0f9e88301f7b2bf6a07d42c130f2f4ee5 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Thu Aug 1 19:12:38 2019 +0000
doc: batman-adv/Multicast-optimizations
4b558be0f9e88301f7b2bf6a07d42c130f2f4ee5 batman-adv/Multicast-optimizations.textile | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/batman-adv/Multicast-optimizations.textile b/batman-adv/Multicast-optimizations.textile index f44514e..5fa34a3 100644 --- a/batman-adv/Multicast-optimizations.textile +++ b/batman-adv/Multicast-optimizations.textile @@ -30,15 +30,14 @@ h3. Limitations
In the following cases multicast packets are still distributed via classic flooding:
-* If there is more than one listener for a specific multicast group. -* If the multicast packets have a scope greater than link-local. +* If there are more than #multicast-fanout (default: 16) listeners for a specific multicast group.
(These things are work in progress and will be supported at a later time.)
-Additionally, in bridged scenarios multicast packets are still flooded in the following cases: +Additionally, in _bridged_ scenarios multicast packets are still flooded in the following cases:
* If there is no IGMP/MLD querier. -* If the IPv4 multicast destination is between 224.0.0.1 and 224.0.0.255. +* If the packet has an IPv4 multicast destination. * If the IPv6 multicast destination is ff02::1.
h2. How to deactivate the multicast optimizations?