On Wednesday 29 April 2009 22:09:45 Nathan Wharton wrote:
Yes. It occurs if the interfaces through which the gateway and client can communicate are not the interfaces listed first on the command line.
I just cooked a patch that should ignore these IP inconsistencies. Please try revision 1255 and let us know if it helped.
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.
Ok, you are right. In your setup it makes sense.
Regards, Marek