Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta.com>
To: joakim.tjernlund@transmode.se
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] STP bug, loop not detetcted
Date: Mon, 12 May 2008 10:50:11 -0700	[thread overview]
Message-ID: <20080512105011.7070c249@extreme> (raw)
In-Reply-To: <1210585065.32216.218.camel@gentoo-jocke.transmode.se>

On Mon, 12 May 2008 11:37:45 +0200
Joakim Tjernlund <joakim.tjernlund@transmode.se> wrote:

> 
> On Thu, 2008-05-08 at 14:58 +0200, Joakim Tjernlund wrote:
> > On Thu, 2008-05-08 at 14:13 +0200, Francesco Dolcini wrote:
> > > Joakim Tjernlund wrote:
> > > > On Thu, 2008-05-08 at 11:04 +0200, Francesco Dolcini wrote:
> > > >> cisco and others solved this kind of problem using proprietary 
> > > >> unidirectional link detection protocols (see cisco informational rfc 
> > > >> 5171 for example). No standard exists as far as I know (BFD rfc does not 
> > > >> consider the layer 2 case).
> > > > 
> > > > Are these proprietary unidirectional link detection protocols the only
> > > > way to solve the problem?
> > > spanning tree protocol, in the various IEEE incarnation (802.1D, 802.1Q) 
> > > and cisco (PVSTP) does not handle this problem, so an external mechanism 
> > > is needed.
> > 
> > Do they explicitly ban it? Otherwise I don't see why not the kernel STP
> > can be enchanted. You could even view it as an external mechanism.
> > 
> > > 
> > > > Would STP break if the interface was set to "non forwarding" in this
> > > > case until the bridge stops seeing its own STP messages?
> > > At least this will not solve the more general problem of a 
> > > unidirectional link (rx working and tx broken).
> > 
> > hmm, if TX is broken there won't be a loop anyway?
> > 
> > Anyhow, even if my proposed change doesn't solve all cases it seems like
> > a useful, very simple, ad don to STP. I am just concerned that it can
> > break some other aspect of STP. So far it seems OK.
> > 
> > What is the bridge maintainers view on this?
> 
> Stephen, whats is your view about extending the bridge code according to
> above? Also, after looking at the bride code I don't see where this
> should be added, I must be getting old :(
> 
>         Jocke

If you want to make STP vlan aware, then fine, a good place to start
is getting a version of new RSTP and making it vlan aware.

  reply	other threads:[~2008-05-12 17:50 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07  9:22 [Bridge] STP bug, loop not detetcted Joakim Tjernlund
2008-05-07  9:33 ` Jaime Nebrera
2008-05-07 10:40   ` Benny Amorsen
2008-05-07 10:42 ` Benny Amorsen
2008-05-08  2:16 ` richardvoigt
2008-05-08  8:01   ` Joakim Tjernlund
2008-05-08  9:04     ` Francesco Dolcini
2008-05-08 10:01       ` Joakim Tjernlund
2008-05-08 12:13         ` Francesco Dolcini
2008-05-08 12:58           ` Joakim Tjernlund
2008-05-12  9:37             ` Joakim Tjernlund
2008-05-12 17:50               ` Stephen Hemminger [this message]
2008-05-12 17:54                 ` Joakim Tjernlund
2008-05-13  3:10     ` richardvoigt
2008-05-13  7:35       ` Joakim Tjernlund
2008-05-13  8:41       ` Benny Amorsen
2008-05-13 22:29         ` Dylan Hall
2008-05-13 23:09           ` richardvoigt
2008-05-13 23:56             ` Dylan Hall
2008-05-14  0:55               ` Brad Dameron
2008-05-14  7:27           ` Francesco Dolcini
2008-05-13 17:28       ` Stephen Hemminger
2008-05-13 19:24         ` [Bridge] RSTP implementation choice Benoit PAPILLAULT
2008-05-14  7:51         ` [Bridge] STP bug, loop not detetcted Francesco Dolcini

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=20080512105011.7070c249@extreme \
    --to=shemminger@vyatta.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=joakim.tjernlund@transmode.se \
    /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