On Fri, Feb 24, 2017 at 06:56:58PM +0100, Linus Lüssing wrote:
On Fri, Feb 24, 2017 at 10:48:35AM -0600, Derick Roman De Leon Leal wrote:
Thanks for the quick reply Linus,
No transmission on IPv4
If that's for the adhoc0 interface directly then this seems to be a wireless driver issue and not a batman-adv one :(.
Hm, if I'm not mistaken then the OM2P-HS should have an Atheros AR9285 chipset. So an ath9k driver which many people use in adhoc mode for meshing.
Someone suggested that I should use a bssid that starts with 02 (eg. 02:12:34:56:78:9A). Is this a requirement for the mesh to work?
Not a "requirement for the mesh to work", afaik. But when a MAC address is self-generated, then it should have the second lowest bit set:
This is true for the interface MAC address, but this should not apply for the Cell-ID/BSSID. It can be a random ID.
Cheers,