Hi, new at batman. I've got the following done:
1. got an airlink ar430w and wrt54gl to ping each other over ad-hoc network 2. setup br-lan:0 on each router. ar430w has is 192.168.100.1; wrt54gl is 192.168.100.2 3. was able to ping each other via br-lan:0 IP 4. using openwrt 8.09 on both routers.
The wrt54gl got the wan/internet link up. I started "batmand -g 1mbit/128kbit br-lan:0" the ar430w doesn't have internet; I started "batmand -r 3 -d 3 br-lan:0"
got this on the ar430w logs:
Interface activated: br-lan:0 Using interface br-lan:0 with address 192.168.100.1 and broadcast address 192.168.100.255 B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5) Adding throw route to 127.0.0.0/8 via 0.0.0.0 (table 68 - lo) Adding throw route to 192.168.1.0/24 via 0.0.0.0 (table 68 - br-lan) Adding throw route to 192.168.100.0/24 via 0.0.0.0 (table 68 - br-lan:0) debug level: 3 routing class: 3 Adding route to 192.168.100.2 via 0.0.0.0 (table 66 - br-lan:0) Found new gateway 192.168.100.2 -> class: 32 - 1024KBit/128KBit Adding default route to 192.168.100.2 (gw_flags: 32, tq: 217, gw_product: 0) Gateway client - got IP (169.254.0.1) from gateway: 192.168.100.2 Adding default route via gate0 (table 68)
When I run route -n on the ar430w, there's no default route set. I manually ran: route add default gw 169.254.0.1
Next I tried to ping the outside world on the ar430w but it gets no where. Any ideas?
thx mike
Turns out I didn't have the batgat kernel module loaded; now I can connect to the net. However, the default gw is still not automatically set on the repeater
mike
At 12:23 AM 4/9/2009, leongmzlist wrote:
Hi, new at batman. I've got the following done:
- got an airlink ar430w and wrt54gl to ping each other over ad-hoc network
- setup br-lan:0 on each router. ar430w has is 192.168.100.1;
wrt54gl is 192.168.100.2 3. was able to ping each other via br-lan:0 IP 4. using openwrt 8.09 on both routers.
The wrt54gl got the wan/internet link up. I started "batmand -g 1mbit/128kbit br-lan:0" the ar430w doesn't have internet; I started "batmand -r 3 -d 3 br-lan:0"
got this on the ar430w logs:
Interface activated: br-lan:0 Using interface br-lan:0 with address 192.168.100.1 and broadcast address 192.168.100.255 B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5) Adding throw route to 127.0.0.0/8 via 0.0.0.0 (table 68 - lo) Adding throw route to 192.168.1.0/24 via 0.0.0.0 (table 68 - br-lan) Adding throw route to 192.168.100.0/24 via 0.0.0.0 (table 68 - br-lan:0) debug level: 3 routing class: 3 Adding route to 192.168.100.2 via 0.0.0.0 (table 66 - br-lan:0) Found new gateway 192.168.100.2 -> class: 32 - 1024KBit/128KBit Adding default route to 192.168.100.2 (gw_flags: 32, tq: 217, gw_product: 0) Gateway client - got IP (169.254.0.1) from gateway: 192.168.100.2 Adding default route via gate0 (table 68)
When I run route -n on the ar430w, there's no default route set. I manually ran: route add default gw 169.254.0.1
Next I tried to ping the outside world on the ar430w but it gets no where. Any ideas?
thx mike
On Thursday 09 April 2009 15:50:31 leongmzlist wrote:
Turns out I didn't have the batgat kernel module loaded; now I can connect to the net. However, the default gw is still not automatically set on the repeater
The batgat kernel module increases the performance only. You can run the whole setup without it. See the FAQ for more details: http://www.open-mesh.net/wiki/FAQ
Regards, Marek
Hi,
Gateway client - got IP (169.254.0.1) from gateway: 192.168.100.2 Adding default route via gate0 (table 68)
When I run route -n on the ar430w, there's no default route set. I manually ran: route add default gw 169.254.0.1
so far everything is correct but the deprecated "route -n" command shows you only one routing table. As the log indicates the default route went into table 68. You can see it using:
ip route ls table 68
More information regarding the routing tables can be found here: http://www.open-mesh.net/wiki/RoutingVodoo
Next I tried to ping the outside world on the ar430w but it gets no where. Any ideas?
You need to NAT on your gateways (wrt54gl) internet interface. iptables -t nat -I POSTROUTING -o $your_wan_if -j MASQUERADE
Depending on the batman version you use it might be required to NAT on the gate0 interface on the client side in a similar fashion. With batman version 0.3.2 its not necessary anymore.
Regards, Marek
b.a.t.m.a.n@lists.open-mesh.org