From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: johnzeng <johnzeng2013@yahoo.com>,
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.] i found time delay is very high and there are more caution info , if possible , please give me some advisement
Date: Fri, 21 Oct 2016 17:31:35 +0200 [thread overview]
Message-ID: <20161021153135.GC3607@otheros> (raw)
In-Reply-To: <mailman.126.1477060277.610.b.a.t.m.a.n@lists.open-mesh.org>
On Fri, Oct 21, 2016 at 04:31:20PM +0200, johnzeng via B.A.T.M.A.N wrote:
> Date: Fri, 21 Oct 2016 22:31:00 +0800
> From: johnzeng <johnzeng2013@yahoo.com>
> To: b.a.t.m.a.n@lists.open-mesh.org
> Subject: i found time delay is very high and there are more caution info ,
> if possible , please give me some advisement
If I remember correctly, then one typical issue for Arch Linux
users was, that Arch compiles batman-adv with network-coding, even
though it is marked as "Experimental". And that introduces high latency
and/or packetloss.
johnzeug, can you check whether network coding is enabled or
disabled and if it is enabled, whether disabling helps?
(batctl nc disable)
And like Sven asked, what batman-adv version are you using. Not
that long ago the network coding default was changed to disabled
by default even if the module is compiled with NC. Maybe you run
an older batman-adv release?
Regards, Linus
next parent reply other threads:[~2016-10-21 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.126.1477060277.610.b.a.t.m.a.n@lists.open-mesh.org>
2016-10-21 15:31 ` Linus Lüssing [this message]
2016-10-21 14:31 i found time delay is very high and there are more caution info , if possible , please give me some advisement johnzeng
2016-10-21 14:43 ` [B.A.T.M.A.N.] " 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=20161021153135.GC3607@otheros \
--to=linus.luessing@c0d3.blue \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=johnzeng2013@yahoo.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