Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2019-09-14,master

commit 0c1c9c80d2c7d6f5d29d457180b5452a42a49032 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Thu Aug 1 19:24:23 2019 +0000

doc: batman-adv/Multicast-optimizations-tech

0c1c9c80d2c7d6f5d29d457180b5452a42a49032 batman-adv/Multicast-optimizations-tech.textile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/batman-adv/Multicast-optimizations-tech.textile b/batman-adv/Multicast-optimizations-tech.textile index 263aa45..61e03e9 100644 --- a/batman-adv/Multicast-optimizations-tech.textile +++ b/batman-adv/Multicast-optimizations-tech.textile @@ -79,15 +79,15 @@ Example: ff02::1 (all nodes) | (excl. all nodes addr.) |=. supported without bridges¹. Example: 224.0.0.251 (mDNS) |=. supported². Example: ff12::39 (locally administrated) | -| *routable* |=. support planned³. -Example: 239.1.2.3 (locally administrated) |=. support planned³. +| *routable* |=. supported without bridges³. +Example: 239.1.2.3 (locally administrated) |=. supported². Example: ff0e::101 (NTP) |

¹: These addresses cannot be considered for optimization towards nodes which have a bridge interface on top of their batman interface as they are not snoopable. See [[multicast-optimizations-flags#BATADV_MCAST_WANT_ALL_UNSNOOPABLES]] for details.

²: In bridged scenarios, an IGMP/MLD querier needs to be present in the mesh. Also, a 3.17 kernel or newer is required.

-³: Routable multicast addresses are not supported yet. See [[multicast-optimizations-tech#routable-multicast-addresses]] for details. +³: Routable IPv4 multicast addresses in bridged scenarios are not supported yet. See [[multicast-optimizations-tech#routable-multicast-addresses]] for details.

For details on IPv4 and IPv6 multicast address ranges check out this detailed article on "Wikipedia":https://en.wikipedia.org/wiki/Multicast_address.