[B.A.T.M.A.N.] Issues with mesh routing

[B.A.T.M.A.N.] Issues with mesh routing

[Phill Raynsford]

Hi,

We're using batman-adv 2018.2 (with BATMAN IV routing algorithm) to mesh linux hosts together via wlan interfaces. 
We've built our own discovery service that uses broadcast packets to announce new mesh neighbours.
Recently, our discovery service has been successfully listening to and receiving these broadcast packets, however attempting to ping any of these hosts through batctl fails. On closer inspection, the originators table is entirely empty. This suggests to me that routing is broken in some way, which is why broadcast packets seem to be transmitted OK but we can't talk to specific hosts.

Has anyone ever seen this kind of thing occur before, and perhaps to fix it? I haven't seen any suspicious messages in any of the system logs, and other batctl diagnostic outputs seem OK.

Thanks for the help,
Phill
 

Re: [B.A.T.M.A.N.] Issues with mesh routing

[Sven Eckelmann]

[-- Attachment #1: Type: text/plain, Size: 562 bytes --]

On Tuesday, 5 March 2019 11:03:31 CET Phill Raynsford wrote:
[...]
> Has anyone ever seen this kind of thing occur before, and perhaps to fix it? I haven't seen any suspicious messages in any of the system logs, and other batctl diagnostic outputs seem OK.

Seen this with broken or misconfigured wifi drivers. For example drivers which 
were changing broadcast frames to unicast frames (which breaks OGMs because 
they must be broadcasts) or some of them were changing the source address of 
broadcast frames (which is also not acceptable).

Kind regards,
	Sven

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]