commits September 2024

commits@lists.open-mesh.org

1 participants
23 discussions

[linux-merge]linux integration; annotated tag, v6.11, created. v6.11
by postmaster＠open-mesh.org 15 Sep '24

15 Sep '24

The annotated tag, v6.11 has been created at fa7818b3a6dd56c7956f515d287ed9f80c7bf59a (tag) tagging 98f7e32f20d28ec452afb208f9cffc08448a2652 (commit) replaces v6.11-rc7 tagged by Linus Torvalds on Sun Sep 15 16:57:56 2024 +0200 - Shortlog ------------------------------------------------------------ Linux 6.11 -----BEGIN PGP SIGNATURE----- iQFSBAABCAA8FiEEq68RxlopcLEwq+PEeb4+QwBBGIYFAmbm9fQeHHRvcnZhbGRz QGxpbnV4LWZvdW5kYXRpb24ub3JnAAoJEHm+PkMAQRiGXcwH/A8+IXnrGv+VzYgD +mE4hgGGHt4dClcUZ31gQetkkT6xktEVp6pB6JkFO7oEgBiTkJBbYGl6VZtsAIOd Fi3jic8ik0uhZLFcxDJcHTceh6Pw8bkhWoh0tkF3bkDRwbppJdG7Khyk8DxTl24w ldqh9om2cC7w9IPVx93xTgKgMMZ63qiJyUdTvxEZI3BG8F70smlgZSPskLp2Iktd FIJZPcyKM0bhJYwZOpXK0vx5C2cA4oIW4xriHUw4aklv646OBxNKevB2JJAft2uA 6LyvuLgnYn/OpdFGZ8slvdmhm6hLWft5B1/bWKorUkz7p5YGiySFzpkMVAkNJ6mS cRwHJNc= =flw3 -----END PGP SIGNATURE----- ----------------------------------------------------------------------- -- linux integration

1 0

[linux-merge]linux integration; annotated tag, v6.11-rc7, created. v6.11-rc7
by postmaster＠open-mesh.org 08 Sep '24

08 Sep '24

The annotated tag, v6.11-rc7 has been created at 8517d20decd39c018e8d7d6bbc5a0ca254c9a007 (tag) tagging da3ea35007d0af457a0afc87e84fddaebc4e0b63 (commit) replaces v6.11-rc6 tagged by Linus Torvalds on Sun Sep 8 14:50:28 2024 -0700 - Shortlog ------------------------------------------------------------ Linux 6.11-rc7 -----BEGIN PGP SIGNATURE----- iQFSBAABCAA8FiEEq68RxlopcLEwq+PEeb4+QwBBGIYFAmbeHCQeHHRvcnZhbGRz QGxpbnV4LWZvdW5kYXRpb24ub3JnAAoJEHm+PkMAQRiGwfwH/ijnVvDWt0L1mpkE oIPmKV+2018CA5ww/Hh+ncToWn/aCmrczHc1SEUOk/SbZnGyXJj/6KiNEK6XpJyu Hb90y53D5B9jkEq8WPbSy5RtqCU598gYPeBxkczjj431jer9EsZVzqsKxGRzdAud 2+Ft/qLiVL8AP5P8IPuU7G8CU6OE0fUL5PyuzMGDtstL3R6lPpG+kf/VrJGV1mp7 DVZO8hKwIi5Vu+ciaTJv+9PMHzXRnMhLIGabtGIzM8nhmrQx/Kv/PMjiEl/OBkmk 6PzafEkxVtBKDNK2Qhp+QMTQJATuPccZI8Kn6peZhqoNWYHBqx7d88Q/2iiAGj0z skPW5Gs= =orf8 -----END PGP SIGNATURE----- ----------------------------------------------------------------------- -- linux integration

1 0

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

