From: Antonio Quartulli <a@unstable.cc>
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.] mesh losing internal Ilayer3 connectivity
Date: Fri, 20 May 2016 15:33:13 +0800 [thread overview]
Message-ID: <20160520073313.GR12056@prodigo.lan> (raw)
In-Reply-To: <26642956.zsKuDycQ3V@bentobox>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
On Fri, May 20, 2016 at 09:23:24AM +0200, Sven Eckelmann wrote:
> On Thursday 19 May 2016 14:22:58 Nick Schaf wrote:
> > I've run into what sounds like a similar problem, but dove in and found more
> > details. Here's the setup:
> >
> > -19 nodes running BATMAN-adv 2014.14.0 on OpenWrt Chaos Calmer; various
> > hardware (D-Link, BBB, Open-Mesh, WRTnode, TP-Link).
>
> Only scrolled through your mail. But there are two things which I find odd.
> First you use a really old (actually not existing) version of batman-adv.
>
> Then you have some TT problems. I think we had many fixes since then which may
> be related to your problem. But going through 2 years of fixes might be a
> quite hard (at very cumbersome) journey.
>
> Maybe it is really a good idea to try to upgrade to the recent version
> (2016.1+fixes) from the Chaos Calmers openwrt-routing feed on all your nodes.
> Maybe Antonio remembers one special TT/roaming bug and can recommend one to
> test. But most likely testing the current version is easier.
I don't recall any superfix which might magically solve the problems you
are seeing. Therefore I'd just follow Sven's suggestion and try running a recent
version of batman-adv.
Cheers,
--
Antonio Quartulli
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-20 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-02 11:57 [B.A.T.M.A.N.] mesh losing internal Ilayer3 connectivity Karl Auer
2016-05-02 14:54 ` Sven Eckelmann
2016-05-19 14:22 ` Nick Schaf
2016-05-20 7:23 ` Sven Eckelmann
2016-05-20 7:33 ` Antonio Quartulli [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=20160520073313.GR12056@prodigo.lan \
--to=a@unstable.cc \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox