All of lore.kernel.org
 help / color / mirror / Atom feed
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: [B.A.T.M.A.N.] B.A.T.M.A.N. port to ESP32
Date: Sat, 6 Oct 2018 14:14:45 +0200	[thread overview]
Message-ID: <20181006121445.GA1471@otheros> (raw)
In-Reply-To: <babe56e8-b12c-8236-7012-20bb91d400fa@blastwaveinc.com>

Hi John,

On Mon, Oct 01, 2018 at 11:01:25AM -0700, John Gorkos wrote:
> I'm working on a port of the BATMAN-ADV protocol to FreeRTOS,
> specifically running on the ESP32 from EspressIF.

Awesome! I've never seen batman-adv running on such a device. And
it looks like you are already quite close to being the first one
accomplishing this.

> [...]
> Can someone explain to me why this might be occurring, and what I'm
> missing?  Currently, the code is doing two things:  sending a new OGM
> with an incrementing sequence number every 1000 ms,

> and re-broadcasting any received OGMs with a decremented TTL, modified TQ, and DirectLink
> flag set whenever it receives them (also every 1000 ms or so).

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?

If so, then it's probably more likely that just some flags or addresses
got mixed up. Would it be possible for you to share a tcpdump capture
from the Pi? You can also check with "batctl log" whether the Pi
seems to recognize the ESP32 as an originator.

Also, have you tested with two Pis and no EspressIF? Are Pis
themselves forming a mesh just fine for you? Just to outrule that
the issue is on the Pi side.

Regards, Linus

  parent reply	other threads:[~2018-10-06 12:14 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 [this message]
2018-10-08 16:43   ` John Gorkos
2018-10-20 12:20     ` Sven Eckelmann

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=20181006121445.GA1471@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.