commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/New_papers (9005cc30)
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 9005cc30b6da3e99dcc54a4548903a39ec5a3292 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun May 2 22:19:58 2010 +0000 doc: open-mesh/New_papers >--------------------------------------------------------------- 9005cc30b6da3e99dcc54a4548903a39ec5a3292 open-mesh/New_papers.textile | 28 ++++++++++++++++++++++++++++ 1 file changed, 28 insertions(+) diff --git a/open-mesh/New_papers.textile b/open-mesh/New_papers.textile new file mode 100644 index 00000000..4e9de971 --- /dev/null +++ b/open-mesh/New_papers.textile @@ -0,0 +1,28 @@ +This is just a list of papers which need a review before going to the experience site: + += "free" papers = +=== Wi-Me - Wireless Mesh Network Implementation (K. Babu, L.M. Cortes-Pena, P. Shah, S.S. Krishnan) === + + Compares BATMAN and OLSR with a static routing scheme in a small test bed. + + * http://users.ece.gatech.edu/~cortes/files/Wi-Me.pdf + +=== Experimental evaluation of two open source solutions for wireless mesh routing at layer two (R.G. Garroppo, S. Giordano, L. Tavanti) === + + Compares batman-adv and open80211s in a small testbed. + + * http://wwwtlc.iet.unipi.it/research/ggt-iswpc10.pdf + +=== WMM - Wireless Mesh Monitoring === + + Introduction to WMMs and some implementations like AODV, OLSR, BATMAN ... + * http://www.gsd.inesc-id.pt/~ler/reports/ricardopinto-midterm.pdf + +=== more resources === + * find some more: http://scholar.google.com/scholar?start=20&q=BATMAN+OLSR&hl=en&as_sdt=2000 + += non-free papers = +need IEEE/ACM/Springer/etc accounts. Can anyone provide these papers? + * http://www.springerlink.com/content/p802p6k186328706/ + * http://www.computer.org/portal/web/csdl/doi/10.1109/AINA.2009.28 + * http://portal.acm.org/citation.cfm?id=1719404 \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Tweaking (e2c6b9d7)
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 e2c6b9d72b09fa2155f2c840aba455b91657b612 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun May 9 10:22:40 2010 +0000 doc: batman-adv/Tweaking >--------------------------------------------------------------- e2c6b9d72b09fa2155f2c840aba455b91657b612 batman-adv/Tweaking.textile | 89 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 89 insertions(+) diff --git a/batman-adv/Tweaking.textile b/batman-adv/Tweaking.textile new file mode 100644 index 00000000..333ae6ee --- /dev/null +++ b/batman-adv/Tweaking.textile @@ -0,0 +1,89 @@ + += Tweaking B.A.T.M.A.N. Advanced = + +{{{ +#!div style="width: 46em; text-align: justify" + +This document aims to provide a high level overview about the invidual 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. + +=== Interface handling === + +To better understand the background of the new interface configuration concept (as of batman-adv 0.2.2), 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. + +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. + +{{{ +ls /sys/class/net/eth0/batman_adv/ +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. + +{{{ +echo bat0 > /sys/class/net/eth0/batman_adv/mesh_iface +}}} + +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: +{{{ +cat /sys/class/net/eth0/batman_adv/iface_status +active +}}} + +To deactivate an interface you have to write "none" into its "mesh_iface" file: +{{{ +echo none > /sys/class/net/eth0/batman_adv/mesh_iface +}}} + +=== Mesh cloud handling === + +After having interfaces added to a mesh cloud, batman-adv automatically creates the appropiate batX mesh interface(s). Each of those interfaces receives a special "mesh" subfolder within their standard /sys/class/net/<iface> folder, e.g. + +{{{ +ls /sys/class/net/bat0/mesh/ +aggregate_ogm originators transtable_global vis_mode +orig_interval transtable_local vis_data +}}} + +'''aggregate originator messages''' + +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. + +{{{ +cat /sys/class/net/bat0/mesh/aggregate_ogm +status: enabled +commands: enable, disable, 0, 1 +}}} + +'''originator interval''' + +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. + +{{{ +cat /sys/class/net/bat0/mesh/orig_interval +status: 1000 +}}} + +'''visualizing the topology''' + +The vis_mode and vis_data files provide a system to visualize the batman-adv network. The [wiki:VisAdv visualizing the 2nd layer] document describes this system in detail, therefore no in depth explanation is given here. [[BR]] + +The default vis mode is "client" + +{{{ +cat /sys/class/net/bat0/mesh/vis_mode +status: client +commands: client, server, 0, 1 +}}} + +which needs te be changed to "server" before the topology data can be read from the "vis_data" file. + +}}} + +

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Troubleshooting (08f28db7)
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 08f28db722fde98f2fb9da1fb6868d8ed00e5068 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Wed Mar 31 17:45:31 2010 +0000 doc: batman-adv/Troubleshooting >--------------------------------------------------------------- 08f28db722fde98f2fb9da1fb6868d8ed00e5068 batman-adv/Troubleshooting.textile | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/batman-adv/Troubleshooting.textile b/batman-adv/Troubleshooting.textile index 1a995b2c..5abfa199 100644 --- a/batman-adv/Troubleshooting.textile +++ b/batman-adv/Troubleshooting.textile @@ -1,24 +1,24 @@ = B.A.T.M.A.N.-Adv Troubleshooting = ''B.A.T.M.A.N.-Adv does net work as expected, what can I do now?'' -First, try to minimise the complexity of your setup, i.e. just try to build a simple mesh network between two devices. Usually just following the [wiki/batman-adv-quick-start-guide quick-start-guide] is a good way to start with. +First, try to minimise the complexity of your setup, i.e. just try to build a simple mesh network between two devices. Usually just following the [wiki:batman-adv-quick-start-guide quick-start-guide] is a good way to start with. If you still can't get any setup working at all, go through this checklist: === Any warnings or errors in the kernel log? === -Check 'dmesg' for warnings, errors or crashes. If you are seeing a crash, write a [/report ticket] and post the log their, describe your setup and hardware, and ideally how this crash could be reproduced. If the kernel log is just showing cryptic numbers and you are building the kernel(-module) yourself (i.e. OpenWRT distro with [/wiki/building-batman-adv-with-openwrt this] article), enable kernel symbol table please (see its advanced section for enabling this)! +Check dmesg/logread/syslog for warnings, errors or kernel oopses. If you are seeing a kernel oops, write a [/report ticket] and post the log there, describe your setup and hardware, and ideally how this crash could be reproduced. If the kernel log is just showing cryptic numbers it will be difficult to help you. You can increase the chances of finding the bug by enabling the kernel symbol table which will translate these numbers to function names that can help developers to see what is happening. Please check the "advanced" section of [wiki:building-batman-adv-with-openwrt this article] to learn how to enable this functionality on OpenWRT. === Are both nodes having the same cell id? === -Check with 'iwconfig'. Some wifi drivers are a little buggy and do not always merge two ad-hoc cells, therefore you're usually best advised to chose and configure one manually (i.e. 'iwconfig wlan0 ap 02:XX:XX:XX:XX:XX'). If configuring a cell-id manually, you should set the 7th bit of the first byte - or start it with "02:" in other words. To keep this id (mostly) unique, using one of the routers mac-address for the rest is usually the safest way to go. +Check with 'iwconfig'. Some wifi drivers are a little buggy and do not always merge two ad-hoc cells, therefore you're usually best advised to choose and configure one manually (i.e. 'iwconfig wlan0 ap 02:XX:XX:XX:XX:XX'). While configuring a cell-id manually, you should set the 7th bit of the first byte - or start it with "02:" in other words. To keep this id (mostly) unique, using one of the routers mac-address for the rest is usually the safest way to go. === Is 'batctl if' showing the used interfaces as active? === -If batman-adv is saying "[inactive]" for one of the mesh-port interfaces, make sure this one is up (i.e. 'ifconfig wlan0 up') +If batman-adv is saying "inactive" for one of the mesh-port interfaces, make sure this one is up (i.e. 'ifconfig wlan0 up') === Is 'batctl o' showing the other node? === Make sure, that they see each other with a reasonable TQ quality (i.e. > 200). Be aware, that a full TQ update in a dynamic environment but still with the default ogm-interval setting can be delayed for up to 64 seconds. If they are not seeing each other, check your wifi settings twice, try ad-hoc meshing without batman-adv or any bridges first to make sure, that the ad-hoc wifi layer itself works fine and allows any kinds of packets (ad-hoc mode is usually not the best implemented and well tested wifi mode in a lot of wifi drivers). === Are those tq-values rather stable or acting crazy? === -If they are acting crazy, check if the mesh-port interfaces used by batman-adv all have a different mac addresses. Otherwise this could break the routing algoritm in some scenarios. +If they are acting crazy, check if the mesh-port interfaces used by batman-adv all have a different mac addresses. Otherwise this could break the routing algorithm in some scenarios. === Does a ping to the other node via the mesh work? === Set static ipv4-addresses (or (autoconfigured) ipv6 addresses) not being used on any other interfaces on bat0 and check if those two nodes can ping each other. If this works, but large pings do not (i.e. ping -s 1700), then check the MTU settings. All mesh hosts need an MTU of 24 Bytes less (i.e. on bat0 or any host bridged into the mesh) than on their mesh-port interfaces' MTU (the interfaces you've added via 'batctl if'). For instance you could chose to increase the MTU on all mesh-port interfaces to 1524 (or decrease it on all hosts, bat0 or any host interface being bridged into the mesh, to 1476 which is usually harder to maintain when having 'foreign' hosts). @@ -27,4 +27,4 @@ Set static ipv4-addresses (or (autoconfigured) ipv6 addresses) not being used on If you can see the other node but can't send any packets through the mesh network, check whether you can ping it with batman-adv's internal echoing packets (see 'batctl ping -h' for usage info). If this works, check your layer 3 settings, in general your routes and IP adresses - don't use the same routes/addresses on different interfaces, don't set any ip-addresses on the mesh-port interfaces. Just use bat0 or the bridge you might have created on top of it. === Are the wifi/lan LEDs blinking like crazy? === -Make sure you DONT bridge any mesh-port-interfaces with your bat0 interface! \ No newline at end of file +Make sure you DON'T bridge any mesh-port-interfaces with your bat0 interface!

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download (c67f9bf2)
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 c67f9bf20aabff83d66425d8ae38613936b5d1b8 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Apr 24 19:20:17 2010 +0000 doc: open-mesh/Download >--------------------------------------------------------------- c67f9bf20aabff83d66425d8ae38613936b5d1b8 open-mesh/Download.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index 29ff0b07..fdbd6bfc 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -58,7 +58,7 @@ There are various pre-compiled binaries available: * [http://downloads.open-mesh.org/batman/stable/binaries/fonera-kamikaze fonera-kamikaze] * [http://downloads.open-mesh.org/batman/stable/binaries/buffalo-freifunk/batm… buffalo-freifunk] * [http://downloads.open-mesh.org/batman/stable/binaries/armv5te armv5te (static)] - + * [http://zolpo.com/ Insurance Quotes] === 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.

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/WikiStart (f9653d1f)
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 f9653d1fba1d10eacd0dc778d78779f90db0ac63 Author: Sven Eckelmann <sven(a)narfation.org> Date: Sat Apr 24 19:19:05 2010 +0000 doc: open-mesh/WikiStart >--------------------------------------------------------------- f9653d1fba1d10eacd0dc778d78779f90db0ac63 open-mesh/WikiStart.textile | 1 + 1 file changed, 1 insertion(+) diff --git a/open-mesh/WikiStart.textile b/open-mesh/WikiStart.textile index 35978d4d..80cb01dd 100644 --- a/open-mesh/WikiStart.textile +++ b/open-mesh/WikiStart.textile @@ -23,6 +23,7 @@ B.A.T.M.A.N. (better approach to mobile ad-hoc networking) is a routing protocol * [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 + * [http://zolpo.com/auto-insurance/ Auto Insurance] ---- == Other Projects on open-mesh.org == * [wiki:FFTrace FFTrace] - freifunk traceroute tool

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/WikiStart (170f1b8f)
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