From: Jaime Nebrera <jnebrera@eneotecnologia.com>
To: joakim.tjernlund@transmode.se
Cc: Bridge@lists.linux-foundation.org
Subject: Re: [Bridge] STP bug, loop not detetcted
Date: Wed, 07 May 2008 11:33:02 +0200 [thread overview]
Message-ID: <1210152782.4861.6.camel@blas> (raw)
In-Reply-To: <1210152122.32216.95.camel@gentoo-jocke.transmode.se>
Hi Joakim,
I'm not aware if Linux bridge is aware of this. I can tell you that in
general, STP has problems when mixed with VLANs.
To solve this some extensions have arised: PVST by Cisco, MSTP, an
improvement more or less estandarized and PVST+, a new update only
available in Cisco environments.
In general they run multiple "STP" instances per VLAN or VLAN group.
Regards
El mié, 07-05-2008 a las 11:22 +0200, Joakim Tjernlund escribió:
> Got a bridge with 4 optical VLAN interfaces, eth1.1, eth1.2, eth1.3 and
> eth1.4, attached and the builtin STP enabled. eth1 is connected to
> a "switch" with 4 real interfaces, each real interface maps to one of
> the above mentioned VLANs.
>
> If I loop two or more interfaces by connecting each interface's output
> to its own input, I get a loop that STP doesn't detect.
> Looping by connecting an output from one interface to another interface
> input works fine.
>
> Bug or limitation in STP? If limitation, would RSTP help here?
>
> Kernel 2.6.25
>
> Jocke
> _______________________________________________
> Bridge mailing list
> Bridge@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/bridge
--
Jaime Nebrera - jnebrera@eneotecnologia.com
Consultor TI - ENEO Tecnologia SL
Pol. PISA - C/ Manufactura 6, P1, 3B
Mairena del Aljarafe - 41927 - Sevilla
Telf.- 955 60 11 60 / 619 04 55 18
next prev parent reply other threads:[~2008-05-07 9:33 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 [this message]
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
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=1210152782.4861.6.camel@blas \
--to=jnebrera@eneotecnologia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.