Open-Mesh » batman-adv

the configuration you are showing implies that you are using some kind of OpenWRT. Can you please provide version numbers for OpenWRT and batman-adv?

Also, have you checked whether your ath5k cards work without batman-adv, e.g. by configuring IPs on the Wifi directly without using batman-adv? It is not unlikely that the problem is on the WiFi layer, and not within batman-adv. You can also check "iw adhoc0 station dump" to verify if other stations are actually associated. You may also try to remove encryption of your adhoc device for testing purposes.

Sorry for the slow response.

OpenWRT is version 39772 and batman-adv is 2014.0.0.

iw adhoc0 station dump always shows other stations associated.

I tried removing the encryption, with similar results.

Hi Eric,
have you tried assigning IPs to the adhoc0 interfaces and pinging each other (as simon suggested)?

I've made the following changes to the above /etc/config/network file (at the very end) on one unit:

config 'interface' 'mesh'
option 'ifname' 'adhoc0'
option 'proto' 'static'
option 'ipaddr' '192.168.2.11'
option 'netmask' '255.255.255.0'

I've made the other unit 192.168.2.13

I can ping both 192.168.2.xxx IP addresses, from either end, but not consistently. If I leave both ends idle for a couple of minutes, and then try pinging from 11 to 13, the first 8 packets are lost, and the 9th packet takes just under a minute to return. If I leave them alone for only 30 seconds, pings work from the start. This is without physically moving the devices at all, and only two units on the bench:

/etc/config# ping 192.168.2.13
PING 192.168.2.13 (192.168.2.13): 56 data bytes
64 bytes from 192.168.2.13: seq=9 ttl=64 time=995.797 ms
64 bytes from 192.168.2.13: seq=10 ttl=64 time=0.603 ms
64 bytes from 192.168.2.13: seq=11 ttl=64 time=0.685 ms
64 bytes from 192.168.2.13: seq=12 ttl=64 time=0.671 ms
64 bytes from 192.168.2.13: seq=13 ttl=64 time=0.681 ms
64 bytes from 192.168.2.13: seq=14 ttl=64 time=0.691 ms
64 bytes from 192.168.2.13: seq=15 ttl=64 time=0.682 ms

The 9th packet is always the successful one, and it's always just under a second to return.

Probably not a batman-adv problem. Let me know your thoughts and then you can probably close the ticket.

The interruption you have looks like the node is sending the ARP request and this requires some time (for whatever reason) to get answered. If you leave them alone for few seconds only, then they will both have the old ARP entries and so they do not need to send any request.

This is not a batman-adv problem because batman-adv is not involved at all in this case: you are using the adhoc interfaces directly.

Antonio,

Thanks for your help.

The root problem appears to have been a change to the OpenWrt options in buildroot. There is not a specific wpa_supplicant option for P2P. If I choose that, everything seems to work. The old option of wpad_mini, etc. no longer work.

Please go ahead and close this.

Thanks again.