All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] B.A.T.M.A.N. port to ESP32
Date: Sat, 20 Oct 2018 14:20:54 +0200	[thread overview]
Message-ID: <8862805.a4Yc4RlQzm@sven-edge> (raw)
In-Reply-To: <9849012d-6cee-9877-0dbf-65348cb7c593@blastwaveinc.com>

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

On Montag, 8. Oktober 2018 18:43:37 CEST John Gorkos wrote:
[...]
> > This sounds wrong. You should not rebroadcast any OGM. You should
> > only rebroadcast from the best candidate. I'm wondering whether
> > this could cause issues. Or are you testing with a single
> > EspressIF and a single Pi only for now?
> I must have a misunderstanding of the BATMAN IV OGM mechanism.  My
> understanding is that ALL 1-hop (direct) neighbors will rebroadcast the
> heard OGM, and beyond that, only best-hop candidates.

Yes, single hop neighbors have special rules. But it is also important to 
check for the incoming+outgoing interface [1].

[...]
> So, to be clear, I'm working on BATMAN IV and not BATMAN V.  Based on
> the open-mesh docs, BATMAN V networks don't rebroadcast OGMs but instead
> use the Echo Location Packets.  Am I reading that wrong?

Yes, you are wrong. ELP are used in a link-local context (detecting neighbors 
and announcing itself to neighbors). OMG2 are used to inform the complete 
mesh.

> If there's a
> compelling reason to move to BATMAN V, I'd be happy to take a look at
> it.

B.A.T.M.A.N. V is using a different metric. IV is using one which is basically 
packet loss based for direct neighbors and V is using the expected throughput
for direct neighbors. Unfortunately, the ELP documentation [2] in the wiki is
outdated [3].

Kind regards,
	Sven

[1] https://git.open-mesh.org/batman-adv.git/blob/6f6cc4f54909127b236069207fe5691d31c29b24:/net/batman-adv/bat_iv_ogm.c#l1411
[2] https://www.open-mesh.org/projects/batman-adv/wiki/ELP
[3] https://www.open-mesh.org/issues/363

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

      reply	other threads:[~2018-10-20 12:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01 18:01 [B.A.T.M.A.N.] B.A.T.M.A.N. port to ESP32 John Gorkos
2018-10-06  6:07 ` Sven Eckelmann
2018-10-06 12:14 ` Linus Lüssing
2018-10-08 16:43   ` John Gorkos
2018-10-20 12:20     ` 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=8862805.a4Yc4RlQzm@sven-edge \
    --to=sven@narfation.org \
    --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.