Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit c393d474a6ad5da553167634c84f6f8ba46421d8 Author: Hendrik Fabelje batman@fabelje.de Date: Wed Mar 2 16:55:26 2011 +0000

doc: batman-adv/Quick-start-guide: instead you are just using the new bridge interface 'mesh-bridge' for routing: clarify that IP has to be assigned to mesh-bridge

c393d474a6ad5da553167634c84f6f8ba46421d8 batman-adv/Quick-start-guide.textile | 62 +++++++++++++++++++++--------------- 1 file changed, 36 insertions(+), 26 deletions(-)

diff --git a/batman-adv/Quick-start-guide.textile b/batman-adv/Quick-start-guide.textile index 1fcf9a38..27beeaf5 100644 --- a/batman-adv/Quick-start-guide.textile +++ b/batman-adv/Quick-start-guide.textile @@ -1,81 +1,91 @@ -= B.A.T.M.A.N. Advanced quick start guide =

-{{{ -#!div style="width: 46em; text-align: justify" +h1. B.A.T.M.A.N. Advanced quick start guide + + +<pre> +<code class="div">

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 === + +h3. 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 add ifname', e.g. -{{{ +<pre> batctl if add eth0 -}}} +</code></pre> Make sure, this interface is up and running ('ifconfig eth0 up') and use the command -{{{ +<pre> batctl if -}}} +</code></pre> to verify its status. Check the system log for hints in case it does not behave as you expect.

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 === + +h3. 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 ===

-'''simple mesh network'''[[BR]] +h3. Examples + + +*simple mesh network* +

On all nodes, install batman-adv, load the module and enter the following commands:

-{{{ +<pre> ifconfig wlan0 mtu 1524 iwconfig wlan0 mode ad-hoc essid my-mesh-network ap 02:12:34:56:78:9A channel 1 -}}} +</code></pre>

-{{{ +<pre> batctl if add wlan0 ifconfig wlan0 up ifconfig bat0 up -}}} +</code></pre>

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. +*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. + +*mixing non-B.A.T.M.A.N. systems with batman-adv*

-'''mixing non-B.A.T.M.A.N. systems with batman-adv'''[[BR]]

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:

-{{{ +<pre> ifconfig wlan0 mtu 1524 iwconfig wlan0 mode ad-hoc essid my-mesh-network ap 02:12:34:56:78:9A channel 1 -}}} +</code></pre>

-{{{ +<pre> batctl if add wlan0 ifconfig wlan0 up -}}} +</code></pre>

-{{{ +<pre> brctl addbr mesh-bridge brctl addif mesh-bridge eth0 brctl addif mesh-bridge bat0 ifconfig eth0 up ifconfig bat0 up ifconfig mesh-bridge up -}}} +</code></pre>

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.

-'''Note:''' Assign the IP Address to mesh-bridge in this case, not bat0. +*Note:* Assign the IP Address to mesh-bridge in this case, not bat0.

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.)'' +_(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.)_

-}}} +</code></pre>