On Wed, Jul 4, 2012 at 9:43 AM, Guido Iribarren guidoiribarren@buenosaireslibre.org wrote:
On Wed, Jul 4, 2012 at 6:12 AM, Simon Wunderlich simon.wunderlich@s2003.tu-chemnitz.de wrote:
Hello Guido,
gw-mode is activated in all mesh nodes, not only in colmena-casa and f8d11504758 it's set to client on every node except f8d11504758, which has gw_mode=server
As far as i can recall, disabling gw_mode=client in every mesh node, solved the problem. But now that i found out about this "batctl td" thing, i'm in doubt about the validity of the previous statement :( i should check again and report.
I can now confirm this.
if i set gw_mode=off in a particular mesh node, DHCP requests originating from that node work correctly, even when the mesh node client is claimed by the "wrong" backbone node.
in this scenario: * ruth_eth0 on -1 by colmena-casa [ ] (7a27) * hquilla_eth0 on -1 by colmena-casa [ ] (7a27)
root@ruth:~# batctl gw off root@ruth:~# /sbin/udhcpc -t 0 -i br-lan:ipv4 -f -R udhcpc (v1.19.4) started Sending discover... Sending select for 10.254.0.131... Lease of 10.254.0.131 obtained, lease time 600
root@hquilla:~# batctl gw client root@hquilla:~# /sbin/udhcpc -t 0 -i br-lan:ipv4 -f -R udhcpc (v1.19.4) started Sending discover... Sending discover... Sending discover...^C
when hquilla sends the request, this is received at f8d11504758 interface wlan0-2 BAT colmena-casa > f8d11504758: UCAST....... and gets dropped (doesn't reach dnsmasq)
when ruth (gw_mode=off) sends the request, this is received at f8d11504758 interface wlan0-2 BAT colmena: BCAST, orig ruth, ...... (then rebroadcasted several times) and it reaches dnsmasq properly.
If you prefer the raw "batctl td" for some eye-injuring reason, here you go: http://pastebin.com/HNBg01hR
hope that helps!
Gui