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.] MAC addresses of loop detect frames in global translation-table
Date: Wed, 31 May 2017 15:39:23 +0200 [thread overview]
Message-ID: <13855542.45yYzsjnKj@prime> (raw)
In-Reply-To: <OF367AF97D.9569B75C-ONC1258131.00480417-C1258131.00491EA2@phoenixcontact.com>
[-- Attachment #1: Type: text/plain, Size: 2668 bytes --]
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.
Thanks,
Simon
On Wednesday, May 31, 2017 3:18:39 PM CEST Andreas Pape wrote:
> Hello,
>
> I stumbled across some weired MAC addresses starting with ba:be in the
> global translation-table when running batman-adv-2017.0.1. I run my setup
> with bla enabled.
>
> Most of the entries in the global tt of my devices consist of these mac
> addresses. Looking through the code they come from frames which seem to be
> used for loop detection. Adding such MAC addresses to the local tt is
> prevented with the help of the batadv_bla_is_loopdetect_mac function. I
> wonder why adding these macs to the global tt is not prevented in a
> simliar way. Would it be possible to add a corresponding check to
> batadv_tt_global_add to prevent these macs from being added to the global
> tt? Or is there a specific reason why these mac addresses must occur in
> the global tt and which I have not understood so far?
>
> Best regards,
> Andreas
>
>
>
> ..................................................................
> PHOENIX CONTACT ELECTRONICS GmbH
>
> Sitz der Gesellschaft / registered office of the company: 31812 Bad Pyrmont
> USt-Id-Nr.: DE811742156
> Amtsgericht Hannover HRB 100528 / district court Hannover HRB 100528
> Geschäftsführer / Executive Board: Ulrich Leidecker, Christoph Leifer
> __________________________________________________________________
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte
> Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail
> irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und
> vernichten Sie diese Mail. Das unerlaubte Kopieren, jegliche anderweitige
> Verwendung sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.
> ---------------------------------------------------------------------------
> ------------------------- This e-mail may contain confidential and/or
> privileged information. If you are not the intended recipient (or have
> received this e-mail in error) please notify the sender immediately and
> destroy this e-mail. Any unauthorized copying, disclosure, distribution or
> other use of the material or parts thereof is strictly forbidden.
> ___________________________________________________________________
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-05-31 13:39 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 [this message]
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
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=13855542.45yYzsjnKj@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