and don't declare an OpenWRT "network" for it. Perhaps it is related to that?
I remember going in circles with getting a named interface without all the overlay of an OpenWRT network associated with it, but, alas, not all the details anymore.
Thanks, though I think the configurations for 802.11s is different to batman-adv
I should also mention that the same configuration works on a different board but I notice that on the other board a wpa_supplicant process is launched like:
That's a reasonable thing to look at. I believe you should be able to at least see interface creation in the logs. I run without an OpenWrt "network" as I don't bridge the interface proper, but rather the tunnel endpoints that run over the interface.
From my logs (routed through syslog-ng)
2018 Aug 20 19:57:57 office info kernel: [ 38.782894] IPv6: ADDRCONF(NETDEV_UP): mesh0: link is not ready
Use iw list to check if your wifi driver supports adhoc mode (IBSS).
It is common to use a "dumb" 802.11s (mesh) mode radio underneath BATMAN, instead of adhoc. Turning off mesh_fwding gives the mesh routing control to BATMAN. Of course all the nodes in the mesh must use the same radio mode.