07 Sep '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit b83edc532b1ee0eaf6de43904156450aa14e770c Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat Aug 31 21:19:38 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- b83edc532b1ee0eaf6de43904156450aa14e770c batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index cc918632..09a6ef84 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -163,4 +163,18 @@ Answer: yes **Learning:** -WIP \ No newline at end of file +1) Bridged-in host A listens to a link-local multicast address <MC-LL-A> +2) Bridged-in host C on node X floods an MLD Query through the mesh +2.1) Node X sets and floods a WANT_ALL flag, because querier is potentially "shadowing". +2.2) Node Y learns node Y's WANT_ALL flag. +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 (unless it's shadowed by the querier on host C) and will refrain to forward the MLD Report further towards bat0 because bat0 has no querier behind it, as required by RFC4541 +3.2) batman-adv on node X learns about <MC-LL-A> through the export of the bridge (unless it's shadowed), but will not add it to TT, because it has the WANT_ALL flag set + +**Multicast packet forwarding:** + +4) Bridged-in host B sends a multicast packet to the multicast address <MC-LL-A> +4.1) br0 on node Y has not heard of <MC-LL-A>, but will forward the multicast packet towards the MLD Querier, as required by RFC4541 +4.2) batman-adv on node Y has not previously learned through the TT about <MC-LL-A> but batman-adv will forward the multicast packet to node X regardless because of the WANT_ALL flag +4.3) br0 on node X has previously learned about <MC-LL-A> through the MLD Report, so it forwards the multicast packet on eth0 to host A +4.4) Host A successfully receives the multicast packet from host B! \ No newline at end of file

1 0

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

07 Sep '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 69428fa7233f05eed96477bdb27de9ce911024e8 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat Aug 31 20:57:52 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- 69428fa7233f05eed96477bdb27de9ce911024e8 batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index 3ea88cec..cc918632 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -144,8 +144,9 @@ Answer: yes 4) Bridged-in host B sends a multicast packet to the multicast address <MC-LL-A> 4.1) br0 on node X has heard of <MC-LL-B> and will forward the multicast packet towards bat0, as required by RFC4541 -... -Packet arrives at bridged-in host A +4.2) batman-adv on node X had previously learned through the TT that <MC-LL-A> has a listener on node X and batman-adv will therefore forward the multicast packet to node X +4.3) br0 on node X has previously learned about <MC-LL-A> through the MLD Report, so it forwards the multicast packet on eth0 to host A +4.4) Host A successfully receives the multicast packet from host B! h3. Scenario E: Multicast to host on node with a bridged-in querier

1 0

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

07 Sep '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit b30aa3a65893c5132388faa3ac05134eecd0b279 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat Aug 31 20:55:27 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- b30aa3a65893c5132388faa3ac05134eecd0b279 .../Multicast-IGMP-MLD-Report-Forwarding.textile | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index 3d6074e0..3ea88cec 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -129,7 +129,23 @@ Answer: yes **Learning:** -WIP +1) Bridged-in host A listens to a link-local multicast address <MC-LL-A> +2) Bridged-in host C on node Y floods an MLD Query through the mesh +2.1) Node Y sets and floods a WANT_ALL flag, because querier is potentially [[Multicast-optimizations-flags#Case-3-Shadowing-Multicast-Querier|"shadowing"]]. +2.2) Node X learns node Y's WANT_ALL flag. +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) batman-adv on node X will forward the MLD Report towards node Y, even with the multicast_rtr_only option enabled, as node Y has the WANT_ALL flag set. +3.4) batman-adv on node Y learns about <MC-LL-A> through the TT +3.5) br0 on node Y learns that a listener for <MC-LL-A> is behind bat0 and then forwards the MLD Report further towards the querier on eth0, as required by RFC4541 + +**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 heard of <MC-LL-B> and will forward the multicast packet towards bat0, as required by RFC4541 +... +Packet arrives at bridged-in host A h3. Scenario E: Multicast to host on node with a bridged-in querier

1 0

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

07 Sep '24

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

1 0

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

07 Sep '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit cce9016fa62cd340b9ce40595a0570ac067f22e2 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat Aug 31 20:24:19 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- cce9016fa62cd340b9ce40595a0570ac067f22e2 batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile | 2 ++ 1 file changed, 2 insertions(+) diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index a79341f1..1b13114e 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -11,6 +11,8 @@ 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. + h3. Scenario A: Multicast to host on node without querier h4. Scenario A, Overview:

