commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: attachments/asym_path.png (dd239513)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: attachments/new_neigh.png (beb1ac0d)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Routing_scenarios (1128bdd2)
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 (12d2c33a)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Wiki (c3a40d61)
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 c3a40d61dbf51b215e85fbd4dfdc2445c4e3c519 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Tue Nov 30 01:36:15 2010 +0000 doc: batman-adv/Wiki >--------------------------------------------------------------- c3a40d61dbf51b215e85fbd4dfdc2445c4e3c519 batman-adv/Wiki.textile | 34 +++++++++++++++++++++------------- 1 file changed, 21 insertions(+), 13 deletions(-) diff --git a/batman-adv/Wiki.textile b/batman-adv/Wiki.textile index 0e26e004..9545b7c3 100644 --- a/batman-adv/Wiki.textile +++ b/batman-adv/Wiki.textile @@ -1,28 +1,36 @@ -= B.A.T.M.A.N. advanced = -{{{ -#!div style="width: 46em; text-align: justify" +h1. B.A.T.M.A.N. advanced -B.A.T.M.A.N. advanced (often referenced as batman-adv) is an implementation of the B.A.T.M.A.N. routing protocol in form of a linux kernel module operating on layer 2. The rest of this document will explain the conceptual details and their implications. If you are looking for explanations how to use the module, please consult our [wiki:batman-adv-quick-start-guide quick start guide]. -=== Layer 2 ? === +<pre> +<code class="div"> + +B.A.T.M.A.N. advanced (often referenced as batman-adv) is an implementation of the B.A.T.M.A.N. routing protocol in form of a linux kernel module operating on layer 2. The rest of this document will explain the conceptual details and their implications. If you are looking for explanations how to use the module, please consult our [[batman-adv-quick-start-guide|quick start guide]]. + + +h3. Layer 2 ? + Most other wireless routing protocol implementations (e.g. the batman daemon) operate on layer 3 which means they exchange routing information by sending UDP packets and bring their routing decision into effect by manipulating the kernel routing table. Batman-adv operates entirely on ISO/OSI Layer 2 - not only the routing information is transported using raw ethernet frames but also the data traffic is handled by batman-adv. It encapsulates and forwards all traffic until it reaches the destination, hence emulating a virtual network switch of all nodes participating. Therefore all nodes appear to be link local and are unaware of the network's topology as well as unaffected by any network changes. This design bears some interesting characteristics: - * network-layer agnostic - you can run whatever you wish on top of batman-adv: IPv4, IPv6, DHCP, IPX .. - * nodes can participate in a mesh without having an IP - * easy integration of non-mesh (mobile) clients (no manual HNA fiddling required) - * roaming of non-mesh clients - * optimizing the data flow through the mesh (e.g. interface alternating, multicast, forward error correction, etc) +* network-layer agnostic - you can run whatever you wish on top of batman-adv: IPv4, IPv6, DHCP, IPX .. +* nodes can participate in a mesh without having an IP +* easy integration of non-mesh (mobile) clients (no manual HNA fiddling required) +* roaming of non-mesh clients +* optimizing the data flow through the mesh (e.g. interface alternating, multicast, forward error correction, etc) + + +h3. A kernel module ? -=== A kernel module ? === A layer 2 routing protocol also has to handle the data traffic because usually one can't route/forward ethernet packets. Processing packets in userland is very expensive in terms of CPU cycles, as each packet has to be read() and write() to the kernel and back, which limits the sustainable bandwidth especially on low-end devices. To have good support for these devices as well, we implemented batman-adv as a kernel driver. It introduces a negligible packet processing overhead even under a high load. -=== batctl ? === + +h3. batctl ? + To still have a handy tool to configure & debug the batman-adv kernel module, the batctl tool was developed. It offers a convenient interface to all the module's settings as well as status information. It also contains a layer 2 version of ping, traceroute and tcpdump, since the virtual network switch is completely transparent for all protocols above layer 2. -}}} +</code></pre>

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Tweaking (ed26d2b4)
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 ed26d2b4024f9580a426d63bbf514e2b729d77d8 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Nov 22 01:11:09 2010 +0000 doc: batman-adv/Tweaking >--------------------------------------------------------------- ed26d2b4024f9580a426d63bbf514e2b729d77d8 batman-adv/Tweaking.textile | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) diff --git a/batman-adv/Tweaking.textile b/batman-adv/Tweaking.textile index 5760e328..089a163d 100644 --- a/batman-adv/Tweaking.textile +++ b/batman-adv/Tweaking.textile @@ -9,7 +9,7 @@ __Note__: Although this document focusses on the "raw" /sys/ configuration inter === Interface handling === -To better understand the background of the new interface configuration concept (as of batman-adv 2010.0.0), it is helpful to see in which direction batman-adv is heading: Until now, batman aggregated all configured interface into a single mesh cloud (manifested in a single bat0 interface). In the future it will be possible to let a single mesh node participate in mutliple mesh clouds at the same time which makes it necessary to assign interfaces to individual mesh clouds and having multiple batX interfaces. Although the "multiple mesh cloud" feature is not complete yet, the configuration interface support is already available. +To better understand the background of the new interface configuration concept (as of batman-adv 2010.0.0), it is helpful to see in which direction batman-adv is heading: Until now, batman aggregated all configured interface into a single mesh cloud (manifested in a single bat0 interface). As of 2010.2.0 it is possible to let a single mesh node participate in mutliple mesh clouds at the same time which makes it necessary to assign interfaces to individual mesh clouds and having multiple batX interfaces. After loading batman-adv, it will scan your systems interfaces to search for compatible interfaces. Once found, it will create subfolders in the /sys/class/net/<iface> directories of each supported interface, e.g. @@ -21,7 +21,7 @@ iface_status mesh_iface If an interface does not have the "batman_adv" subfolder it probably is not supported. Not supported interfaces are: loopback, non-ethernet and batman's own interfaces.[[BR]] __Note__: After the module was loaded it will continuously watch for new interfaces to verify the compatibility. There is no need to reload the module if you plug your USB wifi adapter into your machine after batman advanced was initially loaded. -To activate a given interface on a mesh cloud simply write the mesh clouds interface name into its "mesh_iface" file inside the batman_adv subfolder. Since the "multiple mesh cloud" feature is currently disabled, you can only write "bat0" but later on you can freely choose the interface name. +To activate a given interface on a mesh cloud simply write the mesh clouds interface name into its "mesh_iface" file inside the batman_adv subfolder. You can freely choose the interface name but for the sake of simplicity we continue to use "bat0". {{{ echo bat0 > /sys/class/net/eth0/batman_adv/mesh_iface @@ -46,7 +46,7 @@ After having added interfaces to a mesh cloud, batman-adv automatically creates {{{ ls /sys/class/net/bat0/mesh/ -aggregated_ogms bonding log_level orig_interval vis_mode +aggregated_ogms bonding fragmentation log_level orig_interval vis_mode }}} '''aggregate originator messages''' @@ -71,6 +71,19 @@ cat /sys/class/net/bat0/mesh/bonding disabled }}} +'''fragmentation''' + +Available since: batman-adv 2010.2.0 + +Batman-adv has a built-in layer 2 fragmentation for unicast data flowing through the mesh which will allow to run batman-adv over interfaces / connections that don't allow to increase the MTU beyond the standard Ethernet packet size of 1500 bytes. When the fragmentation is enabled batman-adv will automatically fragment over-sized packets and defragment them on the other end. Per default fragmentation is enabled and inactive if the packet fits but it is possible to deactivate the fragmentation entirely. + +__Note__: Although the fragmentation is rather handy it comes with a severe performance penalty (as every fragmentation does), therefore it should be avoided to make use of this feature whenever possible. + +{{{ +cat /sys/class/net/bat0/mesh/fragmentation +enabled +}}} + '''log level''' Available since: batman-adv 2010.1.0 (if debugging has been compiled-in)

1 0

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

14 Jul '17

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017