Am 05.09.2011 10:06, schrieb Marek Lindner:
I have tried to reproduce your issue but was unsuccessful. Could you help
narrowing down the cause by providing some more information ?
For instance:
* What is the simpliest setup that can provoke the issue ? Does it also happen
if you only involve 2 nodes ? Or 3 / 4 / 5 ? Does the problem go away if you
reduce the number of interfaces on each node ?
* You provided some logs showing additions / deletions of a non-existing mac
address and you said this would go away after a while. What do the logs say
when the problem is about to disappear ?
* Are the nodes that often exhibit this flakiness far apart or direct
neighbors ? What does the topology look like ? Again, the simplier the setup
the better.
Regards,
Marek
Hello Marek,
i needed to get this working so i switched to 2011.2 last weekend and
the problems are gone.
So it seems it's a bug introduced in 2011.3.
The network on which i had the problems is live and in use, so i can't
make any further tests on it right now.
I have some similar devices as spare parts. I'll try to set them up and
reproduce the problems - but that can take a while.
What i can tell you is:
- every node has only one wlan-network on which batman runs and only the
node itself uses the bat0 interface - no bridging, no routing
- at the end, most of the time only the directly connected nodes were
reachable via a normal ping - the "hopping" was not working
- i had the *feeling* that the problems got bigger the more nodes we added
- also i *think* the problems began when we mixed Fonera- and
TP-Link-devices (sightly different architecture i think)
- the log was always spammed with messages - because of the tiny devices
i use it's not easy to save the log and inspect it when the connection
is working again - which can take an hour...
Thank you for your help. I'm sorry, that i can't provide you more infos
to track down the bug.
Tobias
