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>
Subject: Re: [B.A.T.M.A.N.] Node freezes but still alive
Date: Fri, 24 Feb 2017 18:56:58 +0100 [thread overview]
Message-ID: <20170224175658.GF4202@otheros> (raw)
In-Reply-To: <CAM0tZWaO3F5D1KzPX85V4ydGSj_a0cXc29xhchUwTxVcnexVdA@mail.gmail.com>
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
[*]: https://lede-project.org/releases/17.01/start
next prev parent reply other threads:[~2017-02-24 17:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-24 16:48 [B.A.T.M.A.N.] Node freezes but still alive Derick Roman De Leon Leal
2017-02-24 17:56 ` Linus Lüssing [this message]
2017-02-25 0:55 ` Antonio Quartulli
-- strict thread matches above, loose matches on Subject: below --
2017-02-25 18:38 Derick Roman De Leon Leal
[not found] <58aff662.222c9d0a.f11b.d39bSMTPIN_ADDED_MISSING@mx.google.com>
2017-02-24 16:48 ` Derick Roman De Leon Leal
2017-02-23 23:37 Derick Roman De Leon Leal
2017-02-24 8:28 ` Linus Lüssing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170224175658.GF4202@otheros \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.