From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: umut deniz <umut.deniz@gmail.com>
Subject: Re: [B.A.T.M.A.N.] Fwd: nodes start disappearing after a certain node count
Date: Sun, 24 Feb 2019 22:22:37 +0100 [thread overview]
Message-ID: <1711580.CLzo8a4Rc7@sven-edge> (raw)
In-Reply-To: <CAHh66V-79d--F=d-Rx+af6Vffm09bs=-EOTiK4dtB3+r-E91Ag@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1468 bytes --]
On Sunday, 24 February 2019 21:48:18 CET umut deniz wrote:
> my current platform is ti's beagleboneblack wireless board running openwrt
> distribution (the required bbbw dtb and wl1835 driver firmware applied) with
> batman enabled and configured. with this high level description of the
> components i am able to build a mesh network 6 nodes (i.e. bbbw cards) but as
> soon as i introduce a 7th card into the network batman mesh becomes unresponsive
> as the last seen times start to increase and finally, after 200 seconds all the
> nodes drops from the originator and neighbor tables which could be inspected
> with < :#batctl o> and < :#batctl n> commands respectively. all the cards are on
> the same table and well powered.
[...]
> i researched for a while for the cause with no avail. i would appreciate any
> kind of help to point me to the right direction to solve this.
Please don't use things like wl1835 when building larger meshes. It is known
that these kind of devices only support a very limited amount of peers and
are most of the time only (more or less) stable in management mode (client).
And afaik, the wlcore driver (like other TI wirelss drivers) is also orphaned.
If you're wifi link/driver doesn't work, batman-adv can also do nothing to fix
it.
Rule of thumb: If it is a USB/SDIO wifi device, start waving your hands in the
air, scream and run away. This strategy is also helpful in other wifi related
situations.
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-24 21:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHh66V8N6KCqGdxnMQpHTaqjLbfMwWyGrRvjZY+P20W3-UF4Hw@mail.gmail.com>
2019-02-24 20:48 ` [B.A.T.M.A.N.] Fwd: nodes start disappearing after a certain node count umut deniz
2019-02-24 21:22 ` Sven Eckelmann [this message]
2019-02-25 14:06 ` umut deniz
2019-02-25 14:19 ` Sven Eckelmann
2019-02-25 16:00 ` Linus Lüssing
2019-02-25 16:50 ` Sven Eckelmann
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=1711580.CLzo8a4Rc7@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=umut.deniz@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox