commits July 2017

commits@lists.open-mesh.org

1 participants
1317 discussions

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/InternetTuning (21727f0a)
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 21727f0a9f503c8f77a9079d5576b8f5676dffdd Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun May 31 18:24:52 2009 +0000 doc: batmand/InternetTuning >--------------------------------------------------------------- 21727f0a9f503c8f77a9079d5576b8f5676dffdd batmand/InternetTuning.textile | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/batmand/InternetTuning.textile b/batmand/InternetTuning.textile index 6b666ebc..29c76f8f 100644 --- a/batmand/InternetTuning.textile +++ b/batmand/InternetTuning.textile @@ -1,4 +1,8 @@ -'''Gateway''' + +h2. Internet tuning + + +*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: @@ -25,7 +29,7 @@ That behaviour allows the gateway maintainer to distinguish between traffic insi Additionally, you have to make sure that the gateway allows forwarding and that the firewall masquerades all traffic coming through gate0. -'''!GatewayClient''' +*!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: @@ -51,10 +55,10 @@ batman 0.3.1 and before: If you plan to attach non-batman clients to your batman internet client you have to masquerade all outgoing packets on interface gate0 (e.g. iptables). batman 0.3.2 and later: -The batman daemon will try to locate the iptables binary to setup the masquerading automatically. This behaviour can be disabled using the "--disable-client-nat" option. If the outgoing packets are not masqueraded (the iptables binary wasn't found / the automatism disabled) batman will switch to the "half tunnel" mode which operates without masquerading. Beware: This mode __requires__ the gateway to have a routing entry for each client that accesses the internet (e.g. non-batman clients may be announced via HNA). Also, batman won't be able to automatically detect whether the chosen gateway is connected to the internet or not as only outgoing packets go through gate0. +The batman daemon will try to locate the iptables binary to setup the masquerading automatically. This behaviour can be disabled using the "--disable-client-nat" option. If the outgoing packets are not masqueraded (the iptables binary wasn't found / the automatism disabled) batman will switch to the "half tunnel" mode which operates without masquerading. Beware: This mode +requires+ the gateway to have a routing entry for each client that accesses the internet (e.g. non-batman clients may be announced via HNA). Also, batman won't be able to automatically detect whether the chosen gateway is connected to the internet or not as only outgoing packets go through gate0. -'''Tuning''' +*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.

1 0

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

14 Jul '17

1 0

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

14 Jul '17

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/VisualizeMesh (84dc7a56)
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 84dc7a563f0cf8d7dc18b64eae7ad4a74cbcf9ee Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun May 31 09:28:51 2009 +0000 doc: batmand/VisualizeMesh >--------------------------------------------------------------- 84dc7a563f0cf8d7dc18b64eae7ad4a74cbcf9ee batmand/VisualizeMesh.textile | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/batmand/VisualizeMesh.textile b/batmand/VisualizeMesh.textile new file mode 100644 index 00000000..55acaae6 --- /dev/null +++ b/batmand/VisualizeMesh.textile @@ -0,0 +1,33 @@ +'''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 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. + + +'''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. + +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). + +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 [http://downloads.open-mesh.org/batman/misc/wbm2009/08-vis_zoomed.png this one] you need to use one of the many tools available. This very screenshot was made by connecting mesh3d (which is part of the [http://s3d.berlios.de/ s3d tools] - debian packages are available) to the vis dot draw output. If you have impressive screenshots don't hesitate to let us know. :-)

1 0

[doc] backup-redmine/2017-07-13, master: doc: batmand/InternetTuning (cdca4e97)
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 cdca4e97d27e06fb02cb40a66d4e876ecaa86771 Author: Marek Lindner <mareklindner(a)neomailbox.ch> Date: Sun May 31 06:50:28 2009 +0000 doc: batmand/InternetTuning >--------------------------------------------------------------- cdca4e97d27e06fb02cb40a66d4e876ecaa86771 batmand/InternetTuning.textile | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/batmand/InternetTuning.textile b/batmand/InternetTuning.textile index 78f25845..1f660caa 100644 --- a/batmand/InternetTuning.textile +++ b/batmand/InternetTuning.textile @@ -25,7 +25,7 @@ That behaviour allows the gateway maintainer to distinguish between traffic insi Additionally, you have to make sure that the gateway allows forwarding and that the firewall masquerades all traffic coming through gate0. -'''GatewayClient''' +'''!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: @@ -45,9 +45,13 @@ 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. +After a gateway is chosen batman will create a gate0 interface and tries to get an IP from the gateway. 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. -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. +batman 0.3.1 and before: +If you plan to attach non-batman clients to your batman internet client you have to masquerade all outgoing packets on interface gate0 (e.g. iptables). + +batman 0.3.2 and later: +The batman daemon will try to locate the iptables binary to setup the masquerading automatically. This behaviour can be disabled using the "--disable-client-nat" option. If the outgoing packets are not masqueraded (the iptables binary wasn't found / the automatism disabled) batman will switch to the "half tunnel" mode which operates without masquerading. Beware: This mode __requires__ the gateway to have a routing entry for each client that accesses the internet (e.g. non-batman clients may be announced via HNA). Also, batman won't be able to automatically detect whether the chosen gateway is connected to the internet or not as only outgoing packets go through gate0. '''Tuning'''

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

commits July 2017