| 106 | | Usage |
| 107 | | ===== |
| 108 | | |
| 109 | | Make sure you have no firewall running that is blocking UDP |
| 110 | | port 4305 (originator messages), port 4306 (gateway traffic). |
| 111 | | Port 4307 has to be open for incoming UDP traffic if you run the |
| 112 | | B.A.T.M.A.N. visualization server. |
| 113 | | |
| 114 | | First the network interfaces supposed to participate |
| 115 | | in the batman mesh must be configured properly. Assuming you |
| 116 | | are already running olsr on interface eth1 with the IP address |
| 117 | | 104.1.12.123/8 and now want to run batman in parallel to olsr |
| 118 | | on the same physical interface but with a 105.1.12.123/8 IP/netmask. |
| 119 | | |
| 120 | | $ ifconfig eth1:bat 105.1.12.123 netmask 255.0.0.0 broadcast 105.255.255.255 |
| 121 | | $ batmand -d 3 eth1:bat |
| 122 | | |
| 123 | | This will configure an alias interface on top of eth1 named eth1:bat and start |
| 124 | | the batman daemon with debug level 3 on that alias interface. As soon as |
| 125 | | another running batmand (with the same netmask and broadcast address) is |
| 126 | | connected to that link (or within the range of the wireless link) |
| 127 | | both batman daemons should see each other and indicate this in the debug output. |
| 128 | | |
| 129 | | The daemon started with debug level 3 can be terminated with ctrl-c. |
| 130 | | If no debuglevel is given at startup, using |
| 131 | | |
| 132 | | $ batmand eth1:bat |
| 133 | | |
| 134 | | the daemon will immediateley fork to the background (as is the usual behavior |
| 135 | | of a daemon). However you can always connect to the main daemon (running |
| 136 | | in background) by launching a client-batmand process with the |
| 137 | | -c and -d <number> option, where the number represents the desired |
| 138 | | debug-level. The following command will connect to a running batmand |
| 139 | | process providing debug-level 1 informations. |
| 140 | | |
| 141 | | $ batmand -c -d 1 # shows a list of other nodes in the mesh |
| 142 | | |
| 143 | | $ batmand -c -d 2 # shows a list of nodes offering internet GW access |
| 144 | | |
| 145 | | $ route -n # shows your current routing table as modified by batmand |
| 146 | | |
| 147 | | For a full list of supported debug-levels and other startup options see |
| 148 | | |
| 149 | | $ batmand -h # providing a brief summary of options and |
| 150 | | |
| 151 | | $ batmand -H # for a more detailed list of options |
| 152 | | |
| 153 | | Use ctrl-c to terminate a process running in foreground and |
| 154 | | |
| 155 | | $ killall batmand |
| 156 | | |
| 157 | | to terminate the main batmand daemon running in background. |
| 158 | | |
| 159 | | If you want to use one of the batman-internet gateways showed with |
| 160 | | debug-level 2 launch the main batmand using: |
| 161 | | |
| 162 | | $ batmand -r 3 eth1:bat # to automatically select a reasonable GW |
| 163 | | |
| 164 | | $ batmand -r 3 -p <ip-of-batmand-gw-node> eth1:bat # to set a preferred GW |
| 165 | | |
| 166 | | In case of success this will setup a tunnel to a (preferred) batman-gw-node |
| 167 | | and configure the routing table that all packets matching the default route |
| 168 | | are forwarded (tunneled) respectively. |
| 169 | | More information is available using the -h and -H options. |
| 170 | | |
| 171 | | |
| 172 | | |
| 173 | | |
| 174 | | Happy routing! |
| 175 | | |
| 176 | | The B.A.T.M.A.N. contributors |
