Changeset 1183 for trunk/batman
- Timestamp:
- 01/14/09 03:40:35 (20 months ago)
- Files:
-
- 1 modified
-
trunk/batman/INSTALL (modified) (7 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/batman/INSTALL
r1182 r1183 4 4 ################################### 5 5 6 <<<<<<< .mine 7 8 9 ======= 10 >>>>>>> .r1182 6 11 Compiling from source 7 12 ===================== … … 11 16 12 17 You need the usual compile environment and the libpthread-library 13 and the kernel module "tun". Both should already be installed on 14 your machine, if you use a PC with Linux. On embedded devices 18 and the kernel module "tun". Both should already be installed on 19 your machine, if you use a PC with Linux. On embedded devices 15 20 both may not be installed in order to save space. 16 21 17 The *BSD and Mac OS operating systems are currently unmaintained, 22 The *BSD and Mac OS operating systems are currently unmaintained, 18 23 make targets are still available but will most probably not work. 19 24 If you're interested in porting and maintaining B.A.T.M.A.N. for … … 23 28 --------- 24 29 25 You don't necessarily need to compile. Our download store at 30 You don't necessarily need to compile. Our download store at 26 31 downloads.open-mesh.net likely offers precompiled packages 27 32 for your system. 28 33 29 Download and compile the latest stable sources from the download 34 Download and compile the latest stable sources from the download 30 35 section http://open-mesh.net/batman/downloads by executing eg.: 31 36 32 33 34 35 37 $ wget http://downloads.open-mesh.net/batman/releases/batman-0.3.1/batman-0.3.1.tar.gz 38 $ tar xzvf batman-0.3.1.tar.gz 39 $ cd batmand-0.3.1 40 $ make 36 41 37 After the compilation process is finished you'll find a executable 38 file called 'batmand'. This executable is quite big because it is 42 After the compilation process is finished you'll find a executable 43 file called 'batmand'. This executable is quite big because it is 39 44 not stripped. Don't strip it if you want to help us finding a bug 40 45 in the daemon. Strip it by executing: 41 46 42 47 $ strip batmand 43 48 44 49 Install by executing (as root): 45 50 46 51 $ make install 47 52 48 Or start it right from the directory where you compiled it by 53 Or start it right from the directory where you compiled it by 49 54 issuing: 50 55 51 ./batmand 56 ./batmand 52 57 53 58 … … 55 60 ================================= 56 61 57 Just to be sure, there has been some confusion with outdated 58 batman(d) packages. So its a good idea to check for any old 62 Just to be sure, there has been some confusion with outdated 63 batman(d) packages. So its a good idea to check for any old 59 64 package by login into your router and executing: 60 65 61 66 $ ipkg status | grep batman 62 67 63 68 Remove everything listed by doing for example: 64 69 65 70 $ ipkg remove batman batman-iii freifunk-batman-de ... 66 71 67 72 Then continue with the installation of fresh and stable batman packages! … … 70 75 use the ipkg-package management system. Add the line: 71 76 72 77 src lui http://freifunk.schmudde.com/ipkg 73 78 74 to your package sources file ( /etc/ipkg.conf ) and update the list of79 to your package sources file (/etc/ipkg.conf) and update the list of 75 80 available packages by executing: 76 81 77 78 79 82 $ ipkg update 83 $ ipkg install batmand 84 $ ipkg install freifunk-batman 80 85 81 If not already installed (or automatically resolved) you may also need to 86 If not already installed (or automatically resolved) you may also need to 82 87 explicitly install the libpthread and kmod-tun package. Do this by executing: 83 88 84 85 89 $ ipkg install libpthread 90 $ ipkg install kmod-tun 86 91 87 Afterwards, reboot your WRT and check the web interface. You need to enable 88 batman for one (or several) interfaces and specify the netmask and IP address 92 Afterwards, reboot your WRT and check the web interface. You need to enable 93 batman for one (or several) interfaces and specify the netmask and IP address 89 94 as well as other optionally parameters. 90 95 91 Alternatively you can get the latest stable release (as well as development) 92 versions from 96 Alternatively you can get the latest stable release (as well as development) 97 versions from http://open-mesh.net/batman/downoads/ 93 98 94 99 For example to install batmand-0.2 on a freifunk WRT do: 95 100 96 101 $ ipkg install http://downloads.open-mesh.net/batman/stable/wrt-freifunk/batmand_0.2-current_mipsel-wr-elf-32-lsb-dynamic.ipk 97 102 98 Be aware that, a recent batmand-...ipk from open-mesh.net 99 100 Both packages install /usr/sbin/batmand and the last installed 101 103 Be aware that, a recent batmand-...ipk from open-mesh.net 104 should be equal to the batmand-...ipk from freifunk.schmudde.com/ipkg. 105 Both packages install /usr/sbin/batmand and the last installed 106 one will overwrite the previous one. 102 107 103 108 … … 106 111 ===== 107 112 108 Make sure you have no firewall running that is blocking UDP 109 port 4305 (originator messages), port 4306 (gateway traffic). 113 Make sure you have no firewall running that is blocking UDP 114 port 4305 (originator messages), port 4306 (gateway traffic). 110 115 Port 4307 has to be open for incoming UDP traffic if you run the 111 116 B.A.T.M.A.N. visualization server. 112 117 113 118 First the network interfaces supposed to participate 114 in the batman mesh must be configured properly. Assuming you 115 are already running olsr on interface eth1 with the IP address 116 104.1.12.123/8 and now want to run batman in parallel to olsr 119 in the batman mesh must be configured properly. Assuming you 120 are already running olsr on interface eth1 with the IP address 121 104.1.12.123/8 and now want to run batman in parallel to olsr 117 122 on the same physical interface but with a 105.1.12.123/8 IP/netmask. 118 123 119 120 121 124 $ ifconfig eth1:bat 105.1.12.123 netmask 255.0.0.0 broadcast 105.255.255.255 125 $ batmand -d 3 eth1:bat 126 122 127 This will configure an alias interface on top of eth1 named eth1:bat and start 123 128 the batman daemon with debug level 3 on that alias interface. As soon as 124 another running batmand (with the same netmask and broadcast address) is 125 connected to that link (or within the range of the wireless link) 129 another running batmand (with the same netmask and broadcast address) is 130 connected to that link (or within the range of the wireless link) 126 131 both batman daemons should see each other and indicate this in the debug output. 127 132 128 133 The daemon started with debug level 3 can be terminated with ctrl-c. 129 134 If no debuglevel is given at startup, using 130 135 131 136 $ batmand eth1:bat 132 137 133 the daemon will immediateley fork to the background (as is the usual behavior 134 of a daemon). However you can always connect to the main daemon (running 135 in background) by launching a client-batmand process with the 136 -c and -d <number> option, where the number represents the desired 137 debug-level. The following command will connect to a running batmand 138 the daemon will immediateley fork to the background (as is the usual behavior 139 of a daemon). However you can always connect to the main daemon (running 140 in background) by launching a client-batmand process with the 141 -c and -d <number> option, where the number represents the desired 142 debug-level. The following command will connect to a running batmand 138 143 process providing debug-level 1 informations. 139 144 140 145 $ batmand -c -d 1 # shows a list of other nodes in the mesh 141 146 … … 146 151 For a full list of supported debug-levels and other startup options see 147 152 148 153 $ batmand -h # providing a brief summary of options and 149 154 150 155 $ batmand -H # for a more detailed list of options 151 156 152 Use ctrl-c to terminate a process running in foreground and 153 157 Use ctrl-c to terminate a process running in foreground and 158 154 159 $ killall batmand 155 160 156 161 to terminate the main batmand daemon running in background. 157 162 158 If you want to use one of the batman-internet gateways showed with 163 If you want to use one of the batman-internet gateways showed with 159 164 debug-level 2 launch the main batmand using: 160 165 161 $ batmand -r 3 eth1:bat # to automatically select a reasonable GW 162 163 $ batmand -r 3 -p <ip-of-batmand-gw-node> eth1:bat # to set a preferred GW 166 $ batmand -r 3 eth1:bat # to automatically select a reasonable GW 164 167 165 In case of success this will setup a tunnel to a (preferred) batman-gw-node 166 and configure the routing table that all packets matching the default route 168 $ batmand -r 3 -p <ip-of-batmand-gw-node> eth1:bat # to set a preferred GW 169 170 In case of success this will setup a tunnel to a (preferred) batman-gw-node 171 and configure the routing table that all packets matching the default route 167 172 are forwarded (tunneled) respectively. 168 173 More information is available using the -h and -H options.
