commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

Start a nNew thread

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Experience (56d232de)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo (8ceb9cf4)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Tweaking (dda94dff)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo (661208f9)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Gsoc2011-ideas: initial, very short notes of ideas (b230e1ca)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit b230e1ca95972b1152100582080e80a251af48bc Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue Feb 15 22:08:46 2011 +0000 doc: open-mesh/Gsoc2011-ideas: initial, very short notes of ideas >--------------------------------------------------------------- b230e1ca95972b1152100582080e80a251af48bc open-mesh/Gsoc2011-ideas.textile | 49 ++++++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) diff --git a/open-mesh/Gsoc2011-ideas.textile b/open-mesh/Gsoc2011-ideas.textile new file mode 100644 index 00000000..e0da03bb --- /dev/null +++ b/open-mesh/Gsoc2011-ideas.textile @@ -0,0 +1,49 @@ += Google Summer of Code 2011 - Ideas = + +== batman-adv == +Categories + Usecases to improve: +* Increasing Robustness +* Improving Mobility / Convergence Speed +* Improving Indoor performance +* Improving VoIP group multicast performance +* ... + + +Tasks: +* Improve broadcast data performance (dynamic number of rebroadcast, MPR like optimizations, ...) +* (link layer?) FEC, ARQ module (maybe create a separate kernel module, port also the link layer fragmentation to this module so other protocols might use it?) +* Dynamic OGM/NDP intervals +* Dead-node fast path switching +* Link quality / Packet delivery ratio measurement improvements + -> weighted/exponential moving average + -> testing / performance measurements of / improving NDP, find and improve "performance bottlenecks" +* Multicast Optimization Algorithm enhancements + -> implement reactive tracker packet mode + -> decrease latency of reactive tracker packet mode: attaching small data packets to tracker packet, if MTU fits (otherwise broadcast) in react. mode? ...? + -> ultimately, make proactive tracker mode obsolete + -> optimize number of rebroadcasts (we have the info about the number of next hop nodes) + -> don't send tracker packets if <= 1 destination or > 50%25 of all nodes are destinations + -> Enhance HNA, host network announcements, improvement scheme to also support MCAs, multicast announcements + -> ... +* Implement a suitable solution against hidden node broadcast packet problem (time slots, multiple interfaces, channel switching (extra module?), ...) +* Implement a suitable congestion avoidance mechanism for batman's control packets (different queues for control and data packets, time slots, ...) +* Unit test infrastructure (Implementation centric tesitng, simulator using Linux VMs to test different topologies or administrative changes? Code centric unit tests ...) +* Separate routing algorithm from routing infrastructure (ultimately, allow user space routing protocols to interact with kernel routing framework) +* Bonding improvements: + -> Add checks for links' capacities (detect full queues etc.) to gain performance of IF1 + IF2 + ... instead of min(IF1, IF2, ...) (example to have 1gbit/s (ethernet) + 100mbit/s (802.11n wifi) instead of just the minimum of all interfaces) + -> Improve bonding mode gain (seems to be just 66%25 efficiency with TCP due to reordering problem?) +* IPv6 stateless autoconf GW solution (playing with TTL of broadcast packets, use router preference option in RA (RFC4191)?) +* Further HNA roaming improvements +* Network Coding? + +== batctl == +* Enhance live link quality monitoring: bisect -> dot-files -> graphs -> to (live) video? (+ adding horst tool information, wifi interface stats?) +* Add further info to batman-adv vis servers/clients for debugging networks +* bisect, include initial state +* live vis in map (HTML5 + Openstreetmap?) + +== misc == +* multiple interface support in Mesh 3D +* ap51flash GUI; ap51flash multi-flash on single interface +* Android/Maemo/Meego porting + _maintenance_! +* Cooperative work with Pidgin guys? (video/audio/file-transfer/bonjour in pidgin and improving its + batman-adv's combined performance in a mesh network?) \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Gsoc2011-ideas: fix layout (8fac85a6)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit 8fac85a6c62beaa2ab141d96cb0791acc5663f99 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue Feb 15 22:10:37 2011 +0000 doc: open-mesh/Gsoc2011-ideas: fix layout >--------------------------------------------------------------- 8fac85a6c62beaa2ab141d96cb0791acc5663f99 open-mesh/Gsoc2011-ideas.textile | 54 ++++++++++++++++++++-------------------- 1 file changed, 27 insertions(+), 27 deletions(-) diff --git a/open-mesh/Gsoc2011-ideas.textile b/open-mesh/Gsoc2011-ideas.textile index e0da03bb..9fde1dfa 100644 --- a/open-mesh/Gsoc2011-ideas.textile +++ b/open-mesh/Gsoc2011-ideas.textile @@ -2,22 +2,22 @@ == batman-adv == Categories + Usecases to improve: -* Increasing Robustness -* Improving Mobility / Convergence Speed -* Improving Indoor performance -* Improving VoIP group multicast performance -* ... + * Increasing Robustness + * Improving Mobility / Convergence Speed + * Improving Indoor performance + * Improving VoIP group multicast performance + * ... Tasks: -* Improve broadcast data performance (dynamic number of rebroadcast, MPR like optimizations, ...) -* (link layer?) FEC, ARQ module (maybe create a separate kernel module, port also the link layer fragmentation to this module so other protocols might use it?) -* Dynamic OGM/NDP intervals -* Dead-node fast path switching -* Link quality / Packet delivery ratio measurement improvements + * Improve broadcast data performance (dynamic number of rebroadcast, MPR like optimizations, ...) + * (link layer?) FEC, ARQ module (maybe create a separate kernel module, port also the link layer fragmentation to this module so other protocols might use it?) + * Dynamic OGM/NDP intervals + * Dead-node fast path switching + * Link quality / Packet delivery ratio measurement improvements -> weighted/exponential moving average -> testing / performance measurements of / improving NDP, find and improve "performance bottlenecks" -* Multicast Optimization Algorithm enhancements + * Multicast Optimization Algorithm enhancements -> implement reactive tracker packet mode -> decrease latency of reactive tracker packet mode: attaching small data packets to tracker packet, if MTU fits (otherwise broadcast) in react. mode? ...? -> ultimately, make proactive tracker mode obsolete @@ -25,25 +25,25 @@ Tasks: -> don't send tracker packets if <= 1 destination or > 50%25 of all nodes are destinations -> Enhance HNA, host network announcements, improvement scheme to also support MCAs, multicast announcements -> ... -* Implement a suitable solution against hidden node broadcast packet problem (time slots, multiple interfaces, channel switching (extra module?), ...) -* Implement a suitable congestion avoidance mechanism for batman's control packets (different queues for control and data packets, time slots, ...) -* Unit test infrastructure (Implementation centric tesitng, simulator using Linux VMs to test different topologies or administrative changes? Code centric unit tests ...) -* Separate routing algorithm from routing infrastructure (ultimately, allow user space routing protocols to interact with kernel routing framework) -* Bonding improvements: + * Implement a suitable solution against hidden node broadcast packet problem (time slots, multiple interfaces, channel switching (extra module?), ...) + * Implement a suitable congestion avoidance mechanism for batman's control packets (different queues for control and data packets, time slots, ...) + * Unit test infrastructure (Implementation centric tesitng, simulator using Linux VMs to test different topologies or administrative changes? Code centric unit tests ...) + * Separate routing algorithm from routing infrastructure (ultimately, allow user space routing protocols to interact with kernel routing framework) + * Bonding improvements: -> Add checks for links' capacities (detect full queues etc.) to gain performance of IF1 + IF2 + ... instead of min(IF1, IF2, ...) (example to have 1gbit/s (ethernet) + 100mbit/s (802.11n wifi) instead of just the minimum of all interfaces) -> Improve bonding mode gain (seems to be just 66%25 efficiency with TCP due to reordering problem?) -* IPv6 stateless autoconf GW solution (playing with TTL of broadcast packets, use router preference option in RA (RFC4191)?) -* Further HNA roaming improvements -* Network Coding? + * IPv6 stateless autoconf GW solution (playing with TTL of broadcast packets, use router preference option in RA (RFC4191)?) + * Further HNA roaming improvements + * Network Coding? == batctl == -* Enhance live link quality monitoring: bisect -> dot-files -> graphs -> to (live) video? (+ adding horst tool information, wifi interface stats?) -* Add further info to batman-adv vis servers/clients for debugging networks -* bisect, include initial state -* live vis in map (HTML5 + Openstreetmap?) + * Enhance live link quality monitoring: bisect -> dot-files -> graphs -> to (live) video? (+ adding horst tool information, wifi interface stats?) + * Add further info to batman-adv vis servers/clients for debugging networks + * bisect, include initial state + * live vis in map (HTML5 + Openstreetmap?) == misc == -* multiple interface support in Mesh 3D -* ap51flash GUI; ap51flash multi-flash on single interface -* Android/Maemo/Meego porting + _maintenance_! -* Cooperative work with Pidgin guys? (video/audio/file-transfer/bonjour in pidgin and improving its + batman-adv's combined performance in a mesh network?) \ No newline at end of file + * multiple interface support in Mesh 3D + * ap51flash GUI; ap51flash multi-flash on single interface + * !Android/Maemo/Meego porting + _maintenance_! + * Cooperative work with Pidgin guys? (video/audio/file-transfer/bonjour in pidgin and improving its + batman-adv's combined performance in a mesh network?) \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Gsoc2011-ideas (b11ec587)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit b11ec5875592a01860c665b44bcbb418c9fc41db Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Tue Feb 15 22:12:09 2011 +0000 doc: open-mesh/Gsoc2011-ideas >--------------------------------------------------------------- b11ec5875592a01860c665b44bcbb418c9fc41db open-mesh/Gsoc2011-ideas.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/Gsoc2011-ideas.textile b/open-mesh/Gsoc2011-ideas.textile index 9fde1dfa..ec11e5f9 100644 --- a/open-mesh/Gsoc2011-ideas.textile +++ b/open-mesh/Gsoc2011-ideas.textile @@ -6,7 +6,7 @@ Categories + Usecases to improve: * Improving Mobility / Convergence Speed * Improving Indoor performance * Improving VoIP group multicast performance - * ... + * Improving nomadic scenarios (circular + chain topology) Tasks:

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Tweaking (f00494c5)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo: continue with release v2011.0.0 (b1af0506)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit b1af05062a0ff2e6b3d67f64a127bdf2a0441c54 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Jan 29 21:37:02 2011 +0000 doc: batman-adv/Release-todo: continue with release v2011.0.0 >--------------------------------------------------------------- b1af05062a0ff2e6b3d67f64a127bdf2a0441c54 batman-adv/Release-todo.textile | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index b36cab9f..0a9da914 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -13,18 +13,18 @@ This page contains a checklist of things that need to be done for a release. '''Code''' - * [ ] make sure all code contains the release version strings + * [x] make sure all code contains the release version strings * [x] update copyright years (if needed) * [x] remove dead code (if any) * [x] check against kernel versions * [x] check that maint branch is merged in next * [x] check for open patches on the ml - * [ ] git tag release + * [x] git tag release '''Documentation''' - * [ ] build changelog + * [x] build changelog * [x] update README * [ ] write release announcement * [ ] update wiki documentation @@ -32,8 +32,8 @@ This page contains a checklist of things that need to be done for a release. '''Release''' - * [ ] build package tar.gz and generate checksums - * [ ] move packages/checksums to stable/sources / create symlinks from releases + * [x] build package tar.gz and generate checksums + * [x] move packages/checksums to stable/sources / create symlinks from releases * [ ] update download links in the trac downloads page * [ ] send release mail * [ ] update IRC channel topic @@ -47,7 +47,7 @@ This page contains a checklist of things that need to be done for a release. '''Aftershow''' - * [ ] Merge differences (README, CHANGELOG, ...) into master branch - * [ ] Merge current next into maint (must be fast-forward or pre-tagging steps were done wrong) + * [x] Merge differences (README, CHANGELOG, ...) into master branch + * [x] Merge current next into maint (must be fast-forward or pre-tagging steps were done wrong) * [ ] Get patches for next release from master-rebase/batctl-rebase repository * [ ] Rebase patches in next on top of linux-next and send it to kernel maintainers for future kernels

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Understand-your-batman-adv-network (96ecd609)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

