public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Cc: Alexey Ermakov <axel101@gmail.com>
Subject: Re: Batman-adv packet retranslation
Date: Sun, 24 May 2020 18:28:22 +0200	[thread overview]
Message-ID: <2164745.TYCVdmGlQZ@sven-edge> (raw)
In-Reply-To: <CAOVt3fE8-U73oJV2XjnxFzWc35LAMeXeaNsTUUgPaLqvchv-Cw@mail.gmail.com>

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

On Sunday, 24 May 2020 16:43:55 CEST Alexey Ermakov wrote:
> Sorry, I didn't provided full information about experiment conditions.
[...]
> 6) batctl hardif eth0 to 100                NOTE: If sklip this step,
> all works fine!
> 
> After this I started host bridge interface br0. NOTE: if bridge had
> started before batman configured all works fine

As Marek pointed  out, you told batman-adv that the  eth0 interfaces have for 
some reason a link speed of 0.1 [Mbit/s] (or 1 [100Kbit/s] - what the actual 
unit is for B.A.T.M.A.N. V). And unfortunately, 88% (for the hop penalty) of 1 
[100 Kbit/s] is in integer arithmetic 0 [100 Kbit/s]. And 0 whatever/s is just 
discarded by B.A.T.M.A.N. V [1] and not considered for routing traffic - hey, 
this path ends up as being 0 and therefore useless.

The reason why you want to set the link to 1 [100 Kbit/s] has to be figured 
out by yourself. But for a (during forwarding) strictly monotonic decreasing, 
integer value, it is a bad starting point to set it to 1 [whatever-unit] for a 
multi-hop setup.

Kind regards,
	Sven

[1] https://git.open-mesh.org/batman-adv.git/blob/e946e0beec5764ed5182943bf764f8793f1364bf:/net/batman-adv/bat_v_ogm.c#l880

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

  parent reply	other threads:[~2020-05-24 16:28 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 [this message]
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
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=2164745.TYCVdmGlQZ@sven-edge \
    --to=sven@narfation.org \
    --cc=axel101@gmail.com \
    --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