commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Wiki (a68fd26a)
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 a68fd26af1b419b9f5ca1f35c045b17153cfde41 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Jun 21 02:38:17 2010 +0000 doc: batman-adv/Wiki >--------------------------------------------------------------- a68fd26af1b419b9f5ca1f35c045b17153cfde41 batman-adv/Wiki.textile | 72 ++++++++++++++++++++----------------------------- 1 file changed, 29 insertions(+), 43 deletions(-) diff --git a/batman-adv/Wiki.textile b/batman-adv/Wiki.textile index 14c59583..577f17db 100644 --- a/batman-adv/Wiki.textile +++ b/batman-adv/Wiki.textile @@ -1,43 +1,29 @@ -= batman-advanced = - -Batman-advanced is a new approach to wireless networking which -does no longer operate on the IP basis. Unlike the layer 3 batman-daemon, which exchanges -information using UDP packets and sets routing tables, batman-advanced operates -on ISO/OSI Layer 2 only and uses and routes (or better: bridges) Ethernet Frames. -It emulates a virtual network switch of all nodes participating. Therefore all nodes -appear to be link local, thus all higher operating protocols won't be affected -by any changes within the network. You can run almost any protocol above B.A.T.M.A.N.-Advanced, -prominent examples are: IPv4, IPv6, DHCP, IPX. - -=== Pros and Cons === -Pros: - * supports any Ethernet-capable protocol (IPv4, IPv6, ARP, DHCP ...) - * no manual IP assignment, just use DHCP - * easy integration of attached networks (no manual HNA fiddling), just put the bat0 in the bridge with your other devices. You can for example build a roaming network of Access Points with this technique. - * Not affected by your Firewall (but you can secure the payload traffic, of course) -Cons: - * ~~no gateway handling inside of B.A.T.M.A.N. (DHCP/IPv6 autoconf/static routes will work but B.A.T.M.A.N. won't help to choose the best gateway for you)~~ (the upcoming batman-adv 0.3 supports advanced gateway handling) -=== batctl (former battools) === - -Since the nodes participating in the B.A.T.M.A.N. Advanced switch are -completely transparent for all protocols above layer 2, we needed to build -our own diagnostic tool batctl. This tool contains a layer 2 version -of ping, traceroute and tcpdump. It also offers a configuration interface -for the kernel module as well as an integrated log reader. -Further information can be found in the enclosed README file. - -=== Userland vs Kernelland === - -The userland implementation of batman-advanced was a proof of concept implementation to verify that the concept is -working. Unfortunately, switching 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, which is now the -preferred version. It can be controlled via the /proc file system and works transparently. The userland remains unmaintained and has been removed from the subversion repository. - -=== Documentation === - -See the [wiki:UserDocs UserDocs] page. - -=== Get it === - -see the [wiki:Download] page \ No newline at end of file + += B.A.T.M.A.N. advanced = + +{{{ +#!div style="width: 46em; text-align: justify" + +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 ? == + +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 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) + +== 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 ? == + +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. + +}}}

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/Download (c5691a39)
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 c5691a39125c6be799f353c0f82639cdc283d550 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun Jun 20 00:12:12 2010 +0000 doc: open-mesh/Download >--------------------------------------------------------------- c5691a39125c6be799f353c0f82639cdc283d550 open-mesh/Download.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/open-mesh/Download.textile b/open-mesh/Download.textile index fbcbc5c8..80290c76 100644 --- a/open-mesh/Download.textile +++ b/open-mesh/Download.textile @@ -5,7 +5,7 @@ We are offering sources and precompiled batmand binaries and packages for differ === 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-2010.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-2010.0.0… batctl-2010.0.0.tar.gz] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2010.0.0… md5] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2010.0.0… sha1] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2010.0.0… asc] + * The latest version of batctl (management and control tool for batman-adv) is [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2010.0.0… batctl-2010.0.0.tar.gz] [http://downloads.open-mesh.net/batman/stable/sources/batctl/batctl-2010.0.0… md5] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2010.0.0… sha1] [http://downloads.open-mesh.org/batman/stable/sources/batctl/batctl-2010.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] @@ -17,7 +17,7 @@ If you find any bugs, please [wiki:Contribute let us know]! === 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/}}}'' + * [wiki:batman-adv B.A.T.M.A.N. advanced]: [[BR]]''{{{svn co http://downloads.open-mesh.org/svn/batman/trunk/batman-adv-kernelland/}}}'' * 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/}}}''

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Release-todo (181b253e)
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 181b253e41e440f409b7cca6ee9a44c25ba034f2 Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun Jun 20 00:13:14 2010 +0000 doc: batman-adv/Release-todo >--------------------------------------------------------------- 181b253e41e440f409b7cca6ee9a44c25ba034f2 batman-adv/Release-todo.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index 2c061857..b0441a76 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -32,4 +32,4 @@ This page contains a checklist of things that need to be done for a release. '''Distributions''' * [ ] update openwrt package - * [ ] inform batman package maintainer + * [x] inform batman package maintainer

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: open-mesh/WikiStart (44c1f593)
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 (4937a107)
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 4937a1073389707b02eb46e50a87b82f0227870f Author: Simon Wunderlich <sw(a)simonwunderlich.de> Date: Sun Jun 20 00:44:59 2010 +0000 doc: batman-adv/Release-todo >--------------------------------------------------------------- 4937a1073389707b02eb46e50a87b82f0227870f batman-adv/Release-todo.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/batman-adv/Release-todo.textile b/batman-adv/Release-todo.textile index b0441a76..db36a2c7 100644 --- a/batman-adv/Release-todo.textile +++ b/batman-adv/Release-todo.textile @@ -9,7 +9,7 @@ This page contains a checklist of things that need to be done for a release. * [x] make sure all code contains the release version strings * [x] update copyright years (if needed) * [x] remove dead code (if any) - * [ ] svn/git tag release + * [x] svn/git tag release * [-] change version strings inside the trunk (strip beta etc) * [-] change version strings after release to next version * [x] check against kernel versions @@ -26,7 +26,7 @@ This page contains a checklist of things that need to be done for a release. * [x] build package tar.gz (replace symlinks with real files) and generate checksums * [x] move packages/checksums to stable/sources / create symlinks from releases * [x] update download links in the trac downloads page - * [ ] send release mail + * [x] send release mail * [ ] update IRC channel topic

1 0

[doc] backup-redmine/2017-07-13, master: doc: batman-adv/Quick-start-guide: adjust article to new batctl commandline API (58e6e046)
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 58e6e046900cae547dc2fff934bd2829e0a3b8ee Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun Jun 20 13:46:27 2010 +0000 doc: batman-adv/Quick-start-guide: adjust article to new batctl commandline API >--------------------------------------------------------------- 58e6e046900cae547dc2fff934bd2829e0a3b8ee batman-adv/Quick-start-guide.textile | 25 ++++++++++++++++++++----- 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/batman-adv/Quick-start-guide.textile b/batman-adv/Quick-start-guide.textile index b282dd7b..9258906b 100644 --- a/batman-adv/Quick-start-guide.textile +++ b/batman-adv/Quick-start-guide.textile @@ -1,12 +1,16 @@ = B.A.T.M.A.N. Advanced quick start guide = -This page shall show a couple of easy examples of how to use and setup a mesh network with B.A.T.M.A.N.-Advanced (further referenced as batman-adv). It is assumed, the tool 'batctl' was installed which allows a more intuitive configuration, though everything can be configured by accessing '/proc/net/batman-adv/...' directly without the need of installing batctl. +{{{ +#!div style="width: 46em; text-align: justify" + +This page shall show a couple of easy examples of how to use and setup a mesh network with B.A.T.M.A.N.-Advanced (further referenced as batman-adv). It is assumed, the tool 'batctl' was installed which allows a more intuitive configuration, though everything can be configured by accessing '/sys/class/net/$iface/batman-adv/...' directly without the need of installing batctl. === Configuring interfaces === -In the first configuraton step you need to tell batman-adv which interfaces it should use to build the mesh network. This can be either wifi devices like wlanX or athX but also common ethernet devices, usually ethX. batman-adv is not limited to a certain interface type, therefore you can use any interface you can find with 'ifconfig' (even pan0 for bluetooth if you like B.A.T.M.A.N. more than the normal, build-in 'mesh-protocol' of bluetooth :-) ). Those interfaces can be added by using 'batctl if ifname', e.g. + +In the first configuraton step you need to tell batman-adv which interfaces it should use to build the mesh network. This can be either wifi devices like wlanX or athX but also common ethernet devices, usually ethX. batman-adv is not limited to a certain interface type, therefore you can use any interface you can find with 'ifconfig' (even pan0 for bluetooth if you like B.A.T.M.A.N. more than the normal, build-in 'mesh-protocol' of bluetooth :-) ). Those interfaces can be added by using 'batctl if add ifname', e.g. {{{ -batctl if eth0 +batctl if add eth0 }}} Make sure, this interface is up and running ('ifconfig eth0 up') and use the command {{{ @@ -17,6 +21,7 @@ to verify its status. Check the system log for hints in case it does not behave Despite being up, those interfaces that have been added using batctl don't need any ip-address configured as batman-adv is operating on layer 2 (which is a common mistake by people who are more familiar with the 'old' batmand or other layer 3 routing protocols)! Those interfaces are bridge-interfaces - you just must not use those plain interfaces for routing anymore. === bat0 === + So where are we going to send data packets to if not to those interfaces we have given batman-adv? That's where the virtual bat0 interface (created by batman-adv) is getting into the game. Usually you are going to assign IP adresses to this one - either manually or via dhcpv4 / avahi autoconfiguration / dhcpv6 / ipv6 autoconfiguration. Any packet that enters this interface will be examined by the batman-adv kernel module for its destination mac-adress and will be forwarded with the help of B.A.T.M.A.N.'s routing voodoo then, so that finally, magically it pops out at the right destination's bat0 interface :). === Examples === @@ -24,15 +29,18 @@ So where are we going to send data packets to if not to those interfaces we have '''simple mesh network'''[[BR]] On all nodes, install batman-adv, load the module and enter the following commands: + {{{ ifconfig wlan0 mtu 1524 iwconfig wlan0 mode ad-hoc essid my-mesh-network ap 02:12:34:56:78:9A channel 1 }}} + {{{ -batctl if wlan0 +batctl if add wlan0 ifconfig wlan0 up ifconfig bat0 up }}} + You can now use the automatically assigned IPv6 link-local adresses on bat0 (usually starting with fe80::...), modern operating systems should support this. Or you can assign IPv4 addresses manually on all those nodes (i.e. 'ifconfig bat0 192.168.123.x/24') or one of the laptops in range has to have a DHCP server running on the bat0 interface. As batman-adv is operating on layer 2, even dhcp-messages can be send over the mesh network. '''Note:''' batman-adv inserts an additional header of 24 bytes into each data packet being send over the mesh. Therefore we are increasing the maximum size of a packet over the plain interfaces to 1524, so that packets with the standard MTU of 1500 can pass normaly through bat0. You might also decrease the MTU to 1476 on all hosts but is usually just do-able in more or less static- and small-scaled mesh-networks. @@ -42,14 +50,17 @@ You can now use the automatically assigned IPv6 link-local adresses on bat0 (usu If you have a couple of computers that you don't want to run batman-adv on but you still want make use of the mesh network, you will need to configure an entry point for them on a node running batman-adv. Any device running Linux (a notebook, a wifi-router, a pc with a wifi card, ...) can be setup to work as a mesh entry point. In addition to the usual mesh setup steps mentioned above it is necessary to configure a bridge over bat0 and the interface those 'non-B.A.T.M.A.N.' machines are connected to. Let's say eth0 is the interface on a mesh access point where those non-B.A.T.M.A.N. systems are attached to and wlan0 is the interface on a mesh access point through which we want to build the mesh network. On each mesh access point, install batman-adv first, load the module and enter the following commands: + {{{ ifconfig wlan0 mtu 1524 iwconfig wlan0 mode ad-hoc essid my-mesh-network ap 02:12:34:56:78:9A channel 1 }}} + {{{ -batctl if wlan0 +batctl if add wlan0 ifconfig wlan0 up }}} + {{{ brctl addbr mesh-bridge brctl addif mesh-bridge eth0 @@ -58,8 +69,12 @@ ifconfig eth0 up ifconfig bat0 up ifconfig mesh-bridge up }}} + From now on you won't want to use eth0, wlan0 or bat0 for any routing anymore, instead you are just using the new bridge interface 'mesh-bridge'. Any packet our mesh access point receives over eth0 will be forwarded to bat0 because of the bridge. batman-adv will forward it through the mesh according to the destination's mac address. For the MTU-part have a look at the note above. ''(How does batman-adv know where it has to send a data packet of an external computer, that is not using batman-adv, to another computer that is not using batman-adv either? It is automatically listening on bat0 and will keep track of any host mac address passing by this interface. Those host's mac addresses will then be announced to other batman-adv nodes in the mesh network automatically - so called HNA messages - so that every batman-adv node is going to know behind which other batman-adv node it can find which mac addresses.)'' + +}}} +

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/VisOutput (f6684821)
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 f6684821b2a9fa118fbb7657ec7c3af2e6494a11 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Jun 21 00:06:24 2010 +0000 doc: batmand/VisOutput >--------------------------------------------------------------- f6684821b2a9fa118fbb7657ec7c3af2e6494a11 batmand/VisOutput.textile | 43 ++++++++++++++++--------------------------- 1 file changed, 16 insertions(+), 27 deletions(-) diff --git a/batmand/VisOutput.textile b/batmand/VisOutput.textile index e41f1502..d466fe53 100644 --- a/batmand/VisOutput.textile +++ b/batmand/VisOutput.textile @@ -1,14 +1,13 @@ -== Working with the vis server output == += Working with the vis server output = -This artcile is for those that intend to write their own visualization tool, combine the vis [[BR]] -output with a map or want to understand the vis server output for another reason. [[BR]] -''If you want to setup the vis server for the batmand have a look at this [wiki:VisualizeMesh article] or for [[BR]] -BATMAN-Advanced at [wiki:VisAdv this one]. [[BR]] +{{{ +#!div style="width: 46em; text-align: justify" + +This artcile is for those that intend to write their own visualization tool, combine the vis output with a map or want to understand the vis server output for another reason. If you want to setup the vis server for the batmand have a look at this [wiki:VisualizeMesh article] or for BATMAN-Advanced at [wiki:VisAdv this one]. -Here is a sample output from the vis server in the dot draw format. Newer vis versions offer [[BR]] -alternative formats (e.g. JSON) which follow the same rules but use another output style. [[BR]] +Here is a sample output from the vis server in the dot draw format. Newer vis versions offer alternative formats (e.g. JSON) which follow the same rules but use another output style. {{{ digraph topology @@ -22,10 +21,7 @@ digraph topology } }}} -Each "digraph { ... }" block contains a complete dump of the vis servers internal database [[BR]] -at a given time. Every line contains the IP address of a batman node, a network it has a [[BR]] -relation to and a label. All nodes sending information to the vis server are listed in the first [[BR]] -column. If a node is missing you should check whether there is a connection problem. [[BR]] +Each "digraph { ... }" block contains a complete dump of the vis servers internal database at a given time. Every line contains the IP address of a batman node, a network it has a relation to and a label. All nodes sending information to the vis server are listed in the first column. If a node is missing you should check whether there is a connection problem. [[BR]] @@ -36,20 +32,11 @@ column. If a node is missing you should check whether there is a connection prob "5.224.160.202" -> "5.174.37.225"[label="1.28"] }}} -The batman node 5.174.37.225 has a connection towards the batman node 5.224.160.202 [[BR]] -with a link quality of "2.13" whereas the 5.224.160.202 has a link quality of "1.28" towards [[BR]] -the 5.174.37.225. The connection is listed twice because each node reports it individually [[BR]] -which gives you the option of seeing asymetric links if you want to display it. [[BR]] +The batman node 5.174.37.225 has a connection towards the batman node 5.224.160.202 with a link quality of "2.13" whereas the 5.224.160.202 has a link quality of "1.28" towards the 5.174.37.225. The connection is listed twice because each node reports it individually which gives you the option of seeing asymetric links if you want to display it. -The link quality gives information how batman evaluates this link. 1.00 means 100%25 link [[BR]] -quality, 2.00 means 50%25, 3.00 is 33.3%25 and 4.00 is 25%25, etc. The number tells you how [[BR]] -many packets you need to send in order to get a single successful transmission. [[BR]] +The link quality gives information how batman evaluates this link. 1.00 means 100%25 link quality, 2.00 means 50%25, 3.00 is 33.3%25 and 4.00 is 25%25, etc. The number tells you how many packets you need to send in order to get a single successful transmission. -While looking at originator tables, debug logs or other batman output you might see different [[BR]] -numbers. Due to performance considerations batman uses his own format (TQ value) to [[BR]] -express link quality. Its max value is 255 and goes down to 0 (float operations are quite [[BR]] -expensive on embedded devices). The vis server transforms the TQ value into its own format [[BR]] -before outputting it. [[BR]] +While looking at originator tables, debug logs or other batman output you might see different numbers. Due to performance considerations batman uses his own format (TQ value) to express link quality. Its max value is 255 and goes down to 0 (float operations are quite expensive on embedded devices). The vis server transforms the TQ value into its own format before outputting it. [[BR]] @@ -59,8 +46,7 @@ before outputting it. [[BR]] "5.224.160.202" -> "0.0.0.0/0.0.0.0"[label="HNA"] }}} -The 5.224.160.202 announces a connection to the internet: "0.0.0.0/0.0.0.0" and the HNA label [[BR]] -represent gateway functionality in the output. +The 5.224.160.202 announces a connection to the internet: "0.0.0.0/0.0.0.0" and the HNA label represent gateway functionality in the output. [[BR]] @@ -70,16 +56,19 @@ represent gateway functionality in the output. "5.174.37.225" -> "192.168.15.0/24"[label="HNA"] }}} -The 5.174.37.225 announces a connection to the 192.168.15.0/24 network (which does not run [[BR]] -batman). All nodes that establish a connection to this network use the 5.174.37.225 as gateway. +The 5.174.37.225 announces a connection to the 192.168.15.0/24 network (which does not run batman). All nodes that establish a connection to this network use the 5.174.37.225 as gateway. === Interfaces belonging to one BATMAN-Adv node === In BATMAN-Advanced since revision 1424, the subgraphing/cluster feature of the dot-file-format has been added to mark interfaces as belonging to the same originator. Every originator the vis-server found has such an additional subgraph block: + {{{ subgraph "cluster_00:11:22:33:44:55" { "00:11:22:33:44:55" [peripheries=2] "01:23:45:67:89:AB" } }}} + In this example the originator '00:11:22:33:44:55' has two active interfaces, "00:11:22:33:44:55" and "01:23:45:67:89:AB". With 'fdp' from the [http://www.graphviz.org/ graphviz-tools] for instance such interfaces inside of a subgraph would be surrounded by a box. The cluster-prefix is a prerequisite for this tool here to describe the relation between those interfaces and is not a label being visualized. Additionally, the ''primary'' interface gets the extra attribute '[peripheries=2]' which is the only interface known to other BATMAN-Nodes, except to direct neighbours (with graphviz, such an interface gets double circled). + +}}} \ No newline at end of file

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/VisOutput (a21cddd0)
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