All of lore.kernel.org
 help / color / mirror / Atom feed
From: lavincent15@gmail.com
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: Batman_V Originator Loop Issue
Date: Wed, 08 Jul 2020 14:44:07 -0000	[thread overview]
Message-ID: <20200708144407.1176.97484@diktynna.open-mesh.org> (raw)
In-Reply-To: <5716273.fDpRzsxG9E@prime>

"can you please describe which nodes are connected to the LAN and which are
not? You say "one is connected to LAN" and the others are "operating as an"

00:30:1a:4e:b8:26 is the only node that is connected via eth0 to my LAN. All three nodes are running mesh point and AP on mesh0 and wlan0 respectively.

"If multiple nodes are connected and bridged to the same LAN, bridge loop
avoidance should be enabled - you have that in your config, but you could
double check with "batctl bl" and then "batctl bbt"/"batctl
cl" (please post
these tables if you think this could be connected).
You could also try disabling distributed arp table and multicast mode, just to
make sure this is not shooting us in the foot here. Those optimizations are
not really needed for such a small network."

I see. Since I only have one node connected to LAN via eth0, I do not need bla. I just tried disabling multicast, bla, and arp table. So far so good! It's working. Thank you so much for the help!

  reply	other threads:[~2020-07-08 14:44 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 [this message]
2020-07-08 15:26   ` lavincent15
2020-07-09 20:33     ` Linus Lüssing
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=20200708144407.1176.97484@diktynna.open-mesh.org \
    --to=lavincent15@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 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.