From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: "Fox, Fred" <Fred.Fox@ars.usda.gov>
Subject: Re: [B.A.T.M.A.N.] Debian Testing kernel module, BATMAN_V not supported
Date: Fri, 16 Feb 2018 19:32:12 +0100 [thread overview]
Message-ID: <8487269.uRpeearfos@sven-edge> (raw)
In-Reply-To: <16f5ebd27da0414cac5517460d4da8b4@DM2PR0201MB028.001f.mgd2.msft.net>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Freitag, 16. Februar 2018 18:52:45 CET Fox, Fred wrote:
> In testing BATMAN_IV with my hardware, I noticed that as long as Node A could see Node C, it would communicate directly with it, even if the links between nodes A-B and nodes B-C had much higher throughput (tested with batctl tp). Would like to see if BATMAN_V would select the higher throughput path.
Forgot something: You can also increase the hop penalty [1] on all nodes to
let B.A.T.M.A.N. IV know that it should prefer shorter paths (as in hop
count - not as in packet loss).
But first try to increase the multicast rate on all nodes. Also make sure that
the wifi driver/hw is actually using the multicast rate setting. For example
by monitoring the rate with wireshark [2] or a similar tool on a wifi monitor
interface [3].
Kind regards,
Sven
[1] https://www.open-mesh.org/projects/batman-adv/wiki/Tweaking#hop-penalty
[2] https://www.wireshark.org/
[3] https://wireless.wiki.kernel.org/en/users/documentation/iw#adding_interfaces_with_iw
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-02-16 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 17:52 [B.A.T.M.A.N.] Debian Testing kernel module, BATMAN_V not supported Fox, Fred
2018-02-16 18:21 ` Sven Eckelmann
2018-02-16 18:32 ` 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=8487269.uRpeearfos@sven-edge \
--to=sven@narfation.org \
--cc=Fred.Fox@ars.usda.gov \
--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