From: Sven Eckelmann <sven@narfation.org>
To: 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 09:23:24 +0200 [thread overview]
Message-ID: <26642956.zsKuDycQ3V@bentobox> (raw)
In-Reply-To: <a1c140db68d543d482a22adfbac42670@BLUPR97MB0100.062d.mgd.msft.net>
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
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.
But thanks for gathering all the info
Kind regards,
Sven
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-05-20 7:23 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 [this message]
2016-05-20 7:33 ` Antonio Quartulli
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=26642956.zsKuDycQ3V@bentobox \
--to=sven@narfation.org \
--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