On 06/02/15 13:38, Sven Eckelmann wrote:
On Friday 06 February 2015 08:26:04 Antonio Quartulli wrote:
Could you please be a bit more specific about the issue you are talking about?
I can only talk about the simple two node installation I had when I was forced to write the wireshark-batman-adv dissector for v15. I just placed them next to each other and tried to ping the other one (not sure anymore if it was the node directly or two other devices plugged in the ethernet port of the devices). And I think there was a reboot of one node and a ARP cache flush involved. I've expected to see the 4addr packets when capturing on the wireless and then having both nodes talking to each other. This was not working. I could only communicate after disabling DAT... but of course the communication which I wanted to capture wasn't happening.
Thanks for the explanation Sven.
To me this looks like the caching effect of DAT: bat0 is likely to change MAC address everytime you recreate the interface (unless you statically assign the MAC) therefore I presume that the other node (the one which did not reboot) was still caching the old bat0 MAC address (each entry requires some minutes before being invalidated/refreshed).
This means that any communication willing to contact the rebooted node was targetting the old address and therefore the two were not be able talk until the cache was refreshed.
Can this be the case?