Hello,
I had batman 0.2 + freifunk working.
Each router was 10.0.0.* and had the same wlan address. Something happened and then batman just started silently dying on the gateway router 10.0.0.1 (with the address 10.0.2.146 from the router connected to the internet). I erased nvram and reinstalled with separate 10.0.5.* addresses for the wlan and that seemed to work (with no http access to the routers and ssh via the 10.0.5.* addresses).
I had wanted to stay with batman 0.2 because of the web interface. That's no longer practical. 0.3 is the preferred batman, so I should use it. I've taken a look at the docs: https://dev.open-mesh.net/svn/batman/trunk/batman/INSTALL
and "RoutingVoodoo."
assuming a fresh install of freifunk with *no OLSR* running what parameters would I want to set:
adsl | 10.0.2.1 [home router ppoe] | freifunk 1 [gateway] does subnet matter? lan 10.0.0.1 wlan do I want 10.0.0.1 or 10.0.5.1? wan via dhcp? essid, bssid, channel all the same for ff routers myessid, 02:CA:FF:EE:BA:BE, 12, ad-hoc what batman parameters will I want to pass? shall I create an init script or is there one? 0.2 had the init and the minutely 'watchout4batman' | | | freifunk n non-gateway nodes lan 10.0.0.n? wlan? wan via dhcp? batman -p 10.0.0.1 -r 3 (or 10.0.2.146 freifunk 1's wan address) eth1 br0 vlan1?
Anything else I should be aware of? Any other recommendations? (e.g. "Scrap that this is exactly how you do it: 1. 2. 3. "
I guess it was a minor mystery that I had 0.2 working. I've gone through and purged the nvram and set wlan with it's own LAN ip. As long as I only run batman on the wireless interface things seem quite smooth and easy.
ff1# batmand -g 8 eth1 ff2# batmand eth1
It finds the gateway, there's internet access. Any suggestions for an init script?
In 0.2 I successfully ran batmand br0 and things worked fine. Trying that in 0.3 just locked things up.
Hi,
Are you trying to run batman with whiterussian (i am not sure of freifunk build)? if so the init script installed with the batman 0.3 package does not support nvram. it supports uci (as noticed @ https://dev.openwrt.org/cgi-bin/trac.fcgi/browser/packages/net/batman/files/...)
If your init script is similar to the one in that openwrt link... you can get stuff working by replacing the uci get variables with valid nvram variables like interface=$(uci get batmand.general.interface) to interface=$(nvram get wireless_interface) ... i dont remember the variable name correctly.
Regards, -- Vinay Menon
Vinay Menon wrote:
Hi,
Are you trying to run batman with whiterussian (i am not sure of freifunk build)?
Yes, Freifunk is Whiterussian.
if so the init script installed with the batman 0.3 package does not support nvram. it supports uci (as noticed @ https://dev.openwrt.org/cgi-bin/trac.fcgi/browser/packages/net/batman/files/...)
If your init script is similar to the one in that openwrt link... you can get stuff working by replacing the uci get variables with valid nvram variables like interface=$(uci get batmand.general.interface) to interface=$(nvram get wireless_interface) ... i dont remember the variable name correctly.
Thank you. I'll take a look.
Does batmand 0.3 automatically identify gateways?
I notice that simply typing batmand -g 8 eth1 isn't enough to identify a new gateway. Do I have to restart batmand on all the nodes? or specify batmand -p newgwip -r 3 eth1 to get them to identify the new gateway?
I thought there was a way to automatically use a gw if another gw was down?
I don't seem to be really running batman. batman -c -d 1 shows all the nodes batman -c -d 2 shows there are no gateways although I had specified one. Apparently, I'm just running an ad-hoc network that's happens to be running batman but not using it.
Sorry for the 36000 posts.
batmand -g 5mb eth1 vlan1 #for gw? batmand -r 3 eth1 #for nodes? suggestions?
Sorry again.
Don Davis wrote:
Does batmand 0.3 automatically identify gateways?
I notice that simply typing batmand -g 8 eth1 isn't enough to identify a new gateway. Do I have to restart batmand on all the nodes? or specify batmand -p newgwip -r 3 eth1 to get them to identify the new gateway?
I thought there was a way to automatically use a gw if another gw was down? _______________________________________________ B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
Simon Wunderlich wrote:
On Thu, Jul 17, 2008 at 03:13:17PM -0500, Don Davis wrote:
batmand -g 5mb eth1 vlan1 #for gw?
Hello Don,
try "-g 5mbit" instead of "-g 5mb". Seems this wrong option is silently ignored ...
best regards, Simon
Thank you. That did do the trick.
Is the gateway detection for announced gateways? Is there a script that can probe to see if the router is a gateway and if so make it available?
I was under the mistaken impression that because I hadn't configured olsr (nor had I disabled it) that I was not running OLSR. Thanks to Sven Ola it seems that it was a zero conf olsr. Without specifying ifconfig eth1:bat 10.0.5.* the batmand eth1 command seemed to work (the same for batmand -g 5mbit eth1 vlan1) and batmand -c -d 1/2/3/4 show batman running.
Is it normal that I have to kill and restart batman for the new gateway to be noticed?
Hello Don,
Debug Level 2 will list the available gateways. There is no need to restart BATMAN, it will notice the new gateway available gateways automatically (the gateways are announced with the BATMAN-packets). One of the gateways will be selected depending on the configuration at -r.
You might want to read the howto [1] for further information. :) Please ask again if your question is not answered there.
regards, Simon
[1] http://open-mesh.net/batman/doc/batmand_howto.pdf
On Thu, Jul 17, 2008 at 05:33:31PM -0500, Don Davis wrote:
Simon Wunderlich wrote:
On Thu, Jul 17, 2008 at 03:13:17PM -0500, Don Davis wrote:
batmand -g 5mb eth1 vlan1 #for gw?
Hello Don,
try "-g 5mbit" instead of "-g 5mb". Seems this wrong option is silently ignored ...
best regards, Simon
Thank you. That did do the trick.
Is the gateway detection for announced gateways? Is there a script that can probe to see if the router is a gateway and if so make it available?
I was under the mistaken impression that because I hadn't configured olsr (nor had I disabled it) that I was not running OLSR. Thanks to Sven Ola it seems that it was a zero conf olsr. Without specifying ifconfig eth1:bat 10.0.5.* the batmand eth1 command seemed to work (the same for batmand -g 5mbit eth1 vlan1) and batmand -c -d 1/2/3/4 show batman running.
Is it normal that I have to kill and restart batman for the new gateway to be noticed? _______________________________________________ B.A.T.M.A.N mailing list B.A.T.M.A.N@open-mesh.net https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
Debug Level 2 will list the available gateways. There is no need to restart BATMAN, it will notice the new gateway available gateways automatically (the gateways are announced with the BATMAN-packets). One of the gateways will be selected depending on the configuration at -r.
I'm a little curious about setting up an init script for batmand 0.3 Using freifunk + batmand 0.3:
S97startnode.sh #! /bin/sh batmand eth1
Works fine for the nodes. However, S97startnode.sh #! /bin/sh batmand -r 3 eth1
does not find the gateway. I thought the default routing class was 3 or would respond fastest but apparently not.
More of a concern though is writing an init script for a gateway. S97gateway.sh #! /bin/sh batmand -g 5mbit eth1 vlan1
at best has to be killed and restarted for batmand to work; worst case scenario it freezes the router. I need to find a way to get it to wait for the dhcp lease before starting (I guess). Though doesn't the dhcp lease come after S99?
What about a script (much like watchout4batman which I haven't seen for batman 0.3) that can be run as a cronjob that does two things 1) makes sure batmand is up and running 2) if an interface is available on vlan1 (or whatever the wan port is on) then restart batmand and announce the node as a gateway?
For a gateway is there any advantage to batmand -g 5mbit eth1 vlan1 over batmand -g 5mbit eth1?
b.a.t.m.a.n@lists.open-mesh.org