commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Filing: change path to manpage (d2af068d)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Tweaking: change path to manpage (b331665a)
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 b331665a0c32008c8e9df011a9f89477b9e0eb5c Author: Sven Eckelmann <sven(a)narfation.org> Date: Tue Mar 22 12:11:29 2011 +0000 doc: batman-adv/Tweaking: change path to manpage >--------------------------------------------------------------- b331665a0c32008c8e9df011a9f89477b9e0eb5c batman-adv/Tweaking.textile | 127 ++++++++++++++++++++++++-------------------- 1 file changed, 68 insertions(+), 59 deletions(-) diff --git a/batman-adv/Tweaking.textile b/batman-adv/Tweaking.textile index d2e9dbc7..caf1c25a 100644 --- a/batman-adv/Tweaking.textile +++ b/batman-adv/Tweaking.textile @@ -1,178 +1,187 @@ -= Tweaking B.A.T.M.A.N. Advanced = -{{{ -#!div style="width: 46em; text-align: justify" +h1. Tweaking B.A.T.M.A.N. Advanced -This document aims to provide a high level overview about the individual settings batman-adv allows you to make, in order to tweak its behaviour. If you are trying to find out what these various sysfs files or batctl options are good for, this is the right document for you. Some of the features require extended explanation & examples which is not the scope of this document. Links to complementary documents will be provided if available.[[BR]] -__Note__: Although this document focusses on the "raw" /sys/ configuration interface you always can use batctl for a more convenient access to the settings. +<pre> +<code class="div"> + +This document aims to provide a high level overview about the individual settings batman-adv allows you to make, in order to tweak its behaviour. If you are trying to find out what these various sysfs files or batctl options are good for, this is the right document for you. Some of the features require extended explanation & examples which is not the scope of this document. Links to complementary documents will be provided if available. + + ++Note+: Although this document focusses on the "raw" /sys/ configuration interface you always can use batctl for a more convenient access to the settings. + + +h3. Interface handling -=== 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). 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. -{{{ +<pre> ls /sys/class/net/eth0/batman_adv/ iface_status mesh_iface -}}} +</code></pre> -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. +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. + ++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. You can freely choose the interface name but for the sake of simplicity we continue to use "bat0". -{{{ +<pre> echo bat0 > /sys/class/net/eth0/batman_adv/mesh_iface -}}} +</code></pre> Repeat this step for all interfaces you wish to add. All interfaces using the same mesh cloud interface belong into the same mesh cloud. Now batman-adv starts using/broadcasting on this/these interface(s). You can check the interface's status by reading the "iface_status" file inside the batman-adv folder: -{{{ +<pre> cat /sys/class/net/eth0/batman_adv/iface_status active -}}} +</code></pre> To deactivate an interface you have to write "none" into its "mesh_iface" file: -{{{ +<pre> echo none > /sys/class/net/eth0/batman_adv/mesh_iface -}}} +</code></pre> + + +h3. Mesh cloud handling -=== Mesh cloud handling === After having added interfaces to a mesh cloud, batman-adv automatically creates the appropriate batX mesh interface(s). Each of those interfaces receives a special "mesh" subfolder within their standard /sys/class/net/<iface> folder, e.g. -{{{ +<pre> ls /sys/class/net/bat0/mesh/ aggregated_ogms gw_bandwidth hop_penalty vis_mode bonding gw_mode log_level fragmentation gw_sel_class orig_interval -}}} +</code></pre> -'''aggregate originator messages''' +*aggregate originator messages* Available since: batman-adv 2010.0.0 In order to reduce the protocol overhead created to find all the participants in the network, batman has the ability to collect & aggregate these protocol messages (called originator messages or ogm) and sending them in a single packet instead of several small packets. This feature is enabled by default, since it is helpful in most cases. If you intend to run batman-adv in a highly mobile environment (for example cars) you might want to turn it off as it introduces a (normally negligible) network update delay. -{{{ +<pre> cat /sys/class/net/bat0/mesh/aggregated_ogms enabled -}}} +</code></pre> -'''bonding mode''' +*bonding mode* Available since: batman-adv 2010.1.0 -When running the mesh over multiple !WiFi interfaces per node batman-adv is capable of optimizing the traffic flow to gain maximum performance. Per default it operates in the "interface alternating" mode (which is suitable for most situations) that switches the !WiFi interface with each hop to avoid store & forward. Alternatively, batman-adv can be switched into "bonding mode" in which batman-adv is using all interfaces at the same time to send & receive data. However, this mode is only recommended in special one-hop cases. You can read about our [wiki:2010-06-13-wbm2010-bracciano alternate/bonding test results] to see what suits you best. +When running the mesh over multiple WiFi interfaces per node batman-adv is capable of optimizing the traffic flow to gain maximum performance. Per default it operates in the "interface alternating" mode (which is suitable for most situations) that switches the WiFi interface with each hop to avoid store & forward. Alternatively, batman-adv can be switched into "bonding mode" in which batman-adv is using all interfaces at the same time to send & receive data. However, this mode is only recommended in special one-hop cases. You can read about our [[2010-06-13-wbm2010-bracciano|alternatebonding test results]] to see what suits you best. -{{{ +<pre> cat /sys/class/net/bat0/mesh/bonding disabled -}}} +</code></pre> -'''fragmentation''' +*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. ++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. -{{{ +<pre> cat /sys/class/net/bat0/mesh/fragmentation enabled -}}} +</code></pre> -'''gateway bandwidth''' +*gateway bandwidth* Available since: batman-adv 2011.0.0 -The [wiki:batman-adv-gateways internet gateway support] allows each gateway to also announce its available internet bandwidth. Clients looking for the most suitable gateway to connect to receive this bandwidth announcement and can make use of it while choosing their gateway. Per default a bandwidth of 2048KBit/512KBit is assumed. Details regarding the syntax of the bandwidth setting can be found in the [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl manpage]. +The [[batman-adv-gateways|internet gateway support]] allows each gateway to also announce its available internet bandwidth. Clients looking for the most suitable gateway to connect to receive this bandwidth announcement and can make use of it while choosing their gateway. Per default a bandwidth of 2048KBit/512KBit is assumed. Details regarding the syntax of the bandwidth setting can be found in the "batctl manpage":http://downloads.open-mesh.org/batman/manpages/batctl.8.html. -__Note__: If a batman-adv node has not activated the gateway server mode this setting has no effect. ++Note+: If a batman-adv node has not activated the gateway server mode this setting has no effect. -{{{ +<pre> cat /sys/class/net/bat0/mesh/gw_bandwidth 2048KBit/512KBit -}}} +</code></pre> -'''gateway mode''' +*gateway mode* Available since: batman-adv 2011.0.0 A batman-adv node can either run in server mode (sharing its internet connection with the mesh) or in client mode (searching for the most suitable internet connection in the mesh) or having the gateway support disabled entirely (which is the default setting). Gateways can tweak the announced internet bandwidth via the gw_bandwidth sysfs file whereas clients can configure the manner in which batman-adv chooses its gateway via the gw_sel_class sysfs file. -__Note__: Please read the [wiki:batman-adv-gateways internet gateway documentation] to understand its interaction with DHCP. ++Note+: Please read the [[batman-adv-gateways|internet gateway documentation]] to understand its interaction with DHCP. -{{{ +<pre> cat /sys/class/net/bat0/mesh/gw_mode off -}}} +</code></pre> -'''gateway selection class''' +*gateway selection class* Available since: batman-adv 2011.0.0 -If multiple batman-adv gateways are available a batman-adv client node selects its best gateway based on certain criteria such as link quality / announced bandwidth / etc. The selection algorithm can be modified to best serve the requirements. The gateway selection class of '20' is the default value. All available gateway selection classes are thoroughly explained in the [http://downloads.open-mesh.org/batman/manpages/batctl.8.html batctl manpage]. +If multiple batman-adv gateways are available a batman-adv client node selects its best gateway based on certain criteria such as link quality / announced bandwidth / etc. The selection algorithm can be modified to best serve the requirements. The gateway selection class of '20' is the default value. All available gateway selection classes are thoroughly explained in the "batctl manpage":http://downloads.open-mesh.org/batman/manpages/batctl.8.html. -__Note__: If a batman-adv node has not activated the gateway client mode this setting has no effect. ++Note+: If a batman-adv node has not activated the gateway client mode this setting has no effect. -{{{ +<pre> cat /sys/class/net/bat0/mesh/gw_sel_class 20 -}}} +</code></pre> -'''hop penalty''' +*hop penalty* Available since: batman-adv 2011.0.0 The hop penalty setting allows to modify batman-adv's preference for multihop routes vs. short routes. The value is applied to the TQ of each forwarded OGM, thereby propagating the cost of an extra hop (the packet has to be received and retransmitted which costs airtime). A higher hop penalty will make it more unlikely that other nodes will choose this node as intermediate hop towards any given destination. On the hand, a lower hop penalty will result in longer routes because retransmissions are not penalized. The default hop penalty of '10' is a reasonable value for most setups and probably does not need to be changed. However, mobile nodes could choose a value of 255 (maximum value) to avoid being chosen as a router by other nodes. -{{{ +<pre> cat /sys/class/net/bat0/mesh/hop_penalty 10 -}}} +</code></pre> -'''log level''' +*log level* Available since: batman-adv 2010.1.0 (if debugging has been compiled-in) -The standard warning and error messages which help to setup & operate batman-adv are sent to the kernel log. However, batman-adv also offers extended logs that can be used to understand and/or debug the routing protocol. Keep in mind that it is necessary to activate debugging at compile time before you can use these facilities (consult [http://www.open-mesh.org/browser/trunk/batman-adv/README the README file] to learn how to set the compile option). Per default, the logging is deactivated (log level: 0), Enable log level '1' to log messages related to routing / flooding / broadcasting. Log level '2' only shows messages related to route or hna added / changed / deleted. Switch to log level '3' to get all log messages. +The standard warning and error messages which help to setup & operate batman-adv are sent to the kernel log. However, batman-adv also offers extended logs that can be used to understand and/or debug the routing protocol. Keep in mind that it is necessary to activate debugging at compile time before you can use these facilities (consult "the README file":http://www.open-mesh.org/browser/trunk/batman-adv/README to learn how to set the compile option). Per default, the logging is deactivated (log level: 0), Enable log level '1' to log messages related to routing / flooding / broadcasting. Log level '2' only shows messages related to route or hna added / changed / deleted. Switch to log level '3' to get all log messages. -{{{ +<pre> cat /sys/class/net/bat0/mesh/log_level 0 -}}} +</code></pre> -'''originator interval''' +*originator interval* Available since: batman-adv 2010.0.0 The value specifies interval (milliseconds) in which batman-adv floods the network with its protocol information. The default value of one message per second allows batman to recognize a route change (in its near neighborhood) within a timeframe of maximal one minute (most likely much sooner). In a very static environment (batman nodes are not moving, rare ups & downs of nodes) you might want to increase the value to save bandwidth. On the other hand, it might prove helpful to decrease the value in a highly mobile environment (e.g. the aforementioned cars) but keep in mind that this will drastically increase the traffic. Unless you experience problems with your setup, it is suggested you keep the default value. -{{{ +<pre> cat /sys/class/net/bat0/mesh/orig_interval 1000 -}}} +</code></pre> -'''visualizing the topology''' +*visualizing the topology* Available since: batman-adv 2010.0.0 -The vis_mode and vis_data files provide a system to visualize the batman-adv network. The [wiki:VisAdv visualizing the 2nd layer] and [wiki:VisOutput vis output] documents describes this system in detail, therefore no in-depth explanation is given here. [[BR]] +The vis_mode and vis_data files provide a system to visualize the batman-adv network. The [[VisAdv|visualizing the 2nd layer] and [wikiVisOutput vis output]] documents describes this system in detail, therefore no in-depth explanation is given here. + The default vis mode is "client" -{{{ +<pre> cat /sys/class/net/bat0/mesh/vis_mode client -}}} +</code></pre> which needs te be changed to "server" before the topology data can be read from the "vis_data" file. -}}} +</code></pre>

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Gateways: change path to manpage (512e2336)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Filing: change path to manpage (cfe67476)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/WikiStart (bb98eaea)
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 bb98eaea7f2ef17fce05edb236a54f724672e587 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sat Mar 26 16:53:26 2011 +0000 doc: open-mesh/WikiStart >--------------------------------------------------------------- bb98eaea7f2ef17fce05edb236a54f724672e587 open-mesh/WikiStart.textile | 62 ++++++++++++++++++++++++++------------------- 1 file changed, 36 insertions(+), 26 deletions(-) diff --git a/open-mesh/WikiStart.textile b/open-mesh/WikiStart.textile index c8de0e75..f953cdc8 100644 --- a/open-mesh/WikiStart.textile +++ b/open-mesh/WikiStart.textile @@ -1,29 +1,39 @@ -= Welcome to Open Mesh = -'''This page serves as development platform for a collection of tools to build free and open mesh networks.''' +h1. Welcome to Open Mesh + +*This page serves as development platform for a collection of tools to build free and open mesh networks.* ---- -= B.A.T.M.A.N. = + +h1. B.A.T.M.A.N. + B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is a routing protocol for multi-hop ad-hoc mesh networks. This is the main development website, we have source code, binary packages, documentation and further information available: -== News == - * '''17.Mar. 2011''' [wiki:2011-03-17-batman-adv-and-the-penguin Batman-adv and the Penguin join forces] - * '''29.Jan. 2011''' [wiki:2011-01-29-batman-adv-2011-0-0-release Batman-adv 2011.0.0 released] - * '''18.Jan. 2011''' [wiki:2011-01-18-wbmv4-announcement WBMv4 Announcement] - * '''12.Dec. 2010''' [wiki:2010-12-12-batman-v-status-update B.A.T.M.A.N. V status update] - * '''22.Nov. 2010''' [wiki:2010-11-21-batman-adv-2010-2-0-release Batman-adv 2010.2.0 released] - - * [wiki:news-archive news archive] -== Getting Started == - * [wiki:Download Download] - Get our latest releases, get access to our SVN repository - * [wiki:Contribute How to contribute] - How to report bugs, send comments, patches or suggestions -== Documentation == - * [wiki:BranchesExplained Branches explained] - learn about the B.A.T.M.A.N. flavours - * [wiki:UserDocs UserDocs] - understand how B.A.T.M.A.N. works - * [wiki:FAQ FAQ] - Frequently Asked Questions - * [wiki:Experience Experience] - Collection of links to B.A.T.M.A.N. press reviews, papers and projects using B.A.T.M.A.N. - * [wiki:Patches Patches] - contribution from others related to B.A.T.M.A.N. - * [wiki:batman-adv B.A.T.M.A.N. Advanced] - information about the Layer 2 version of B.A.T.M.A.N. - * [wiki:MailingList Mailing List]/[wiki:IRC IRC] - contact us ----- -== Other Projects on open-mesh.org == - * [wiki:FFTrace FFTrace] - freifunk traceroute tool - * [wiki:MeshLinux MeshLinux] - Linux distribution geared to build mesh supernodes \ No newline at end of file + +h2. News + +* *17.Mar. 2011* [[2011-03-17-batman-adv-and-the-penguin|Batman-adv and the Penguin join forces]] +* *29.Jan. 2011* [[2011-01-29-batman-adv-2011-0-0-release|Batman-adv 201100 released]] +* *18.Jan. 2011* [[2011-01-18-wbmv4-announcement|WBMv4 Announcement]] +* *12.Dec. 2010* [[2010-12-12-batman-v-status-update|BATMAN V status update]] +* *22.Nov. 2010* [[2010-11-21-batman-adv-2010-2-0-release|Batman-adv 201020 released]] + +* [[news-archive|news archive]] + +h2. Getting Started + +* [[Download|Download]] - Get our latest releases, get access to our SVN repository +* [[Contribute|How to contribute]] - How to report bugs, send comments, patches or suggestions + +h2. Documentation + +* [[BranchesExplained|Branches explained]] - learn about the B.A.T.M.A.N. flavours +* [[UserDocs|UserDocs]] - understand how B.A.T.M.A.N. works +* [[FAQ|FAQ]] - Frequently Asked Questions +* [[Experience|Experience]] - Collection of links to B.A.T.M.A.N. press reviews, papers and projects using B.A.T.M.A.N. +* [[Patches|Patches]] - contribution from others related to B.A.T.M.A.N. +* [[batman-adv|BATMAN Advanced]] - information about the Layer 2 version of B.A.T.M.A.N. +* [[MailingList|Mailing List]]/[[IRC|IRC]] - contact us + +h2. Other Projects on open-mesh.org + +* [[FFTrace|FFTrace]] - freifunk traceroute tool +* [[MeshLinux|MeshLinux]] - Linux distribution geared to build mesh supernodes \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (8d109e03)
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 8d109e037318ad0f0c1ef7da1523b2d798060f9f Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun Mar 20 22:50:55 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- 8d109e037318ad0f0c1ef7da1523b2d798060f9f open-mesh/BranchesExplained.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index bd21f768..b1d67c1f 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -34,7 +34,7 @@ Today, it is an independent project hosted at http://www.bmx6.net. [[BR]] Early 2007 some developers started experimenting with the idea of routing on layer 2 (Ethernet layer) instead of layer 3. As only little knowledge about routing on this low level was available at that time, a first prototype was developed, operating in userspace in form of a daemon but already using layer 2. To differentiate from the layer 3 routing daemon the suffix "adv" (spoken: advanced) was chosen - the batman-adv userspace daemon was born. It uses the routing algorithm of batman 0.3, but instead of sending UDP packets and manipulating routing tables, it provides a virtual network interface and transparently transports packets on its own. -However, the virtual interface in userspace imposed a significant overhead for low-end wireless access points which led to a re-implementation as a kernel module. The batman-adv userspace daemon has been removed, so today "batman-adv" refers to the kernel module only. Currently, most of the development happens around batman-adv. +However, the virtual interface in userspace imposed a significant overhead for low-end wireless access points which led to a re-implementation as a kernel module. The batman-adv userspace daemon has been removed, so today "batman-adv" refers to the kernel module only. Currently, most of the development happens around batman-adv which is part of the official Linux kernel since 2.6.38. To understand the implications of routing on layer 2, the [wiki:batman-adv batman-adv page] should be a good starting point. Further documentation is available in our [wiki:UserDocs docs] section.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BranchesExplained (a235e80d)
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 a235e80dfc0377fa7392fe14ededcfc807fc9829 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun Mar 20 22:50:55 2011 +0000 doc: open-mesh/BranchesExplained >--------------------------------------------------------------- a235e80dfc0377fa7392fe14ededcfc807fc9829 open-mesh/BranchesExplained.textile | 38 +++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/open-mesh/BranchesExplained.textile b/open-mesh/BranchesExplained.textile index b1d67c1f..e147f1a7 100644 --- a/open-mesh/BranchesExplained.textile +++ b/open-mesh/BranchesExplained.textile @@ -1,12 +1,16 @@ -= Branches Explained = -{{{ -#!div style="width: 46em; text-align: justify" +h1. Branches Explained + + +<pre> +<code class="div"> The batman project that started with a basic protocol and a single userspace routing daemon, attracted quite some attention over the years which led to many new ideas and concepts meant to improve the project. These ideas often resulted in proof-of-concept "branches" of which some turned out to be impractical and disappeared but others came to stay. As a consequence different names were created to distinguish these concepts as the name "batman" became a broader term for everything around the project. This page aims to shed some light on all these different names to make it easier to understand the differences. -=== numbers, numbers === + +h3. numbers, numbers + Whenever Roman numerals (as III or IV) are mentioned they refer to the version of B.A.T.M.A.N.'s routing algorithm and thus describe how the routing information are flooded and how they are handled to make the best routing decision possible. @@ -16,32 +20,42 @@ Example: batmand 0.2 uses the B.A.T.M.A.N. III routing algorithm. -=== batmand === -The batman userspace daemon has been the first implementation of the B.A.T.M.A.N. routing protocol. In the early stages of the project it allowed us to easily experiment with the design of the protocol but also to be used in real world deployments. It operates on layer 3 (IP layer) and offers everything you would expect from a standard routing daemon. Check our [wiki:UserDocs docs] section if you want to learn more about is capabilities.[[BR]] +h3. batmand + + +The batman userspace daemon has been the first implementation of the B.A.T.M.A.N. routing protocol. In the early stages of the project it allowed us to easily experiment with the design of the protocol but also to be used in real world deployments. It operates on layer 3 (IP layer) and offers everything you would expect from a standard routing daemon. Check our [[UserDocs|docs]] section if you want to learn more about is capabilities. + At the moment the batman daemon lacks development power (this branch is unmaintained since a while) as most developers moved on to one of the following branches. If you are interested to maintain the code base, feel free to contact us. -=== BMX === + +h3. BMX + Initially, the BMX branch was used to implement and test new features and concepts to overcome certain limitations of the routing algorithm. It started on the code base of batmand 0.3 but, over time, developed into a completely different direction, so that a re-integration became impossible. -Today, it is an independent project hosted at http://www.bmx6.net. [[BR]] +Today, it is an independent project hosted at http://www.bmx6.net. + + -=== batman-adv === +h3. batman-adv + Early 2007 some developers started experimenting with the idea of routing on layer 2 (Ethernet layer) instead of layer 3. As only little knowledge about routing on this low level was available at that time, a first prototype was developed, operating in userspace in form of a daemon but already using layer 2. To differentiate from the layer 3 routing daemon the suffix "adv" (spoken: advanced) was chosen - the batman-adv userspace daemon was born. It uses the routing algorithm of batman 0.3, but instead of sending UDP packets and manipulating routing tables, it provides a virtual network interface and transparently transports packets on its own. However, the virtual interface in userspace imposed a significant overhead for low-end wireless access points which led to a re-implementation as a kernel module. The batman-adv userspace daemon has been removed, so today "batman-adv" refers to the kernel module only. Currently, most of the development happens around batman-adv which is part of the official Linux kernel since 2.6.38. -To understand the implications of routing on layer 2, the [wiki:batman-adv batman-adv page] should be a good starting point. Further documentation is available in our [wiki:UserDocs docs] section. +To understand the implications of routing on layer 2, the [[batman-adv|batman-adv page] should be a good starting point Further documentation is available in our [wikiUserDocs docs]] section. + + +h3. batctl -=== batctl === As batman-adv operates in kernelland a handy tool to manage the module and debug the network became necessary. The batctl tool was created to fill that gap and, since then, has become a valuable companion of batman-adv. -}}} +</code></pre>

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download: Remove precompiled binaries (769c0e0a)
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 769c0e0a79a56269e85c270f07b14dc4d024e318 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sun Mar 20 23:12:36 2011 +0000 doc: open-mesh/Download: Remove precompiled binaries >--------------------------------------------------------------- 769c0e0a79a56269e85c270f07b14dc4d024e318 open-mesh/Download.textile | 83 ++++++++++++++++++++++++++++------------------ 1 file changed, 51 insertions(+), 32 deletions(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index b07af918..27c6595d 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -1,55 +1,74 @@ -= Download B.A.T.M.A.N. = -We are currently working on different branches. To get the details about the differences of these branches, see our [wiki:BranchesExplained Branches Explained page]. + +h1. Download B.A.T.M.A.N. + +We are currently working on different branches. To get the details about the differences of these branches, see our [[BranchesExplained|Branches Explained page]]. Please use the maint branch for your public infrastructure unless you know exactly what you are doing and are prepared for the big unknown. -=== Download Released Source Code === - * The latest version of [wiki:batman-adv batman-adv] is [http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-… batman-adv-2011.0.0.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-… md5] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-… sha1] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-… asc] - * The latest version of batctl (management and control tool for batman-adv) is [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.0.0… batctl-2011.0.0.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.0.0… md5] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.0.0… sha1] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.0.0… asc] - * The latest stable version of batmand is [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.ta… batman-0.3.2.tar.gz] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.ta… md5] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.ta… sha1] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.ta… asc] - * The latest version of the vis server for the batmand (package not needed for batman-adv) is [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz vis-0.3.2.tar.gz] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.g… md5] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.g… sha1] [http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.g… asc] +h3. Download Released Source Code + +* The latest version of [[batman-adv|batman-adv]] is "batman-adv-2011.0.0.tar.gz":http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2011.0.0.tar.gz "md5":http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2011.0.0.tar.gz.md5 "sha1":http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2011.0.0.tar.gz.sha1 "asc":http://downloads.open-mesh.org/batman/stable/sources/batman-adv/batman-adv-2011.0.0.tar.gz.asc +* The latest version of batctl (management and control tool for batman-adv) is "batctl-2011.0.0.tar.gz":http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.0.0.tar.gz "md5":http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.0.0.tar.gz.md5 "sha1":http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.0.0.tar.gz.sha1 "asc":http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2011.0.0.tar.gz.asc + +* The latest stable version of batmand is "batman-0.3.2.tar.gz":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz "md5":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.md5 "sha1":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.sha1 "asc":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/batman-0.3.2.tar.gz.asc +* The latest version of the vis server for the batmand (package not needed for batman-adv) is "vis-0.3.2.tar.gz":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz "md5":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz.md5 "sha1":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz.sha1 "asc":http://downloads.open-mesh.org/batman/releases/batman-0.3.2/vis-0.3.2.tar.gz.asc -If you are wondering whether batman-adv or batmand might suit your setup better, have a look at [wiki:batman-adv this page]. Please note that the development is focusing on batman-adv at the moment. +If you are wondering whether batman-adv or batmand might suit your setup better, have a look at [[batman-adv|this page]]. Please note that the development is focusing on batman-adv at the moment. -If you find any bugs, please [wiki:Contribute let us know]! +If you find any bugs, please [[Contribute|let us know]]! + + +h3. Subversion Repository Access -=== Subversion Repository Access === You can check out our SVN repository and the various batman branches - * [wiki:batman-adv B.A.T.M.A.N. advanced]: [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman-adv/}}}'' - * batctl (for B.A.T.M.A.N. advanced): check out the complete repository, cd into batctl (we're using symlinks here ...): [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/}}}'' - * complete repository: [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/}}}'' - * upcoming B.A.T.M.A.N. 0.4.0 branch '''(maintainer needed!)''': [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman/}}}'' - * Visualization server for B.A.T.M.A.N.: check out the complete repository, cd into vis (we're using symlinks here ...): [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/}}}'' +* [[batman-adv|BATMAN advanced]]: +<pre> +* batctl (for B.A.T.M.A.N. advanced): check out the complete repository, cd into batctl (we're using symlinks here ...): +<pre> +* complete repository: +<pre> +* upcoming B.A.T.M.A.N. 0.4.0 branch *(maintainer needed!)*: +<pre> +* Visualization server for B.A.T.M.A.N.: check out the complete repository, cd into vis (we're using symlinks here ...): +<pre> + -=== Git Repository Access === -Since we started integrating the batman-adv kernel module into the mainline Linux tree, we also maintain a git repository which contains the batman-adv maintenance branches. More information can be found [wiki:UsingBatmanGit on our git page]. +h3. Git Repository Access +Since we started integrating the batman-adv kernel module into the mainline Linux tree, we also maintain a git repository which contains the batman-adv maintenance branches. More information can be found [[UsingBatmanGit|on our git page]]. + + + +h3. batman-adv in the Linux tree -=== batman-adv in the Linux tree === Since linux 2.6.33 batman-adv is part of the official linux tree. You can build batman-adv along with your linux binary by simply selecting batman-adv in the Linux drivers section. If you use an older kernel or want to have access to the latest features you can checkout our SVN or git repository which still are backward compatible until 2.6.21. It follows an overview of linux versions and the batman-adv version they contain, so that you can easily pick the compatible batctl packages: - * linux 2.6.33 => batman-adv 0.2.0 (get batctl 0.2.0 from [http://downloads.open-mesh.org/batman/stable/sources/batctl/ here]) - * linux 2.6.34 => batman-adv 0.2.1 (get batctl 0.2.1 from [http://downloads.open-mesh.org/batman/stable/sources/batctl/ here]) - * linux 2.6.35 => batman-adv 2010.0.0 (get batctl 2010.0.0 from [http://downloads.open-mesh.org/batman/stable/sources/batctl/ here]) - * linux 2.6.36 => batman-adv 2010.1.0 (get batctl 2010.1.0 from [http://downloads.open-mesh.org/batman/stable/sources/batctl/ here]) - * linux 2.6.37 => batman-adv 2010.2.0 (get batctl 2010.2.0 from [http://downloads.open-mesh.org/batman/stable/sources/batctl/ here]) - * linux 2.6.38 => batman-adv 2011.0.0 (get batctl 2011.0.0 from [http://downloads.open-mesh.org/batman/stable/sources/batctl/ here]) +* linux 2.6.33 => batman-adv 0.2.0 (get batctl 0.2.0 from "here":http://downloads.open-mesh.org/batman/stable/sources/batctl/) +* linux 2.6.34 => batman-adv 0.2.1 (get batctl 0.2.1 from "here":http://downloads.open-mesh.org/batman/stable/sources/batctl/) +* linux 2.6.35 => batman-adv 2010.0.0 (get batctl 2010.0.0 from "here":http://downloads.open-mesh.org/batman/stable/sources/batctl/) +* linux 2.6.36 => batman-adv 2010.1.0 (get batctl 2010.1.0 from "here":http://downloads.open-mesh.org/batman/stable/sources/batctl/) +* linux 2.6.37 => batman-adv 2010.2.0 (get batctl 2010.2.0 from "here":http://downloads.open-mesh.org/batman/stable/sources/batctl/) +* linux 2.6.38 => batman-adv 2011.0.0 (get batctl 2011.0.0 from "here":http://downloads.open-mesh.org/batman/stable/sources/batctl/) + -=== Debian === +h3. Debian + Use apt-get (or any other dpkg frontend of choice) to install B.A.T.M.A.N. onto your debian machine. Following packages are available: - * [http://packages.debian.org/sid/batmand batmand] - batman 0.3.2 - * [http://packages.debian.org/sid/batman-adv-source batman-adv-source] - batman-advanced kernel 2011.0.0 module source (installable via [http://packages.debian.org/sid/module-assistant module-assistant]) - * [http://packages.debian.org/sid/batman-adv-dkms batman-adv-dkms] - batman-advanced kernel module 2011.0.0 dkms package to build new modules dynamically (half-automatic) - * [http://packages.debian.org/sid/batctl batctl] - batctl 2011.0.0 +* "batmand":http://packages.debian.org/sid/batmand - batman 0.3.2 +* "batman-adv-source":http://packages.debian.org/sid/batman-adv-source - batman-advanced kernel 2011.0.0 module source (installable via "module-assistant":http://packages.debian.org/sid/module-assistant) +* "batman-adv-dkms":http://packages.debian.org/sid/batman-adv-dkms - batman-advanced kernel module 2011.0.0 dkms package to build new modules dynamically (half-automatic) +* "batctl":http://packages.debian.org/sid/batctl - batctl 2011.0.0 + + +h3. Building [[OpenWRT]] packages -=== Building OpenWRT packages === -B.A.T.M.A.N. is also included in OpenWRT as a package. Download the extra package feed, link the batman folder into your main OpenWRT svn directory and use "make menuconfig" to select the B.A.T.M.A.N. flavor you intend to use. This enables you to integrate B.A.T.M.A.N. seamlessly into your builds (see [wiki:building-batman-adv-with-openwrt this page] for a detailed explanation). +B.A.T.M.A.N. is also included in [[OpenWRT]] as a package. Download the extra package feed, link the batman folder into your main [[OpenWRT]] svn directory and use "make menuconfig" to select the B.A.T.M.A.N. flavor you intend to use. This enables you to integrate B.A.T.M.A.N. seamlessly into your builds (see [[building-batman-adv-with-openwrt|this page]] for a detailed explanation). -More information about how to build the OpenWRT toolchain is available [http://wiki.openwrt.org/OpenWrtDocs/BuildingKamikazeHowTo here]. +More information about how to build the [[OpenWRT]] toolchain is available "here":http://wiki.openwrt.org/OpenWrtDocs/BuildingKamikazeHowTo.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download: Remove precompiled binaries (580fd513)
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