Repository : ssh://git@open-mesh.org/doc On branches: backup-redmine/2017-07-13,master >--------------------------------------------------------------- commit 96ecd6090d82f50ec82d095b56a945687a547220 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sat Jan 29 22:07:52 2011 +0000 doc: batman-adv/Understand-your-batman-adv-network >--------------------------------------------------------------- 96ecd6090d82f50ec82d095b56a945687a547220 .../Understand-your-batman-adv-network.textile | 98 +++++++++++++++------- 1 file changed, 70 insertions(+), 28 deletions(-) diff --git a/batman-adv/Understand-your-batman-adv-network.textile b/batman-adv/Understand-your-batman-adv-network.textile index df33d567..1ea1cade 100644 --- a/batman-adv/Understand-your-batman-adv-network.textile +++ b/batman-adv/Understand-your-batman-adv-network.textile @@ -1,77 +1,119 @@ -= Understand your B.A.T.M.A.N. Advanced network = -{{{ -#!div style="width: 46em; text-align: justify" +h1. Understand your B.A.T.M.A.N. Advanced network -This document assumes you have created a batman-adv network and are interested in finding out how batman routes the traffic from node to node, getting an access to the whole network topology and/or wish understand why batman is doing what it is doing. Batman provides a set of debug tools and debug tables which aim to facilitate this task. Explaining the routing decisions / various routing optimizations are not in the scope of this document. Links to complementary documents will be provided if available.[[BR]] -__Note__: Although this document focusses on the "raw" debugfs interface you always can use batctl for a more convenient access to the data. This document assumes debugfs was mounted at /sys/kernel/debug/. Please adjust the given examples if your system mounts the filesystem somewhere else. The batctl tool will automatically mount debugfs whenever you try to access functionality that require it. This document also assumes that you created a mesh cloud "bat0". [wiki:tweaking-batman-adv This page] provides background information on how to handle mesh clouds. +<pre> +<code class="div"> -=== Tables === +This document assumes you have created a batman-adv network and are interested in finding out how batman routes the traffic from node to node, getting an access to the whole network topology and/or wish understand why batman is doing what it is doing. Batman provides a set of debug tools and debug tables which aim to facilitate this task. Explaining the routing decisions / various routing optimizations are not in the scope of this document. Links to complementary documents will be provided if available. -'''originator table''' + ++Note+: Although this document focusses on the "raw" debugfs interface you always can use batctl for a more convenient access to the data. This document assumes debugfs was mounted at /sys/kernel/debug/. Please adjust the given examples if your system mounts the filesystem somewhere else. The batctl tool will automatically mount debugfs whenever you try to access functionality that require it. This document also assumes that you created a mesh cloud "bat0". [[tweaking-batman-adv|This page]] provides background information on how to handle mesh clouds. + + +h3. Tables + + +*originator table* Each batman node maintains a list of all other nodes in the network and remembers in which direction to send the packets if data should be transmitted. The direction manifests itself in the form of the "best next neighbor" which basically is the next step towards the destination. You can retrieve batman's internal originator table by reading the originators file. The printed table begins with a header line with some more or less useful status data, followed by the data. Each line contains information regarding a specific originator: -{{{ +<pre> <originator> <last-seen> <TQ (transmit quality) value towards the originator> <next best hop> <outgoing iface> <alternative best next hops> -}}} +</code></pre> Sample output: -{{{ +<pre> cat /sys/kernel/debug/batman_adv/bat0/originators -Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ... [B.A.T.M.A.N. adv 0.3.0-alpha, MainIF/MAC: eth0/fe:fe:00:00:01:01 (bat0)] +Originator last-seen (#/255) Nexthop [outgoingIF]: Potential nexthops ... [B.A.T.M.A.N. adv 0.3.0-alpha, [[MainIF]]/MAC: eth0/fe:fe:00:00:01:01 (bat0)] fe:fe:00:00:02:01 0.360s (133) fe:fe:00:00:02:01 [ eth0]: fe:fe:00:00:02:01 (133) -}}} +</code></pre> -'''translation tables''' +*translation tables* To let non-batman nodes use the mesh infrastructure easily, batman-adv introduced mac translation tables: When a batman-adv node detects that a client wishes to communicate over the mesh it will store the client's mac address in the local translation table and flood the network with the information that this mac address / client is attached to this batman-adv node. As soon as other nodes wish to send data to the client, they will search the client's mac in the mesh-wide (global) translation table, to find the corresponding batman-adv node. Then the data gets transmitted to the batman node first which then relays it to the client. The local translation table (mac addresses announced by this host) can be found in the transtable_local file: -{{{ +<pre> cat /sys/kernel/debug/batman_adv/bat0/transtable_local Locally retrieved addresses (from bat0) announced via HNA: - * a2:e1:e8:69:cf:bc -}}} +* fe:fe:00:00:01:01 +</code></pre> + +Every batman node announces at least one mac address - the mac of the batX interface. -Every batman node announces at least one mac address - the mac of the batX interface. [[BR]] The global translation table (mac addresses announced by other hosts) can be found in the transtable_global file: -{{{ +<pre> cat /sys/kernel/debug/batman_adv/bat0/transtable_global Globally announced HNAs received via the mesh bat0: - * fe:29:b9:c2:93:6a via fe:fe:00:00:02:01 -}}} +* fe:fe:00:00:01:01 via fe:fe:00:00:02:01 +</code></pre> Each line contains the announced mac address and the mac of the batman node announcing it. -=== ICMP === +*Gateway table* + +The gateway table lists all available batman-adv gateways in this network (see the [[batman-adv-gateways|gateway documentation]] to learn how to use this feature). Each line contains information about a specific gateway: + +<pre> +<selection symbol> + <gateway> + <TQ (transmit quality) value towards the gateway> + <next best hop> + <outgoing iface> + <gateway class - announced throughput> +</code></pre> + +For example: +<pre> + Gateway (#/255) Nexthop [outgoingIF]: gw_class ... [B.A.T.M.A.N. adv devel 1886, [[MainIF]]/MAC: eth0/fe:fe:00:00:03:01 (bat0)] + fe:fe:00:00:01:01 (233) fe:fe:00:00:01:01 [ eth0]: 41 - 2048KBit/512KBit +=> fe:fe:00:00:02:01 (243) fe:fe:00:00:02:01 [ eth0]: 41 - 2048KBit/512KBit +</code></pre> + +*Softinterface neighbor table* + +This table is part of the [[bridge-loop-avoidance|bridge loop avoidance]] code and contains all nodes that have been detected as being part of the same bridge. The currently selected 'gateway to the LAN' is marked with the '=>' symbol. + +<pre> +cat /sys/kernel/debug/batman_adv/bat0/softif_neigh +Softif neighbor list (bat0) +=> fe:fe:00:00:02:01 (vid: 1) +</code></pre> + + +h3. ICMP + Traditional network debugging tools based on the ICMP protocol such as ping or traceroute won't be able to perform their duties as expected. All traffic in the mesh will be transported to the destination transparently, so that higher protocols do not notice the number of hops or the route. This is one of the main reasons why you can roam around without breaking your connection. To provide the same type of diagnosis tools, batman-adv has an own simplified version of ICMP integrated in the protocol. Via debugfs it is possible to inject IMCP packets which behave very similar to their layer3 counterpart. The icmp socket file /sys/kernel/debug/batman_adv/bat0/icmp_socket can't be used with cat/echo directly, since it expects binary data. The batctl tool offers a ping / traceroute like interface that make use of this icmp socket interface. Please read the batctl manpage or the README file to learn how to use it or to see examples. -=== Logging === -Batman-adv offers extended logging to understand & debug the routing protocol internals. After you activated debugging at compile time (instructions can be found in [http://www.open-mesh.org/browser/trunk/batman-adv/README the README file]) and the appropriate log level has been set (read about the log levels [wiki:tweaking-batman-adv here]) you can retrieve the logs by simply reading the 'log' file: +h3. Logging + + +Batman-adv offers extended logging to understand & debug the routing protocol internals. After you activated debugging at compile time (instructions can be found in "the README file":http://www.open-mesh.org/browser/trunk/batman-adv/README) and the appropriate log level has been set (read about the log levels [[tweaking-batman-adv|here]]) you can retrieve the logs by simply reading the 'log' file: -{{{ +<pre> cat /sys/kernel/debug/batman_adv/bat0/log [ 418] Sending own packet (originator fe:fe:00:00:02:01, seqno 643, TQ 255, TTL 50, IDF off) on interface eth0 [fe:fe:00:00:02:01] [ 418] Received BATMAN packet via NB: fe:fe:00:00:01:01, IF: eth0 [fe:fe:00:00:02:01] (from OG: fe:fe:00:00:02:01, via prev OG: fe:fe:00:00:02:01, seqno 643, tq 245, TTL 49, V 12, IDF 1) [ 418] Drop packet: originator packet from myself (via neighbor) [..] -}}} +</code></pre> The log is a circular ring buffer and will continue writing messages as soon as they become available. -=== Visualization === -Despite its decentral nature batman-adv offers an easy way to access topology information that can be visualized. The [wiki:VisAdv visualization document] covers the necessary steps in detail. -}}} +h3. Visualization + + +Despite its decentral nature batman-adv offers an easy way to access topology information that can be visualized. The [[VisAdv|visualization document]] covers the necessary steps in detail. +</code></pre>

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017