I am using B.A.T.M.A.N. 0.3.2-beta rv1246 with the batgat module. Internet tunneling works well on the first interface mentioned on the command line. Tunneling does not work on the secondary interface, and it floods the log file on the gateway with:
Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash Apr 28 17:38:09 OpenWrt user.debug kernel: batgat: [get_ip_addr:645] found client in hash
And on the client with:
Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip request: sender IP is not gateway IP Apr 28 17:33:10 OpenWrt user.notice batmand: Error - can't receive ip from gateway: number of maximum retries reached
Is there something I can do to get it to work on the secondary interface?
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 client, I am using: batmand -d 3 -r 2 -a 10.1.11.0/24 --disable-client-nat --hop-penalty 5 --purge-timeout 10000 ath0 eth0 ath0 is IP 10.0.1.11/16 eth0 is IP 10.255.1.11/16
Thanks in advance for any help on this.
Hi,
Is there something I can do to get it to work on the secondary interface?
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 ?
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
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.
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
On Wed, Apr 29, 2009 at 10:17 PM, Marek Lindner lindner_marek@yahoo.de wrote:
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.
Works perfectly here now. I hope that didn't mess something else up.
On Friday 01 May 2009 00:29:29 Nathan Wharton wrote:
I just cooked a patch that should ignore these IP inconsistencies. Please try revision 1255 and let us know if it helped.
Works perfectly here now. I hope that didn't mess something else up.
Great! Actually that should not be a problem but let me know if you find something.
Regards, Marek
b.a.t.m.a.n@lists.open-mesh.org
-
Marek Lindner -
Nathan Wharton