public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
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-adv packet retranslation
Date: Mon, 25 May 2020 19:27:32 +0200	[thread overview]
Message-ID: <7073983.9WrHQ1J9Fu@rousseau> (raw)
In-Reply-To: <CAOVt3fGODcxuZAigHuHSgPED5Y67kB2NV2encCyDz4qMFy7gyQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1459 bytes --]

On Monday, 25 May 2020 19:21:50 CEST Alexey Ermakov wrote:
> > I am surprised you still are configuring a throughput override of
> > 100kbit/s. What's the idea behind this configuration ?
> 
> I have two channels between nodes (actually more, but this doesn't matter
> now) 1) Radio modem, connects as follows:
>    NODE1(eth0)<-->modem(radio)<-->(radio)modem<-->(eth0)NODE2
> eth0 interface have 100mbit/s speed and batman detects it as 100mbit/s.
> radio has 145kbit/s, and actual speed of this channel is 145kbit/s
> 
> 2) eth1 Ethernet channel. Speed of this channel is 100mbit/s
>    NODE1(eth1)<---->(eth1)NODE2
> 
> Now make a test:
> 1) Set up eth0 modem channel
> 2) Disconnect eth1 channel
> 3) Turn on nodes - batman saw eth0 channel between nodes and detected
> speed 100mbit/s (because speed between node and modem is 100mbit/s, as
> I understand)
> 4) plug eth1 cable in - At this moment I expect batman switch to eth1
> channel because it has real 100mbit/s speed. But batman doesn't
> switch, because it detects eth0 as 100mbit/s too.
> Therefore I override throughput of eth0, actually batman detects
> incorrect speed on eth0.

If you have to configure the throughput manually why not configure the link with 
something like 5mbit/s instead of 100kbit/s ? Batman-adv does not care that 
this throughput is not exact. All that matters is provide input to the 
algorithm to allow batman-adv to make smart choices.

Kind regards,
Marek Lindner

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-05-25 17:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-21 17:13 Batman-adv packet retranslation Alexey Ermakov
2020-05-22  6:25 ` Sven Eckelmann
2020-05-24 14:43   ` Alexey Ermakov
2020-05-24 15:29     ` Marek Lindner
2020-05-24 15:49       ` Alexey Ermakov
2020-05-24 15:55         ` Marek Lindner
2020-05-24 16:28     ` Sven Eckelmann
2020-05-24 21:53       ` Alexey Ermakov
2020-05-25  8:57         ` Marek Lindner
2020-05-25  9:23           ` Alexey Ermakov
2020-05-25 13:34         ` Marek Lindner
2020-05-25 14:59           ` Alexey Ermakov
2020-05-25 15:57             ` Marek Lindner
2020-05-25 17:21               ` Alexey Ermakov
2020-05-25 17:27                 ` Marek Lindner [this message]
2020-05-25 17:33                   ` Alexey Ermakov
2020-05-22 11:41 ` Marek Lindner

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=7073983.9WrHQ1J9Fu@rousseau \
    --to=mareklindner@neomailbox.ch \
    --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