1 0

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

07 Sep '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit a00abf889a8561d0955c5e4d5fda8dc669fe4739 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat Aug 31 20:21:15 2024 +0000 doc: batman-adv/Multicast-IGMP-MLD-Report-Forwarding >--------------------------------------------------------------- a00abf889a8561d0955c5e4d5fda8dc669fe4739 .../Multicast-IGMP-MLD-Report-Forwarding.textile | 30 +++++++++++++++++++--- 1 file changed, 26 insertions(+), 4 deletions(-) diff --git a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile index a785f36a..a79341f1 100644 --- a/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile +++ b/batman-adv/Multicast-IGMP-MLD-Report-Forwarding.textile @@ -112,14 +112,36 @@ C) Run a bridged-in multicast router (which supports MRD) on node Y (disadvantag D) Send report not just to multicast routers, but also to queriers (not implemented) E) 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 +h3. Scenario D: Multicast from host on node with a bridged-in querier h4. Scenario D, Overview: -_Can bridged-in host A send multicast to bridged-in host B?_ +!mld-to-mcast-routers-only-scenario-D-overview.png! +_Can bridged-in host B send multicast to bridged-in host A?_ h4. Scenario D, Analysis: Answer: yes + +!mld-to-mcast-routers-only-scenario-D.png! + +**Learning:** + +WIP + +h3. Scenario E: Multicast to host on node with a bridged-in querier + +h4. Scenario E, Overview: + +!mld-to-mcast-routers-only-scenario-E-overview.png! +_Can bridged-in host B send multicast to bridged-in host A?_ + +h4. Scenario E, Analysis: + +Answer: yes + +!mld-to-mcast-routers-only-scenario-E.png! + +**Learning:** + +WIP \ No newline at end of file

1 0

[doc] backup-redmine,main: doc: batman-adv/mld-to-mcast-routers-only-scenario-D.dia (2e844666)
by postmaster＠open-mesh.org 07 Sep '24

07 Sep '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit 2e84466631ad25be6284e46bc3a2fff973d9e522 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat Aug 31 20:14:25 2024 +0000 doc: batman-adv/mld-to-mcast-routers-only-scenario-D.dia >--------------------------------------------------------------- 2e84466631ad25be6284e46bc3a2fff973d9e522 batman-adv/mld-to-mcast-routers-only-scenario-D.dia | Bin 0 -> 3748 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/batman-adv/mld-to-mcast-routers-only-scenario-D.dia b/batman-adv/mld-to-mcast-routers-only-scenario-D.dia new file mode 100644 index 00000000..15e974cd Binary files /dev/null and b/batman-adv/mld-to-mcast-routers-only-scenario-D.dia differ

1 0

[doc] backup-redmine,main: doc: batman-adv/mld-to-mcast-routers-only-scenario-D.png (af21a31d)
by postmaster＠open-mesh.org 07 Sep '24

07 Sep '24

Repository : ssh://git@diktynna/doc On branches: backup-redmine,main >--------------------------------------------------------------- commit af21a31dbf0486ce7716e820f0ce87fed02345fa Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Sat Aug 31 20:14:25 2024 +0000 doc: batman-adv/mld-to-mcast-routers-only-scenario-D.png >--------------------------------------------------------------- af21a31dbf0486ce7716e820f0ce87fed02345fa batman-adv/mld-to-mcast-routers-only-scenario-D.png | Bin 0 -> 82182 bytes 1 file changed, 0 insertions(+), 0 deletions(-) diff --git a/batman-adv/mld-to-mcast-routers-only-scenario-D.png b/batman-adv/mld-to-mcast-routers-only-scenario-D.png new file mode 100644 index 00000000..98a12d41 Binary files /dev/null and b/batman-adv/mld-to-mcast-routers-only-scenario-D.png differ

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits September 2024