From: Sven Eckelmann <sven@narfation.org>
To: b.a.t.m.a.n@lists.open-mesh.org,
Simon Wunderlich <simon.wunderlich@open-mesh.com>
Subject: Re: [B.A.T.M.A.N.] [PATCH] batman-adv: add detection for complex bridge loops
Date: Thu, 10 Mar 2016 19:44:40 +0100 [thread overview]
Message-ID: <2657763.4IxibMMjmR@bentobox> (raw)
In-Reply-To: <1408455756-10794-1-git-send-email-sw@simonwunderlich.de>
[-- Attachment #1: Type: text/plain, Size: 1292 bytes --]
On Tuesday 19 August 2014 15:42:36 Simon Wunderlich wrote:
> From: Simon Wunderlich <simon@open-mesh.com>
>
> There are network setups where the current bridge loop avoidance can't
> detect bridge loops. The minimal setup affected would consist of two
> LANs and two separate meshes, connected in a ring like that:
>
> A...(mesh1)...B
> | |
> (LAN1) (LAN2)
> | |
> C...(mesh2)...D
>
> Since both the meshes and backbones are separate, the bridge loop
> avoidance has not enough information to detect and avoid the loop
> in this case. Even if these scenarios can't be fixed easily,
> these kind of loops can be detected.
>
> This patch implements a periodic check (running every 60 seconds for
> now) which sends a broadcast frame with a random MAC address on
> each backbone VLAN. If a broadcast frame with the same MAC address
> is received shortly after on the mesh, we know that there must be a
> loop and report that incident as well as throw an uevent to let others
> handle that problem.
>
> Signed-off-by: Simon Wunderlich <simon@open-mesh.com>
> ---
It looks like this patch doesn't apply anymore. Can you please resent it or
mark it correctly in patchwork [1].
Thanks,
Sven
[1] https://patchwork.open-mesh.org/patch/4154/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-03-10 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 13:42 [B.A.T.M.A.N.] [PATCH] batman-adv: add detection for complex bridge loops Simon Wunderlich
2016-03-10 18:44 ` Sven Eckelmann [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=2657763.4IxibMMjmR@bentobox \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=simon.wunderlich@open-mesh.com \
/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