commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

[doc] backup-redmine/2017-07-13, master: doc: attachments/08-vis_zoomed.png (abd465d4)
by postmaster＠open-mesh.org 14 Jul '17

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/VisualizeMesh: beautifications ... (838b238d)
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 838b238d1d53bac5268ff3c0f93e4b9a1095a208 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Wed Sep 9 14:58:38 2009 +0000 doc: batmand/VisualizeMesh: beautifications ... >--------------------------------------------------------------- 838b238d1d53bac5268ff3c0f93e4b9a1095a208 batmand/VisualizeMesh.textile | 69 +++++++++++++++++++++++++++++++++++-------- 1 file changed, 57 insertions(+), 12 deletions(-) diff --git a/batmand/VisualizeMesh.textile b/batmand/VisualizeMesh.textile index 941a637e..c5f3a9a9 100644 --- a/batmand/VisualizeMesh.textile +++ b/batmand/VisualizeMesh.textile @@ -1,35 +1,80 @@ -== Visualize the mesh == -'''Concept''' +h2. Visualize the mesh -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 an eye-candy graphic of the networks topology. +*Concept* -'''Batman nodes''' +In contrast to other routing protocols each batman node only knows the path to its single hop neighbors and -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 link qualities), secondary interfaces and announced networks. +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 + +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 + +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 given vis IP. +The vis server can run in the mesh itself or somewhere in the internet, just make sure that batman can reach + +the given vis IP. -'''Vis server''' +*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 standardized dot draw format to express the relationships among the nodes. +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 + +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 + +JSON output on TCP port 2005 (dot draw remains available on port 2004). + 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. +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. :-) + + + -'''Fancy graphics''' -If you intend to create images like [http://downloads.open-mesh.org/batman/misc/wbm2009/08-vis_zoomed.png this one] you need to use one of the many tools available. That screenshot was made by connecting mesh3d (which is part of the [http://s3d.berlios.de/ s3d tools] - 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. :-) +[[Image(08-vis_zoomed.png)]]

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/AnnouncingNetworks (69a7fa76)
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 69a7fa769bd6795fbceef691f7f197efb993540d Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Jul 27 19:10:45 2009 +0000 doc: batmand/AnnouncingNetworks >--------------------------------------------------------------- 69a7fa769bd6795fbceef691f7f197efb993540d batmand/AnnouncingNetworks.textile | 76 +++++++++++++++++++++++++------------- 1 file changed, 51 insertions(+), 25 deletions(-) diff --git a/batmand/AnnouncingNetworks.textile b/batmand/AnnouncingNetworks.textile index 7780641a..05cf09ed 100644 --- a/batmand/AnnouncingNetworks.textile +++ b/batmand/AnnouncingNetworks.textile @@ -1,36 +1,62 @@ -== Announcing networks == -Under certain circumstances it is desirable to make non-batman hosts (such as servers, [[BR]] -subnets, other routing domains or simple notebooks) known to the batman network. Batman [[BR]] -can announce these network addresses (also known as HNA) which tells every other batman [[BR]] -node to send the data for this network segment back to the announcing host (assuming [[BR]] +h2. Announcing networks + + +Under certain circumstances it is desirable to make non-batman hosts (such as servers, + +subnets, other routing domains or simple notebooks) known to the batman network. Batman + +can announce these network addresses (also known as HNA) which tells every other batman + +node to send the data for this network segment back to the announcing host (assuming + this host knows how to reach the destination). -All following examples can also be applied as startup parameters. For the sake of simplicity [[BR]] -we assume there is a running batman daemon on the system that we can connect to.[[BR]] +All following examples can also be applied as startup parameters. For the sake of simplicity + +we assume there is a running batman daemon on the system that we can connect to. + + +Adding the announcement for e.g. the local network: + +batmand -c -a 192.168.1.0/24 + + +Adding multiple announcements in one go: + +batmand -c -a 192.168.1.0/24 -a 192.168.100.123/32 + + +Revoking an announcement: + +batmand -c -A 192.168.1.0/24 + + +Revoking multiple announcements in one go: + +batmand -c -A 192.168.1.0/24 -A 192.168.100.123/32 + + +It is worth noting that globally announced networks always give precendece to locally + +announced networks. + + ++Important+: The above examples explain how the batman nodes can find the path + +towards the non-batman network but you also have to ensure that the non-batman network + +knows the path back. This can be accomplished by setting the routes manually, -Adding the announcement for e.g. the local network: [[BR]] -batmand -c -a 192.168.1.0/24 [[BR]] +masquerading, routing protocols, etc. -Adding multiple announcements in one go: [[BR]] -batmand -c -a 192.168.1.0/24 -a 192.168.100.123/32 [[BR]] -Revoking an announcement: [[BR]] -batmand -c -A 192.168.1.0/24 [[BR]] +Batman 0.3.2 (and later versions) allow multiple nodes to announce the same network -Revoking multiple announcements in one go: [[BR]] -batmand -c -A 192.168.1.0/24 -A 192.168.100.123/32 [[BR]] +segment. You may have one non-batman network but several entry points to it. All border -It is worth noting that globally announced networks always give precendece to locally [[BR]] -announced networks. [[BR]] +nodes can announce the same network. Receiving batman nodes choose their entry point -__Important__: The above examples explain how the batman nodes can find the path [[BR]] -towards the non-batman network but you also have to ensure that the non-batman network[[BR]] -knows the path back. This can be accomplished by setting the routes manually, [[BR]] -masquerading, routing protocols, etc. [[BR]] +based on the best TQ value available. -Batman 0.3.2 (and later versions) allow multiple nodes to announce the same network [[BR]] -segment. You may have one non-batman network but several entry points to it. All border[[BR]] -nodes can announce the same network. Receiving batman nodes choose their entry point [[BR]] -based on the best TQ value available. [[BR]]

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/AnnouncingNetworks (8b804782)
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 8b804782b4c9ec01ca8f11eface9917c3a87665c Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Mon Jul 27 19:10:45 2009 +0000 doc: batmand/AnnouncingNetworks >--------------------------------------------------------------- 8b804782b4c9ec01ca8f11eface9917c3a87665c batmand/AnnouncingNetworks.textile | 38 +++++++++++++++++++++++++------------- 1 file changed, 25 insertions(+), 13 deletions(-) diff --git a/batmand/AnnouncingNetworks.textile b/batmand/AnnouncingNetworks.textile index c361783d..7780641a 100644 --- a/batmand/AnnouncingNetworks.textile +++ b/batmand/AnnouncingNetworks.textile @@ -1,24 +1,36 @@ == Announcing networks == -Under certain circumstances it is desirable to make non-batman hosts (such as servers, subnets, other routing domains or simple notebooks) known to the batman network. Batman can announce these network addresses (also known as HNA) which tells every other batman node to send the data for this network segment back to the announcing host (assuming this host knows how to reach the destination). +Under certain circumstances it is desirable to make non-batman hosts (such as servers, [[BR]] +subnets, other routing domains or simple notebooks) known to the batman network. Batman [[BR]] +can announce these network addresses (also known as HNA) which tells every other batman [[BR]] +node to send the data for this network segment back to the announcing host (assuming [[BR]] +this host knows how to reach the destination). -All following examples can also be applied as startup parameters. For the sake of simplicity we assume there is a running batman daemon on the system that we can connect to. +All following examples can also be applied as startup parameters. For the sake of simplicity [[BR]] +we assume there is a running batman daemon on the system that we can connect to.[[BR]] -Adding the announcement for e.g. the local network: -batmand -c -a 192.168.1.0/24 +Adding the announcement for e.g. the local network: [[BR]] +batmand -c -a 192.168.1.0/24 [[BR]] -Adding multiple announcements in one go: -batmand -c -a 192.168.1.0/24 -a 192.168.100.123/32 +Adding multiple announcements in one go: [[BR]] +batmand -c -a 192.168.1.0/24 -a 192.168.100.123/32 [[BR]] -Revoking an announcement: -batmand -c -A 192.168.1.0/24 +Revoking an announcement: [[BR]] +batmand -c -A 192.168.1.0/24 [[BR]] -Revoking multiple announcements in one go: -batmand -c -A 192.168.1.0/24 -A 192.168.100.123/32 +Revoking multiple announcements in one go: [[BR]] +batmand -c -A 192.168.1.0/24 -A 192.168.100.123/32 [[BR]] -It is worth noting that globally announced networks always give precendece to locally announced networks. +It is worth noting that globally announced networks always give precendece to locally [[BR]] +announced networks. [[BR]] -__Important__: The above exmples explain how the batman nodes can find the path towards the non-batman network but you also have to ensure that the non-batman network knows the path back. This can be accomplished by setting the routes manually, masquerading, routing protocols, etc. +__Important__: The above examples explain how the batman nodes can find the path [[BR]] +towards the non-batman network but you also have to ensure that the non-batman network[[BR]] +knows the path back. This can be accomplished by setting the routes manually, [[BR]] +masquerading, routing protocols, etc. [[BR]] -Batman 0.3.2 (and later versions) allow multiple nodes to announce the same network segment. You may have one non-batman network but several entry points to it. All border nodes can announce the same network. Receiving batman nodes choose their entry point based on the best TQ value available. +Batman 0.3.2 (and later versions) allow multiple nodes to announce the same network [[BR]] +segment. You may have one non-batman network but several entry points to it. All border[[BR]] +nodes can announce the same network. Receiving batman nodes choose their entry point [[BR]] +based on the best TQ value available. [[BR]]

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017