From: Sven Eckelmann <sven@narfation.org>
To: Corey Combs <combsca90@gmail.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Version help
Date: Mon, 22 Oct 2018 20:15:33 +0200 [thread overview]
Message-ID: <3971667.ui1v05AXcD@sven-edge> (raw)
In-Reply-To: <CAPzaX0ic23YurEjexLgNq4x6aaAp38f4Nj=iMfNDbLXkHCwhXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1634 bytes --]
On Montag, 22. Oktober 2018 19:51:21 CEST Corey Combs wrote:
> I'm currently working on a project that uses BATMAN for a mesh network
> across multiple Beagle Bone Blacks which are running a Debian version
> 7.9 at the moment. They also are running batctl debian-2012.1.0-1
> [batman-adv 2012.5.0].
Uhm, 2012.5.0 is extreme old and I would advise not to use such an old
version. And beside that, it is using COMPAT_VERSION 14 [1]. The current
COMPAT_VERSION is 15 - batman-adv kernel modules with different
COMPAT_VERSIONs cannot talk to each other.
> I would like to connect a laptop to the
> existing network either using Debian or Ubuntu, however I have run
> into issues with compatibility. I configured everything identically
> with the laptop and I believe I'm connected to the network, but I
> cannot see any other devices on the network. Is it advisable to
> upgrade the version of batctl on the 'bone or downgrade the version on
> debian or Ubuntu so that the versions align? Or is there something
> else I am missing in my efforts?
Why batctl? The biggest problem here is the extreme old batman-adv version
which is not compatible with every batman-adv version since 2014.
And btw. you didn't tell us what batman-adv version your laptop is using. If
they are really using the same version then it could be that either the laptop
or the beagle bone blacks have problems with their wifi driver. Wouldn't be
the first time that things like broadcast or unicast communication via IBSS
is broken with some wifi hw/driver.
Kind regards,
Sven
[1] https://www.open-mesh.org/projects/batman-adv/wiki/Compatversion
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-10-22 18:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 17:51 [B.A.T.M.A.N.] Version help Corey Combs
2018-10-22 18:11 ` Simon Wunderlich
2018-10-22 18:15 ` Sven Eckelmann [this message]
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=3971667.ui1v05AXcD@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=combsca90@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