Ethernet Bridge development
 help / color / mirror / Atom feed
From: Andrew <amckay@iders.ca>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] STP on Linux 2.6.30.9
Date: Thu, 07 Jan 2010 17:57:16 -0600	[thread overview]
Message-ID: <4B4674DC.3090602@iders.ca> (raw)

Hey guys,

I'm working with a bridge I set up on Linux 2.6.30.9.  I have two boards 
connected and created a redundant connection between them.  Basic set up is:

brctl addbr br0
brctl addif br0 vlan1
brctl addif br0 vlan2
brctl stp br0 on

Then I bring up the interfaces.  Everything seems to be fine.  Root 
bridge is negotiated properly and leaves both interfaces in forwarding 
mode.  The other bridge leaves one port in forwarding and puts the other 
in blocking mode.  However after several seconds a message is printed on 
my terminal saying that vlan2 lost it's neighbor and goes through the 
listening, learning and then forwarding states.  It then quickly flips 
back to blocking mode.  Is this normal behavior for STP on Linux 
2.6.30.9?  Or do I have something else going on here?

net/bridge/br_stp.c:36 br0: port 2(vlan2) entering blocking state
br0: neighbor 8000.3a:1f:34:08:54:56 lost on port 2(vlan2)
net/bridge/br_stp.c:36 br0: port 2(vlan2) entering listening state
net/bridge/br_stp.c:36 br0: port 2(vlan2) entering learning state
br0: topology change detected, sending tcn bpdu
net/bridge/br_stp.c:36 br0: port 2(vlan2) entering forwarding state
br0: topology change detected, sending tcn bpdu
net/bridge/br_stp.c:36 br0: port 2(vlan2) entering blocking state

If there's any further information you need, let me know.

Andrew McKay
Iders Inc.

             reply	other threads:[~2010-01-07 23:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-07 23:57 Andrew [this message]
2010-01-09  6:13 ` [Bridge] STP on Linux 2.6.30.9 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=4B4674DC.3090602@iders.ca \
    --to=amckay@iders.ca \
    --cc=bridge@lists.linux-foundation.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