On Tue, Apr 28, 2009 at 10:14 PM, Marek Lindner lindner_marek@yahoo.de wrote:
I'm not 100% about your setup. The problem occurs if the gateway client tries to retrieve an IP address from the gateway via the gateways secondary interface ?
Yes. It occurs if the interfaces through which the gateway and client can communicate are not the interfaces listed first on the command line.
On the gateway, I am using: batmand -d 3 -g 11000 -a 10.2.1.0/24 --disable-client-nat --hop-penalty 5 --purge-timeout 10000 ath0 eth0 ath0 is IP 10.0.2.1/16 eth0 is IP 10.255.2.1/16
On the gateway the option "--disable-client-nat" has no effect. I just commited an additional warning that should indicate that in the future.
Regards, Marek
Will it still be in effect if it is no longer the gateway, and the gateway moves to another node in the mesh? All the nodes start with -r 2, and a batmand -c -g is issued on a node that finds an uplink. If it loses the uplink, batmand -c -r 2 is issued, and --disable-client-nat should still be on.