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.] MAC addresses of loop detect frames in global translation-table
Date: Wed, 31 May 2017 16:20:13 +0200 [thread overview]
Message-ID: <20170531142013.GD29826@otheros> (raw)
In-Reply-To: <13855542.45yYzsjnKj@prime>
On Wed, May 31, 2017 at 03:39:23PM +0200, Simon Wunderlich wrote:
> Hi Andreas,
>
> yes, those are loop detection packets. Preventing these entries from the local
> translation table has been implemented only recently. We can potentially do
> the same for global addresses as well, it just hasn't been done so far ... at
> least I don't see a reason prevening us from that. It is probably added by
> "speedy join" in the first place.
This was the case at least for me. Andreas, do yours have the
temporary flag set, too?
I'm wondering why these packets end up in the mesh in the first
place. (Preventing things as late as in tt_gobal_add() / on
mesh receiving nodes seems like a workaround?)
Regards, Linus
next prev parent reply other threads:[~2017-05-31 14:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 13:18 [B.A.T.M.A.N.] MAC addresses of loop detect frames in global translation-table Andreas Pape
2017-05-31 13:39 ` Simon Wunderlich
2017-05-31 14:20 ` Linus Lüssing [this message]
2017-05-31 14:40 ` Simon Wunderlich
2017-05-31 15:56 ` Linus Lüssing
2017-06-01 8:07 ` Simon Wunderlich
2017-06-01 6:12 ` [B.A.T.M.A.N.] Antwort: " Andreas Pape
2017-06-01 8:16 ` Simon Wunderlich
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=20170531142013.GD29826@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