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/WikiStart (d515c7b7)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/BATMANConcept (278b0ed8)
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 278b0ed86f52f6aaac5885aafdd9fe8aecb287d8 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun Nov 9 18:07:26 2008 +0000 doc: open-mesh/BATMANConcept >--------------------------------------------------------------- 278b0ed86f52f6aaac5885aafdd9fe8aecb287d8 open-mesh/BATMANConcept.textile | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/open-mesh/BATMANConcept.textile b/open-mesh/BATMANConcept.textile new file mode 100644 index 00000000..f0b0bc5f --- /dev/null +++ b/open-mesh/BATMANConcept.textile @@ -0,0 +1,18 @@ +'''B.A.T.M.A.N. O V E R V I E W''' + + +The problem with classical routing protocols is that they are typically not well suited for wireless ad-hoc networks. This is because such networks are unstructured, dynamically change their topology, and are based on an inherently unreliable medium. + +OLSR, the currently most employed protocol for such scenarios, has undergone a number of changes from its original specification in order to deal with the challenges imposed by city-wide wireless mesh networks. While some of its components proved to be unsuitable in practice (like MPR and Hysterese) new mechanisms have been added (like Fish-eye and ETX). However, due to the constant growth of existing community mesh networks and because of the inherent requirement of a link-state algorithm to recalculate the whole topology-graph (a particularly challenging task for the limited capabilities of embedded router HW), the limits of this algorithm have become a challenge. Recalculating the whole topology graph once in an actual mesh with 450 nodes takes several seconds on a small embedded CPU. + +The approach of the B.A.T.M.A.N algorithm is to divide the knowledge about the best end-to-end paths between nodes in the mesh to all participating nodes. Each node perceives and maintains only the information about the best next hop towards all other nodes. Thereby the need for a global knowledge about local topology changes becomes unnecessary. Additionally, an event-based but timelessfootnote{timeless in the sense that B.A.T.M.A.N never schedules nor timeouts topology information for optimising it's routing decisions} flooding mechanism prevents the accruement of contradicting topology information (the usual reason for the existence of routing loops) and limits the amount of topology messages flooding the mesh (thus avoiding overly overhead of control-traffic). The algorithm is designed to deal with networks that are based on unreliable links. + +The protocol algorithm of B.A.T.M.A.N can be described (simplified) as follows. Each node transmits broadcast messages (we call them originator messages or OGMs?) to inform the neighboring nodes about it's existence. These neighbors are re-broadcasting the OGMs? according to specific rules to inform their neighbors about the existence of the original initiator of this message and so on and so forth. Thus the network is flooded with originator messages. OGMs? are small, the typical raw packet size is 52 byte including IP and UDP overhead. OGMs? contain at least the address of the originator, the address of the node transmitting the packet, a TTL and a sequence number. + +OGMs? that follow a path where the quality of wireless links is poor or saturated will suffer from packetloss or delay on their way through the mesh. Therefore OGMs? that travel on good routes will propagate faster and more reliable. + +In order to tell if a OGM has been received once or more than once it contains a sequence number, given by the originator of the OGM. Each node re-broadcasts each received OGM at most once and only those received from the neighbor which has been identified as the currently best next hop (best ranking neighbor) towards the original initiator of the OGM. + +This way the OGMs? are flooded selectively through the mesh and inform the receiving nodes about other node's existence. A node X will learn about the existence of a node Y in the distance by receiving it's OGMs?, when OGMs? of node Y are rebroadcasted by it's single hop neighbors. If node X has more than one neighbor, it can tell by the number of originator messages it receives quicker and more reliable via one of its single hop neighbors, which neighbor it has to choose to send data to the distant node. + +The algorithm then selects this neighbor as the currently best next hop to the originator of the message and configures its routing table respectively.

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download (e0855846)
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 e085584674caed0f168f84007717e9e735f96514 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun Nov 9 18:16:42 2008 +0000 doc: open-mesh/Download >--------------------------------------------------------------- e085584674caed0f168f84007717e9e735f96514 open-mesh/Download.textile | 38 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile new file mode 100644 index 00000000..3dd2379d --- /dev/null +++ b/open-mesh/Download.textile @@ -0,0 +1,38 @@ += 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]. + +We are offering sources and precompiled binaries and packages for different platforms and for the stable and the development branch. However, please use the stable branch for your public infrastructure unless you know exactly what you are doing and are prepared for the big unknown. + +=== B.A.T.M.A.N. web interface package === + +The B.A.T.M.A.N. web interface package for the freifunk firmware as well as the latest stable batmand packages can be found in the ipkg repository at [http://freifunk.schmudde.com/ipkg/ freifunk.schmudde.com]. Therefore, if you are using freifunk firmware, the most convenient way to get B.A.T.M.A.N. running is probably to add the line +''src lui http://freifunk.schmudde.com/ipkg/'' to the file ''/etc/ipkg.conf'' on your WRT and then do an ''ipkg update'' and ''ipkg install batmand'' and ''ipkg install freifunk-batman'' (if not already installed you may also need the packages kmod-tun and libpthread ). Afterwards you can use the web interface to configure and observe batman. + +=== Download Released Source Code === + * '''The latest stable B.A.T.M.A.N. is batman-0.3''': [http://downloads.open-mesh.org/batman/stable/sources/batman-0.3.tar.gz batman-0.3.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/batman-0.3.tar.gz.md5 md5] [http://downloads.open-mesh.org/batman/stable/sources/batman-0.3.tar.gz.sha1 sha1] [http://downloads.open-mesh.org/batman/stable/sources/batman-0.3.tar.gz.sig sig] + * The latest version of the vis server is [http://downloads.open-mesh.org/batman/stable/sources/vis-0.3.tar.gz vis-0.3.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/vis-0.3.tar.gz.md5 md5] [http://downloads.open-mesh.org/batman/stable/sources/vis-0.3.tar.gz.sha1 sha1] [http://downloads.open-mesh.org/batman/stable/sources/vis-0.3.tar.gz.sig sig] + * The latest version of batman-adv is [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland-… batman-adv-kernelland-0.1-beta.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland-… md5] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland-… sha1] [http://downloads.open-mesh.org/batman/stable/sources/batman-adv-kernelland-… sig] + +If you find any bugs, please contribute by adding a New Ticket. +=== SVN Access === +You can check out our SVN repository and the various batman branches + + * upcoming B.A.T.M.A.N. 0.3.1 branch: [[BR]]{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman/}}} + * B.A.T.M.A.N. experimental (BMX) branch: [[BR]]{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman-experimental/}}} + * B.A.T.M.A.N. advanced: [[BR]]{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman-adv-kernelland/batma… + * battool (for B.A.T.M.A.N. advanced): [[BR]]{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/battool/}}} + * Visualization server: check out the complete repository, cd into vis (we're using symlinks here ...) + +=== Download precompiled Binaries === +There are various pre-compiled binaries available: + + * [http://downloads.open-mesh.org/batman/stable/wrt-freifunk/batmand_0.3-curre… mipsel OpenWRT/Whiterussian Freifunk] + * [http://downloads.open-mesh.org/batman/stable/wrt-freifunk/batmand_0.3-curre… WRT-Freifunk] + * [http://downloads.open-mesh.org/batman/stable/zaurus-akita Zaurus-Akita] + * [http://downloads.open-mesh.org/batman/stable/netgear-kamikaze Netgear-Kamikaze] + * [http://downloads.open-mesh.org/batman/stable/meshcube/ Meshcube (static)] + * [http://downloads.open-mesh.org/batman/stable/i386 i386 (static)] + * [http://downloads.open-mesh.org/batman/stable/fonera fonera (static)] + * [http://downloads.open-mesh.org/batman/stable/fonera-kamikaze fonera-kamikaze] + * [http://downloads.open-mesh.org/batman/stable/buffalo-freifunk/batmand_0.3-c… buffalo-freifunk] + * [http://downloads.open-mesh.org/batman/stable/armv5te armv5te (static)]

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/InternetTuning (833437c9)
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 833437c909438c9cc4a88726593580d2b36416fe Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun Nov 9 17:58:00 2008 +0000 doc: batmand/InternetTuning >--------------------------------------------------------------- 833437c909438c9cc4a88726593580d2b36416fe batmand/InternetTuning.textile | 91 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 91 insertions(+) diff --git a/batmand/InternetTuning.textile b/batmand/InternetTuning.textile new file mode 100644 index 00000000..78f25845 --- /dev/null +++ b/batmand/InternetTuning.textile @@ -0,0 +1,91 @@ +'''Gateway''' + +Batman offers to announce the avaibility of an internet connection. You can use the gateway class option (-g down/up) to tell batman how much bandwidth is available. You can specify the download and upload speed - batman will choose the nearest gateway class to represent your speed and propagate it in the network. The following examples should illustrate the usage: + +batmand -g 5000 [interface] + +batmand -g 5000kbit [interface] + +batmand -g 5mbit [interface] + +batmand -g 5mbit/1024 [interface] + +batmand -g 5mbit/1024kbit [interface] + +batmand -g 5mbit/1mbit [interface] + +The syntax is very flexible and allows all these values to become gateway class 49. + +Of course, you should enter the values which represent your connection speeds. + +Your gateway will open a new tunnel interface gate0 and sets up the correct routing entries. All batman internet clients will connect to the gateway which gives them a free IP for their own gate0 interface. The traffic to the gateway is encapsulated in UDP packets and sent to port 4307 (it should not be blocked by the firewall). On the way back from the internet the gateway also encapsulates the traffic. + +That behaviour allows the gateway maintainer to distinguish between traffic inside the mesh and traffic which should go to the internet. All filtering / caching / traffic shaping can be done on the gate0 interface. + +Additionally, you have to make sure that the gateway allows forwarding and that the firewall masquerades all traffic coming through gate0. + + +'''GatewayClient''' + +You can tell batman to watch out for announced gateways and connect to them via the routing class option (-r). This option allows you to influence which gateway will be chosen. Currently, there are 3 modes available: + +batmand -r 1 [interface]: + +This mode is called "fast internet connection" because it considers the link quality and the advertised gateway class before choosing the gateway. Once a gateway is chosen and the tunnel is established batman will try to keep the tunnel open as long as possible to not break your stateful connections. + +batmand -r 2 [interface]: + +This mode only considers the link quality towards the gateway while choosing it. Therefore it is named "stable internet connection". It also will keep the tunnel open as long as possible. + +batmand -r 3 [interface]: + +This mode also considers the link quality only but it will destroy the established tunnel as soon as another gateway with a better link quality is found (fast-switching). + +batmand -r (number between 3 and 256) [interface]: + +This mode also considers the link quality only but switches to another gateway as soon as this gateway has a TQ value which is $number better than the currently selected gateway (late-switching). + +After a gateway is chosen batman will create a gate0 interface and tries to get an IP from the gateway. If you plan to attach non-batman clients to your batman internet client you have to masquerade all outgoing packets on interface gate0. + +The tunnel architecture allows batman to observe the internet connection because all traffic is going through the tunnel. If batman notices that the currently selected gateway does not forward the traffic into the internet it will disconnect from that gateway and choose another gateway. + + +'''Tuning''' + +To be more flexible and better integrate into different setups and environments batman has a runtime interface which you can connect to. You can change batmans behaviour on the fly and adapt to changing requirements. + +For example you announce internet but you discover that your internet connection is down, so you can tell batman to stop announcing the gateway class: + +batmand -c -g 0 + +You could even say: I try to get my internet over that mesh as well: + +batmand -c -r 1 + +Later you deactivate it again and reactivate your gateway announcement: + +batmand -c -r 0 && batmand -c -g 5000 + +Or in one step: batmand -c -g 5000 + +If you know that you want to use a particular gateway you can use the preferred gateway option (-p) to specify it. If batman finds the given gateway it will use it otherwise it will choose a gateway according to the routing class (routing class 1 is default if none is given). + +For example: batmand -c -p 1.2.3.4 + +The preferred gateway option can also be given at startup time. + +If you have many users connected to your gateway you will experience a higher CPU load on the gateway because it has to maintain tunnel connections to numerous gateway clients at the same time. To reduce the load you can use the batgat kernel module which will do the tunneling from within the kernel space. You can load it like any other kernel module. Have a look in your kernel logs to see its boot up messages: + +batgat: [init_module:96] batgat loaded rv959 + +batgat: [init_module:97] I was assigned major number 252. To talk to + +batgat: [init_module:98] the driver, create a dev file with 'mknod /dev/batgat c 252 0'. + +batgat: [init_module:99] Remove the device file and module when done. + +Now the module is loaded but inactive. When you start batmand the daemon will automatically look for a file '/dev/batgat' to communicate with the kernel module in order to activate it. This file should be generated by the kernel if you have devfs (on linux 2.4) or udev (on linux 2.6) running. You can create the file by yourself as mentionned in the logs if it was not generated. When batmand finds this file the kernel module will be used. + +Attention: Do not hardcode the major number in your scripts. This number is assigned by the kernel and may differ from system to system, even from boot to boot. You can retrieve the current number from the proc filesystem: + +cat /proc/devices | grep batgat \ No newline at end of file

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017