Thanks for the quick reply Linus,
No transmission on IPv4, haven't tried on IPv6 but I assume is going to be the same. 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?
Should I share a batman-adv log? which packet type should be more useful?
Thanks a lot!!
Kind Regards, Derick
---------- Forwarded message ---------- From: "Linus Lüssing" linus.luessing@c0d3.blue To: The list for a Better Approach To Mobile Ad-hoc Networking b.a.t.m.a.n@lists.open-mesh.org Cc: Bcc: Date: Fri, 24 Feb 2017 09:28:11 +0100 Subject: Re: [B.A.T.M.A.N.] Node freezes but still alive Hi Derick,
On Thu, Feb 23, 2017 at 05:37:55PM -0600, Derick Roman De Leon Leal wrote:
I have a little setup with two nodes and one gateway, from time to time one of the nodes just stops transmitting data.
Very odd indeed. Can you check whether transmitting IPv4 or IPv6 packets on adhoc0 directly still works when this happens?
Cheers, Linus
B.A.T.M.A.N mailing list B.A.T.M.A.N@lists.open-mesh.org https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n
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:
https://en.wikipedia.org/wiki/MAC_address#Address_details
Not sure, maybe you just hit a bad OpenWRT revision? Maybe give the new LEDE release [*] or a newer OpenWRT version a try?
Regards, Linus
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,
b.a.t.m.a.n@lists.open-mesh.org
-
Antonio Quartulli -
Derick Roman De Leon Leal -
Linus Lüssing