From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: Batman_V Originator Loop Issue
Date: Mon, 27 Jul 2020 20:36:25 +0200 [thread overview]
Message-ID: <20200727183625.GA2340@otheros> (raw)
In-Reply-To: <20200727162815.30286.54503@diktynna.open-mesh.org>
On Mon, Jul 27, 2020 at 04:28:15PM -0000, lavincent15@gmail.com wrote:
> Linus
>
> I would love to try it out and help with the development, but unfortunately I do not have the time to do that. My internship is coming to a close, and I need to use a version I know works to provide good data.
Oh, okay, good luck with the results then!
> Side note* Do you think you could provide me with a rough equation for when a node decides to use a hop instead of a direct connection? I'm particularly interested in how the nodes use the hop penalty in the equation. Does speeding up the interval increase the speediness of its decision? I'm using this in a mobile node environment and I need it to dynamically switch to the most stable connection.
The metric, including the hop-penalty for BATMAN V is described here:
https://www.open-mesh.org/projects/batman-adv/wiki/Ogmv2#322-Metric-Update
Or here in the code, in this short function:
https://elixir.bootlin.com/linux/v5.7.8/source/net/batman-adv/bat_v_ogm.c#L470
And then the algorithm will compare if the resulting throughput
metric is higher via a direct connection or over another hop even
with the (either) hop or half-duplex penalty applied.
Hope that helps.
Regards, Linus
prev parent reply other threads:[~2020-07-27 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 19:47 Batman_V Originator Loop Issue lavincent15
2020-07-08 9:15 ` Simon Wunderlich
2020-07-08 14:44 ` lavincent15
2020-07-08 15:26 ` lavincent15
2020-07-09 20:33 ` Linus Lüssing
2020-07-24 10:02 ` Linus Lüssing
2020-07-24 15:00 ` lavincent15
2020-07-24 20:23 ` Linus Lüssing
2020-07-27 16:28 ` lavincent15
2020-07-27 18:36 ` Linus Lüssing [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=20200727183625.GA2340@otheros \
--to=linus.luessing@c0d3.blue \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.