commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: batmand/VisOutput: added description of subgraphing-blocks (b9c9a709)
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 b9c9a709fdd71e3c0ee2165abdca755d7727a0b8 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Sep 28 20:55:19 2009 +0000 doc: batmand/VisOutput: added description of subgraphing-blocks >--------------------------------------------------------------- b9c9a709fdd71e3c0ee2165abdca755d7727a0b8 batmand/VisOutput.textile | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/batmand/VisOutput.textile b/batmand/VisOutput.textile index 5066da57..57ab5e65 100644 --- a/batmand/VisOutput.textile +++ b/batmand/VisOutput.textile @@ -71,3 +71,14 @@ represent gateway functionality in the output. 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. + +=== Interfaces belonging to one BATMAN-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. Additionally, the ''primary'' interface gets the extra attribute '[peripheries=2]' which is the only interface known to 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: open-mesh/Filing: fixed typo (f18b4689)
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 f18b468934f68af0e67c9fd333021b4bf80b3514 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Sep 28 20:56:02 2009 +0000 doc: open-mesh/Filing: fixed typo >--------------------------------------------------------------- f18b468934f68af0e67c9fd333021b4bf80b3514 open-mesh/Filing.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/open-mesh/Filing.textile b/open-mesh/Filing.textile index 28eb5ab2..7eba4b17 100644 --- a/open-mesh/Filing.textile +++ b/open-mesh/Filing.textile @@ -25,7 +25,7 @@ * [wiki:batman-adv B.A.T.M.A.N. Advanced] - information about the Layer 2 version of B.A.T.M.A.N. * [http://wiki.hskflashcards.com/index.php?page=B.A.T.M.A.N.+Advanced+on+OpenW… B.A.T.M.A.N. Advanced on OpenWRT] - a tutorial for using B.A.T.M.A.N. Advanced on OpenWRT - * [wiki:VisAdv Visualising the 2nd layer] - creating graphics of the layer 2 network and differences to the layer 3 vis output explained + * [wiki:VisAdv Visualizing the 2nd layer] - creating graphics of the layer 2 network and differences to the layer 3 vis output explained * [http://downloads.open-mesh.org/batman/development/sources/batctl_0.2-beta-c… batctl online man page] - read the current batctl man page online * [http://downloads.open-mesh.org/batman/misc/24C3-Wireless_Kernel_Tweaking.mkv Wireless Kernel Tweaking (video)] - Introduction to batman-advanced by Marek and Simon (also available at [http://video.google.de/videoplay?docid=1355876033101731617 google video])

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/VisOutput: addad link to batman-adv vis-setup description (c74fecc9)
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 c74fecc95d5af146cb9bc8798abc5d2d9ad04f12 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Sep 28 21:10:26 2009 +0000 doc: batmand/VisOutput: addad link to batman-adv vis-setup description >--------------------------------------------------------------- c74fecc95d5af146cb9bc8798abc5d2d9ad04f12 batmand/VisOutput.textile | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/batmand/VisOutput.textile b/batmand/VisOutput.textile index 57ab5e65..df7f6887 100644 --- a/batmand/VisOutput.textile +++ b/batmand/VisOutput.textile @@ -2,8 +2,9 @@ == 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. If you [[BR]] -want to setup the vis server have a look at this [wiki:VisualizeMesh article]. [[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]] Here is a sample output from the vis server in the dot draw format. Newer vis versions offer [[BR]] @@ -81,4 +82,4 @@ subgraph "cluster_00:11:22:33:44:55" { "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. Additionally, the ''primary'' interface gets the extra attribute '[peripheries=2]' which is the only interface known to BATMAN-Nodes, except to direct neighbours (with graphviz, such an interface gets double circled). \ No newline at end of file +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 being visualized. Additionally, the ''primary'' interface gets the extra attribute '[peripheries=2]' which is the only interface known to 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 (8b0dd333)
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 8b0dd3336b41def4764bc26dc72d39bdbba42a67 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Sep 28 21:11:14 2009 +0000 doc: batmand/VisOutput >--------------------------------------------------------------- 8b0dd3336b41def4764bc26dc72d39bdbba42a67 batmand/VisOutput.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batmand/VisOutput.textile b/batmand/VisOutput.textile index df7f6887..55d8c0ce 100644 --- a/batmand/VisOutput.textile +++ b/batmand/VisOutput.textile @@ -82,4 +82,4 @@ subgraph "cluster_00:11:22:33:44:55" { "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 being visualized. Additionally, the ''primary'' interface gets the extra attribute '[peripheries=2]' which is the only interface known to BATMAN-Nodes, except to direct neighbours (with graphviz, such an interface gets double circled). \ No newline at end of file +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 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 (ea4e00d2)
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 ea4e00d20a753c8988ff2620c0f1515d44b64954 Author: Linus Lüssing <linus.luessing(a)c0d3.blue> Date: Mon Sep 28 21:12:57 2009 +0000 doc: batmand/VisOutput >--------------------------------------------------------------- ea4e00d20a753c8988ff2620c0f1515d44b64954 batmand/VisOutput.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/batmand/VisOutput.textile b/batmand/VisOutput.textile index 55d8c0ce..b1ee3929 100644 --- a/batmand/VisOutput.textile +++ b/batmand/VisOutput.textile @@ -73,7 +73,7 @@ represent gateway functionality in the output. 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. -=== Interfaces belonging to one BATMAN-Node === +=== 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: {{{

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/VisualizeMesh: beautifications ... (4fdd9e46)
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 4fdd9e46456cd079d1971cc1ef11343ce68585a9 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Wed Sep 9 14:58:38 2009 +0000 doc: batmand/VisualizeMesh: beautifications ... >--------------------------------------------------------------- 4fdd9e46456cd079d1971cc1ef11343ce68585a9 batmand/VisualizeMesh.textile | 78 +++++++++++++++---------------------------- 1 file changed, 27 insertions(+), 51 deletions(-) diff --git a/batmand/VisualizeMesh.textile b/batmand/VisualizeMesh.textile index c5f3a9a9..e993fb0d 100644 --- a/batmand/VisualizeMesh.textile +++ b/batmand/VisualizeMesh.textile @@ -1,80 +1,56 @@ +== Visualize the mesh == -h2. Visualize the mesh - - -*Concept* - -In contrast to other routing protocols each batman node only knows the path to its single hop neighbors and - -knows nothing about the topology behind it. In practice it means that a batman node S is aware of node A - -which is somewhere in the mesh and reachable via neighbor B but it does not know about the number of hops - -and / or nodes in between. This approach is quite handy with regard to memory footprint, mesh stability and - -bandwidth friendliness but somewhat hard to visualize. Therefore a small helper was created: the vis server. - -It gathers the local views of each node and assembles a graph that can be fed into various tools which output +'''Concept''' +In contrast to other routing protocols each batman node only knows the path to its single hop neighbors and[[BR]] +knows nothing about the topology behind it. In practice it means that a batman node S is aware of node A[[BR]] +which is somewhere in the mesh and reachable via neighbor B but it does not know about the number of hops[[BR]] +and / or nodes in between. This approach is quite handy with regard to memory footprint, mesh stability and[[BR]] +bandwidth friendliness but somewhat hard to visualize. Therefore a small helper was created: the vis server.[[BR]] +It gathers the local views of each node and assembles a graph that can be fed into various tools which output[[BR]] an eye-candy graphic of the networks topology. -*Batman nodes* - -Each batman node needs to know the IP address of the vis server it should send the vis packets to. This - -packet is sent every few seconds containing various information about the local neighbors (including their +'''Batman nodes''' +Each batman node needs to know the IP address of the vis server it should send the vis packets to. This[[BR]] +packet is sent every few seconds containing various information about the local neighbors (including their[[BR]] link qualities), secondary interfaces and announced networks. Example: batmand -s visIP [interface] -The vis server can run in the mesh itself or somewhere in the internet, just make sure that batman can reach - +The vis server can run in the mesh itself or somewhere in the internet, just make sure that batman can reach[[BR]] the given vis IP. -*Vis server* - -The vis server can run on multiple interfaces and expects incoming vis packets on UDP port 4307. Per default - -it sends the assembled graph to all clients connected to TCP port 2004 every few seconds. It uses the +'''Vis server''' +The vis server can run on multiple interfaces and expects incoming vis packets on UDP port 4307. Per default[[BR]] +it sends the assembled graph to all clients connected to TCP port 2004 every few seconds. It uses the [[BR]] standardized dot draw format to express the relationships among the nodes. Example: vis [interface] [interface] -The vis server 0.3.2 (and later) additionally offer JSON as output format. Once activated you can retrieve the - -JSON output on TCP port 2005 (dot draw remains available on port 2004). - +The vis server 0.3.2 (and later) additionally offer JSON as output format. Once activated you can retrieve the[[BR]] +JSON output on TCP port 2005 (dot draw remains available on port 2004).[[BR]] Example: vis -j [interface] [interface] -Make sure that all mentioned ports are not blocked by a firewall. You can verify whether your setup works by - -using e.g. telnet to connect to port 2004 or 2005. - - - -*Fancy graphics* - -If you intend to create images like the one below you need to use one of the many tools available. That - -screenshot was made by connecting mesh3d (which is part of the "s3d tools":http://s3d.berlios.de/ - debian packages are available) - -to the vis servers dot draw output (on port 2004). - - - -If you have impressive screenshots don't hesitate to let us know. :-) - - +Make sure that all mentioned ports are not blocked by a firewall. You can verify whether your setup works by[[BR]] +using e.g. telnet to connect to port 2004 or 2005. [[BR]] +'''Fancy graphics''' +If you intend to create images like the one below you need to use one of the many tools available. That [[BR]] +screenshot was made by connecting mesh3d (which is part of the [http://s3d.berlios.de/ s3d tools] - debian packages are available) [[BR]] +to the vis servers dot draw output (on port 2004).[[BR]] +[[BR]] +If you have impressive screenshots don't hesitate to let us know. :-)[[BR]] +[[BR]] +[[BR]] [[Image(08-vis_zoomed.png)]]

1 0

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