From: Marek Lindner <mareklindner@neomailbox.ch>
To: "b.a.t.m.a.n@lists.open-mesh.org" <b.a.t.m.a.n@lists.open-mesh.org>
Cc: Berkay Demirci <berkay.demirci@protonmail.com>
Subject: Re: About Throughput in BATMAN_V
Date: Sun, 19 May 2024 16:33:44 +0200 [thread overview]
Message-ID: <5797991.sP1CNn8AQk@rousseau> (raw)
In-Reply-To: <livakUAT6XSpa0RoYB-m2_tK2wjUm-5ZdcvIBa2G1Hw53hhh_tlHIwr2B5nOomayXajuotSI5NGl956q_aZjZG5yVRu5C-uth6lNJcUNCtw=@protonmail.com>
On Monday, 15 April 2024 10:20:20 CEST Berkay Demirci wrote:
> In the test scenario, two nodes move away from each other so packet loss
> increases over time but it increases more in network 1, and since the
> throughput values are overriden, batman still chooses that network based on
> that value. Only when OGM messages stop reaching in network 1, batman
> switches to network 3 and we see the PDR increasing to 1 immediately when
> that happens.
Correct, the throughput override is a static value and does not adjust to a
changing environment. On wireless interface the estimated throughput would be
adjusted as the nodes move away from each other (batman-adv is able to read
estimated throughput values from the WiFi driver).
> Basically we want batman to be able to switch earlier than that and that's
> why I asked about the throughput meter implementation because the batman
> overriden throughput value doesn't consider packet losses.
Exactly, the throughput override does not consider anything other than the
configured value.
> Another idea we had was to manually change the throughput value via a script
> if packet loss increases too much or something like that, we haven't thought
> in detail yet. So I'm asking if you could have any suggestion that considers
> packet loss as well.
It seems you are attempting to simulate a wireless environment using wired
devices. Wired devices typically can not "move away" from each other, hence
you are running into this issue with your simulation approach.
Maybe mac80211 hwsim is an option for you? I've never used it, so can't
provide specific suggestions.
Have you considered testing on a wireless testbed?
> Otherwise, I'd also appreciate the assistance you could provide for the
> patches for tp fallback implementation. Does it work at all at its current
> state even with problems or is it not there yet?
Your question isn't entirely clear to me. As a first step, you'd have to rebase
the tp meter patches to work on your chosen batman-adv version. How much work
that might be is hard to ascertain without trying it.
Cheers,
Marek
prev parent reply other threads:[~2024-05-19 14:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 12:56 About Throughput in BATMAN_V berkay.demirci
2024-04-03 13:16 ` Marek Lindner
2024-04-04 7:00 ` berkay.demirci
2024-04-04 10:00 ` Marek Lindner
2024-04-05 8:06 ` berkay.demirci
2024-04-08 8:28 ` Marek Lindner
2024-04-15 8:20 ` Berkay Demirci
2024-04-15 9:13 ` Marek Lindner
2024-04-15 18:27 ` Berkay Demirci
2024-05-19 14:33 ` Marek Lindner [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=5797991.sP1CNn8AQk@rousseau \
--to=mareklindner@neomailbox.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=berkay.demirci@protonmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).