From: Cameron Schaus <cam@schaus.ca>
To: Jake Farrell <jake@amperion.com>, bridge@lists.osdl.org
Subject: Re: [Bridge] STP Loop not blocking
Date: Wed, 24 Jan 2007 13:22:37 -0500 [thread overview]
Message-ID: <45B7A3ED.4080607@schaus.ca> (raw)
In-Reply-To: <8764B2C538F2C44B845C4B608D4515D31A48C2@EXVBE012-5.exch012.intermedia.net>
Jake Farrell wrote:
>
> Recently ran into a problem with the 2.6.18 kernel on Xscale arch when
> a bridge, with multiple interfaces on it, is configured with a
> redundant loop. All interfaces are left on forwarding and nexer switch
> to block when the loop is introduced. This was tested against a 2.6.16
> kernel and the problem did not occur, interfaces forwared and blocked
> correctly. Any help would be appreciated.
>
Since you haven't give much detail on your setup (is stp enabled on both
bridges, for example), I'm not 100% clear what may be happening. But it
does sound like something I ran into before.
See my post, and Stephen's reply:
http://lists.osdl.org/pipermail/bridge/2006-December/001573.html
Cam
next prev parent reply other threads:[~2007-01-24 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-24 17:59 [Bridge] STP Loop not blocking Jake Farrell
2007-01-24 18:22 ` Cameron Schaus [this message]
2007-01-24 18:46 ` Jake Farrell
2007-01-24 19:19 ` Stephen Hemminger
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=45B7A3ED.4080607@schaus.ca \
--to=cam@schaus.ca \
--cc=bridge@lists.osdl.org \
--cc=jake@amperion.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 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.