commits May 2024

commits@lists.open-mesh.org

1 participants
88 discussions

[doc] backup-redmine,main: doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding (e7e3c932)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit e7e3c932a90b1413ceefdaca4e18e280ee2ba956 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri Apr 19 21:08:34 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- e7e3c932a90b1413ceefdaca4e18e280ee2ba956

1 0

[doc] backup-redmine,main: doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding (f0ed77e2)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit f0ed77e2a33a8432e7d6217e4b584d05a1ebc0e7 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri Apr 19 21:14:50 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- f0ed77e2a33a8432e7d6217e4b584d05a1ebc0e7 batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index 533ac971..dde5ce51 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -109,3 +109,15 @@ Answer: **no!** 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) C) Export batman-adv TT-global to bridge MDB (not implemented) + +h3. Scenario D: Multicast to/from host on node with a bridged-in querier + +WIP + +h4. Scenario D, Overview: + +_Can bridged-in host A send multicast to bridged-in host B?_ + +h4. Scenario D, Analysis: + +Answer: yes \ No newline at end of file

1 0

[doc] backup-redmine,main: doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding (f410e769)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit f410e7699d54e0a71d926f97ae4cb2f924295073 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri Apr 19 21:01:37 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- f410e7699d54e0a71d926f97ae4cb2f924295073 batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index e151335f..764355aa 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -93,8 +93,8 @@ Learning: 3) Host A replies to the MLD query with an MLD Report for <MC-LL-A> 3.1) br0 on node X learns that a listener for <MC-LL-A> is behind eth0 and then forwards the MLD Report further towards the querier on bat0, as required by RFC4541 3.2) batman-adv on node X learns about the listener for <MC-LL-A> through the export of the bridge and then adds it to TT, which gets distributed to other nodes. -3.3) With the batman-adv multicast_rtr_only option enabled bat0 on node X will not forward the MLD Report -3.4) batman-adv on nodes Y learns about <MC-LL-A> through the TT +3.3) With the batman-adv multicast_rtr_only option enabled batman-adv on node X will refrain to forward the MLD Report further into the mesh +3.4) batman-adv on node Y learns about <MC-LL-A> through the TT Potential Workarounds:

1 0

[doc] backup-redmine,main: doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding (50e00998)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 50e009980ea672465e0bdd1709336214a679bcf1 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri Apr 19 21:03:23 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- 50e009980ea672465e0bdd1709336214a679bcf1 batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index 764355aa..92863caf 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -86,7 +86,7 @@ Answer: **no!** !mld-to-mcast-routers-only-scenario-C.png! -Learning: +**Learning:** 1) Bridged-in host A listens to a link-local multicast address <MC-LL-A> 2) Node Y floods an MLD Query through the mesh @@ -96,6 +96,14 @@ Learning: 3.3) With the batman-adv multicast_rtr_only option enabled batman-adv on node X will refrain to forward the MLD Report further into the mesh 3.4) batman-adv on node Y learns about <MC-LL-A> through the TT +**Multicast packet forwarding:** + +4) Bridged-in host B sends a multicast packet to the multicast address <MC-LL-A> +4.1) br0 on node X has not heard of <MC-LL-A>, but will forward the multicast packet towards the MLD Querier - and not towards bat0 - as required by RFC4541 +4.2) batman-adv on node X had previously learned through the TT that <MC-LL-B> has a listener on node Y and batman-adv will therefore forward the multicast packet to node Y +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: 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

1 0

[doc] backup-redmine,main: doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding (79578814)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 795788149cfa4680ce497b77a072e9b0de879680 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri Apr 19 21:04:01 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- 795788149cfa4680ce497b77a072e9b0de879680 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 92863caf..33934310 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -99,7 +99,7 @@ Answer: **no!** **Multicast packet forwarding:** 4) Bridged-in host B sends a multicast packet to the multicast address <MC-LL-A> -4.1) br0 on node X has not heard of <MC-LL-A>, but will forward the multicast packet towards the MLD Querier - and not towards bat0 - as required by RFC4541 +4.1) br0 on node X has not heard of <MC-LL-A>, but will forward the multicast packet towards the MLD Querier - but not to bat0 - as required by RFC4541 4.2) batman-adv on node X had previously learned through the TT that <MC-LL-B> has a listener on node Y and batman-adv will therefore forward the multicast packet to node Y 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!

1 0

[doc] backup-redmine,main: doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding (9f0690dd)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 9f0690dd605452d2ed367809e0e851ab9409c2e3 Author: Linus Lüssing <linus.luessing(a)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)

1 0

[doc] backup-redmine,main: doc: batman-adv/mld-to-mcast-routers-only-scenario-B.png (56474a61)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 56474a61582e9e333d9c849518b63a42669e2f24 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri Apr 19 21:08:32 2024 +0000 doc: batman-adv/mld-to-mcast-routers-only-scenario-B.png >--------------------------------------------------------------- 56474a61582e9e333d9c849518b63a42669e2f24 batman-adv/mld-to-mcast-routers-only-scenario-B.png | Bin 0 -> 181824 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/batman-adv/mld-to-mcast-routers-only-scenario-B.png b/batman-adv/mld-to-mcast-routers-only-scenario-B.png new file mode 100644 index 00000000..a054013a Binary files /dev/null and b/batman-adv/mld-to-mcast-routers-only-scenario-B.png differ

1 0

[doc] backup-redmine,main: doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding (809cbae7)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 809cbae7b2db7f15ac7dcedc7417c8899fadc1e0 Author: Linus Lüssing <linus.luessing(a)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:

1 0

[doc] backup-redmine,main: doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding (03a42da4)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 03a42da413d43ec46dfce1b951e57ac08a6980d9 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri Apr 19 20:52:35 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- 03a42da413d43ec46dfce1b951e57ac08a6980d9 batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index 209686c5..956f6e7b 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -65,6 +65,14 @@ Answer: yes 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 +**Multicast packet forwarding:** + +4) Bridged-in host A sends a multicast packet to the multicast address <MC-LL-B> +4.1) br0 on node X has not heard of <MC-LL-B>, but will forward the multicast packet towards the MLD Querier, as required by RFC4541 +4.2) batman-adv on node X had previously learned through the TT that <MC-LL-B> has a listener on node Y and batman-adv will therefore forward the multicast packet to node Y +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! + h3. Scenario C: Multicast from host on node with a querier h4. Scenario C, Overview:

1 0

[doc] backup-redmine,main: doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding (67ab373f)
by postmaster＠open-mesh.org 10 May '24

10 May '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 67ab373fb3917fc24f6c97e4ed7ba37fdb4e32dc Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Fri Apr 19 20:53:02 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- 67ab373fb3917fc24f6c97e4ed7ba37fdb4e32dc 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 956f6e7b..96e1e01b 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -82,7 +82,7 @@ _Can bridged-in host B send multicast to bridged-in host A?_ h4. Scenario C, Analysis: -Answer: no +Answer: **no!** !mld-to-mcast-routers-only-scenario-C.png!

1 0

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits May 2024