public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Antwort: Re: MAC addresses of loop detect frames in global translation-table
Date: Thu, 01 Jun 2017 10:16:22 +0200	[thread overview]
Message-ID: <1557491.4zHez3V5Fn@prime> (raw)
In-Reply-To: <OF89FEE322.19461B05-ONC1258132.0021BED4-C1258132.002222CC@phoenixcontact.com>

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

On Thursday, June 1, 2017 8:12:51 AM CEST Andreas Pape wrote:
> > Von: Linus Lüssing <linus.luessing@c0d3.blue>
> > An: The list for a Better Approach To Mobile Ad-hoc Networking
> > <b.a.t.m.a.n@lists.open-mesh.org>
> > Datum: 31.05.2017 16:20
> > Betreff: Re: [B.A.T.M.A.N.] MAC addresses of loop detect frames in
> > global translation-table
> > Gesendet von: "B.A.T.M.A.N" <b.a.t.m.a.n-bounces@lists.open-mesh.org>
> > 
> > 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?
> 
> If I remember it correctly they are shown as "regular" MAC addresses
> without any
> special flags set (like any real mac address of existing devices). In the
> meantime
> I kick these entries in batadv_tt_global_add. But if you are interested I
> could
> revert my firmware and give a more precise answer.
> 

To me, it would be sufficient to get a patch from your or Linus or anyone else 
to fix this. :)

Thanks!
     Simon

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

      reply	other threads:[~2017-06-01  8:16 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
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 [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=1557491.4zHez3V5Fn@prime \
    --to=sw@simonwunderlich.de \
    --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