Hi Linus,
nice to hear from you again.
Am 04.01.2013 um 06:34 schrieb Linus Lüssing:
What were the exact batman-adv versions at the time you made those graphs for the shown nodes as well as any intermediate nodes (although if I got your setup right then the nodes in those graphs do not have any intermediate batman-adv hops involved, do they?)?
Does it make a difference if you make the entries in the neighbor solicitation table permanent (e.g. with 'ip -6 neigh')?
Do the same spikes appear with a 'batctl ping' (or if adding such graphs is quite a hassle then at least, is the overall 'batctl ping' packet loss similar to the one from the ip ping)?
Do you see any "Changing route towards" events in the batman-adv logs between these supposedly always direct neighbors - if yes, maybe with a similar frequency? Or even better, check whether the same packet loss appears when isolating any of such pairs of nodes so that no batman-adv route changes could happen at all.
For some reason, the spikes disappeared around midnight - and I don't know why. Maybe batman-adv converged to a different plan (or converged at all) or the Flying Spaghetti Monster our network to work nowadays.
I'll go one inspecting this issue, but I cannot answer any of your questions. :-(
Keep smiling yanosz