commits January 2023

commits@lists.open-mesh.org

1 participants
283 discussions

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Network-wide-multi-link-optimization: switch to non-controversy git branch names (bd4b70a6)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit bd4b70a683ee278b3c2e266f29f6a27763d0055e Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:19:59 2022 +0000 doc: batman-adv/Network-wide-multi-link-optimization: switch to non-controversy git branch names >--------------------------------------------------------------- bd4b70a683ee278b3c2e266f29f6a27763d0055e batman-adv/Network-wide-multi-link-optimization.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Network-wide-multi-link-optimization.textile b/batman-adv/Network-wide-multi-link-optimization.textile index f70ca47e..db34970d 100644 --- a/batman-adv/Network-wide-multi-link-optimization.textile +++ b/batman-adv/Network-wide-multi-link-optimization.textile @@ -82,7 +82,7 @@ The default originator table can be found at its original place, using ''batctl <pre> root@OpenWrt:/# batctl o -[B.A.T.M.A.N. adv master-b82b9b2, MainIF/MAC: eth0/fe:f0:00:00:02:01 (bat0 BATMAN_IV)] +[B.A.T.M.A.N. adv main-b82b9b2, MainIF/MAC: eth0/fe:f0:00:00:02:01 (bat0 BATMAN_IV)] Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ... fe:f1:00:00:03:01 0.350s (254) fe:f1:00:00:03:01 [ eth1]: fe:f1:00:00:03:01 (254) fe:f1:00:00:01:01 0.800s (255) fe:f1:00:00:01:01 [ eth1]: fe:f1:00:00:01:01 (255)

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/NetworkCoding: switch to non-controversy git branch names (f9ebe02f)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit f9ebe02fa1527994ccaa2c4ff4a491f2a6c6e2c1 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:20:17 2022 +0000 doc: batman-adv/NetworkCoding: switch to non-controversy git branch names >--------------------------------------------------------------- f9ebe02fa1527994ccaa2c4ff4a491f2a6c6e2c1 batman-adv/NetworkCoding.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/NetworkCoding.textile b/batman-adv/NetworkCoding.textile index bab9e049..e76a3d3f 100644 --- a/batman-adv/NetworkCoding.textile +++ b/batman-adv/NetworkCoding.textile @@ -24,7 +24,7 @@ There are a few requirements to your setup, if you want to benefit from network * For network coding to work, it is required to have an enabled and working promiscuous mode on all nodes, as promiscuity is used to both overhear packets and receive network coded packets. Be aware that many wireless devices have no functioning promiscuous mode, so some testing might be required. * Your wireless device must support an MTU of 1546, as the batman-adv header for network coded packets carries more information than usual unicast packets. -To enable network coding, enable it a compile time (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/master:/README.external to learn how to set the compile option). It can be turned off at runtime with batctl: +To enable network coding, enable it a compile time (consult "the README.external file":https://git.open-mesh.org/batman-adv.git/blob/refs/heads/main:/README.external to learn how to set the compile option). It can be turned off at runtime with batctl: <pre> # batctl nc 0 </pre>

1 0

[doc] backup-redmine/2023-01-14,main: doc: open-mesh/Joker: switch to non-controversy git branch names (608d8f00)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 608d8f00fe3f9debca60311f1e9b7efac79c16c9 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:19:43 2022 +0000 doc: open-mesh/Joker: switch to non-controversy git branch names >--------------------------------------------------------------- 608d8f00fe3f9debca60311f1e9b7efac79c16c9 open-mesh/Joker.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/Joker.textile b/open-mesh/Joker.textile index 0df54589..5df0b37b 100644 --- a/open-mesh/Joker.textile +++ b/open-mesh/Joker.textile @@ -17,7 +17,7 @@ Release tarballs as well as snapshots are available: * git web directory: https://git.open-mesh.org/joker.git * git download: git clone git://git.open-mesh.org/joker.git -* snapshot:https://git.open-mesh.org/joker.git/snapshot/refs/heads/master.tar… +* snapshot:https://git.open-mesh.org/joker.git/snapshot/refs/heads/main.tar.gz h2. Usage

1 0

[doc] backup-redmine/2023-01-14,main: doc: alfred/Batadv-vis (8d4aed56)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 8d4aed56180761143af697c5352b23b483fb4f30 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:19:05 2022 +0000 doc: alfred/Batadv-vis >--------------------------------------------------------------- 8d4aed56180761143af697c5352b23b483fb4f30 alfred/Batadv-vis.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/alfred/Batadv-vis.textile b/alfred/Batadv-vis.textile index e1b4e45c..ddaa8c92 100644 --- a/alfred/Batadv-vis.textile +++ b/alfred/Batadv-vis.textile @@ -2,6 +2,6 @@ h1. Batadv-vis batadv-vis can be used to visualize your batman-adv mesh network. It read the neighbor information and local client table and distributes this information via alfred in the network. By gathering this local information, any vis node can get the whole picture of the network. -It allows output of different formats (json, graphviz) and replaces the in-kernel vis functionality found in older batman-adv kernel modules (<2014). See the sample picture below. For more information, please read the vis section of the "README":https://git.open-mesh.org/alfred.git/blob_plain/refs/heads/master:/README.rst or the "manpage":https://downloads.open-mesh.org/batman/manpages/batadv-vis.html for usage. +It allows output of different formats (json, graphviz) and replaces the in-kernel vis functionality found in older batman-adv kernel modules (<2014). See the sample picture below. For more information, please read the vis section of the "README":https://git.open-mesh.org/alfred.git/blob_plain/refs/heads/main:/README.rst or the "manpage":https://downloads.open-mesh.org/batman/manpages/batadv-vis.html for usage. !batman-adv-vis-example.png! \ No newline at end of file

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (7901c387)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 7901c387244daf878e3175166ac17772d4b0145e Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Wed Dec 14 17:34:02 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- 7901c387244daf878e3175166ac17772d4b0145e batman-adv/Multicast-Packet-Type.textile | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index b971d7db..fa64266a 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -106,7 +106,10 @@ h3. #Num Dests size ** If limit of entries were reached, we could just send another mcast packet? (~6*256 = 1536). Or do we want to be prepared for jumbo frames? -** -> going for 2 bytes / potential jumbo frame support + +--- + +-> going for 2 bytes / potential jumbo frame support h3. Non ideal splits

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (97c9b23f)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 97c9b23ff9abdf56bc39d27d3437d5fbd65c04b0 Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Wed Dec 14 17:33:40 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- 97c9b23ff9abdf56bc39d27d3437d5fbd65c04b0 batman-adv/Multicast-Packet-Type.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index a7687219..b971d7db 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -118,7 +118,7 @@ A batman-adv node currently cannot anticipate this for optimized splitting, as i --- --> Going for just one multicast packet instead of up to mcast_fanout to start with. +-> Going for just one multicast packet instead of up to mcast_fanout to start with, for simplicity. h3. Fragmentation / MTUs:

1 0

[doc] backup-redmine/2023-01-14,main: doc: batman-adv/Multicast-Packet-Type (9255ac0b)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 9255ac0b2dc8e34e68ecbaa01fd34d359120a127 Author: Linus L��ssing <linus.luessing(a)c0d3.blue> Date: Wed Dec 14 17:42:32 2022 +0000 doc: batman-adv/Multicast-Packet-Type >--------------------------------------------------------------- 9255ac0b2dc8e34e68ecbaa01fd34d359120a127 batman-adv/Multicast-Packet-Type.textile | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/batman-adv/Multicast-Packet-Type.textile b/batman-adv/Multicast-Packet-Type.textile index fa64266a..e1b9cab9 100644 --- a/batman-adv/Multicast-Packet-Type.textile +++ b/batman-adv/Multicast-Packet-Type.textile @@ -97,7 +97,6 @@ h2. Implementation Tasks # If yes, further check if number of batman-adv multicast per IP multicast packet is smaller than multicast fanout setting. So calculate MTU - sizeof(_Data_) - sizeof(multicast-packet-header) and divide by number of destinations (check Translation Table). If it exceeds multicast fanout then bail out and fall back to broadcast flooding. Otherwise continue: # - h2. Open questions, known issues, TODOs h3. #Num Dests size @@ -134,3 +133,13 @@ By default only apply multicast packet type if resulting packet is smaller than Solution B) Later ideally the fragmentation code would be able to split the payload within a multicast packet type, while leaving multicast packet type headers in tact. A node should still forward packets if due to this splitting the mcast-fanout limit were violated, to avoid packet loss. + +h3. Adding a sequence number? / How to avoid loops with tracker marking later? + +When later implementing a split control <-> data plane as originally envisioned, by allowing to send a multicast packet with only the tracker TVLV, without data. And caching this information to fill a multicast routing table. And then allowing to send a multicast packet without the tracker TVLV afterwards, there is the following issue: + +When first a path is marked through the tracker TVLV, then paths change due to OGM updates. And then a tracker packet marks such new paths then the merger of both the old and newly tracker marked paths could create routing loops, as the old path is not automatically invalidated. + +Solution: + +Don't mark paths. Instead use the tracker TVLV to fill a cache with the mcast/dests lists and assign a hash to this information. Then later send the multicast data with a TVLV containing only this hash instead of the full mcast/dests list. Therefore a specific list of destinations is still maintained and routing decisions still happen on the go, loopfree, instead of trying to a maintain a loopfree, adjacent multicast routing table. \ No newline at end of file

1 0

[doc] backup-redmine/2023-01-14,main: doc: devtools/Analyzing_virtual_network_packets: switch to non-controversy git branch names (2c2de875)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 2c2de8755cc534261bbe2af91acdd233a282c546 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:18:22 2022 +0000 doc: devtools/Analyzing_virtual_network_packets: switch to non-controversy git branch names >--------------------------------------------------------------- 2c2de8755cc534261bbe2af91acdd233a282c546 devtools/Analyzing_virtual_network_packets.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/devtools/Analyzing_virtual_network_packets.textile b/devtools/Analyzing_virtual_network_packets.textile index 74f995ca..1da64470 100644 --- a/devtools/Analyzing_virtual_network_packets.textile +++ b/devtools/Analyzing_virtual_network_packets.textile @@ -2,7 +2,7 @@ h1. Analyzing virtual network packets h2. Wireshark -The easiest way to get the traffic of a virtual machine is via the tap interfaces. It is recommended to use the newest wireshark version (git master branch) to get support for batman-adv's packet format. Wireshark can then be started manually on a specific tap interface: +The easiest way to get the traffic of a virtual machine is via the tap interfaces. It is recommended to use the newest wireshark version (git main branch) to get support for batman-adv's packet format. Wireshark can then be started manually on a specific tap interface: <pre><code class="shell"> wireshark -k -i tap1

1 0

[doc] backup-redmine/2023-01-14,main: doc: open-mesh/News-draft: switch to non-controversy git branch names (1b703fc6)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit 1b703fc60d9b7bc4bf52c5bd4e73270631ba8efd Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:18:41 2022 +0000 doc: open-mesh/News-draft: switch to non-controversy git branch names >--------------------------------------------------------------- 1b703fc60d9b7bc4bf52c5bd4e73270631ba8efd open-mesh/News-draft.textile | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/open-mesh/News-draft.textile b/open-mesh/News-draft.textile index 23833e72..9f05d285 100644 --- a/open-mesh/News-draft.textile +++ b/open-mesh/News-draft.textile @@ -25,7 +25,7 @@ and to all those that supported us with good advice or rigorous testing: h2. batman-adv <pre> -$ git describe origin/master +$ git describe origin/main v2022.2-12-g402531de $ range=v2022.2..v2022.2-12-g402531de $ git shortlog --email --no-merges "${range}" @@ -75,7 +75,7 @@ bugfixes h2. batctl <pre> -$ git describe origin/master +$ git describe origin/main v2022.2-1-gb4052ae $ range=v2022.2..v2022.2-1-gb4052ae $ git shortlog --email --no-merges "${range}" @@ -109,7 +109,7 @@ bugfixes h2. alfred <pre> -$ git describe origin/master +$ git describe origin/main v2022.2-6-g678c732 $ range=v2022.2..v2022.2-6-g678c732 $ git shortlog --email --no-merges "${range}"

1 0

[doc] backup-redmine/2023-01-14,main: doc: alfred/Alfred-gpsd: switch to non-controversy git branch names (ee8142e7)
by postmaster＠open-mesh.org 14 Jan '23

14 Jan '23

Repository : ssh://git@diktynna/doc On branches: backup-redmine/2023-01-14,main >--------------------------------------------------------------- commit ee8142e76dc1c3840f47ae054d1fe014b6810e0e Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Dec 17 13:18:51 2022 +0000 doc: alfred/Alfred-gpsd: switch to non-controversy git branch names >--------------------------------------------------------------- ee8142e76dc1c3840f47ae054d1fe014b6810e0e alfred/Alfred-gpsd.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/alfred/Alfred-gpsd.textile b/alfred/Alfred-gpsd.textile index 937b005c..6ec79a16 100644 --- a/alfred/Alfred-gpsd.textile +++ b/alfred/Alfred-gpsd.textile @@ -2,4 +2,4 @@ h1. Alfred-gpsd Alfred-gpsd can be used to distibute GPS location information about your batman-adv mesh network. This information could be, for example, combined with Vis to visualize your mesh topology with true geographic layout. For mobile or nomadic nodes, Alfred-gpsd, can get location information from gpsd. Alternatively, a static location can be passed on the command line, which is useful for static nodes without a GPS. -For more information, please read the alfred-gpsd section of the "README":https://git.open-mesh.org/alfred.git/blob_plain/refs/heads/master:/README.rst or the "manpage":https://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html for usage. \ No newline at end of file +For more information, please read the alfred-gpsd section of the "README":https://git.open-mesh.org/alfred.git/blob_plain/refs/heads/main:/README.rst or the "manpage":https://downloads.open-mesh.org/batman/manpages/alfred-gpsd.html for usage. \ No newline at end of file

1 0

← Newer
1
...
5
6
7
8
9
10
11
...
29
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits January 2023