public inbox for b.a.t.m.a.n@lists.open-mesh.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: Batman_V Originator Loop Issue
Date: Thu, 9 Jul 2020 22:33:44 +0200	[thread overview]
Message-ID: <20200709203344.GB2269@otheros> (raw)
In-Reply-To: <20200708152649.1176.81859@diktynna.open-mesh.org>

Hi Luke,

On Wed, Jul 08, 2020 at 03:26:49PM -0000, lavincent15@gmail.com wrote:
> Simon,
> 
> When I enable DAT on all of my nodes, the network breaks down. With DAT disabled on all the nodes, the network works fine.
> 
> As I develop my project, I would like to take advantage of the mesh wide ARP caching feature DAT. Is there any way I can fix things to where DAT will work on my network?
> 
> Thanks,
> Luke

Would it be possible for you to try an older version of
batman-adv, like v2019.0? There were a few new feature additions
for DAT after that one.

Btw. did you also try disabling aggregation with your batman-adv
2020.1 version? That didn't make a difference, right?

(disabling aggregation for BATMAN_V in v2019.0 won't make a difference
as it wasn't implemented there yet, so if you could try that with
2020.1 would be great)

Regards, Linus

  reply	other threads:[~2020-07-09 20:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 19:47 Batman_V Originator Loop Issue lavincent15
2020-07-08  9:15 ` Simon Wunderlich
2020-07-08 14:44   ` lavincent15
2020-07-08 15:26   ` lavincent15
2020-07-09 20:33     ` Linus Lüssing [this message]
2020-07-24 10:02       ` Linus Lüssing
2020-07-24 15:00         ` lavincent15
2020-07-24 20:23           ` Linus Lüssing
2020-07-27 16:28             ` lavincent15
2020-07-27 18:36               ` Linus Lüssing

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=20200709203344.GB2269@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox