Ethernet Bridge development
 help / color / mirror / Atom feed
From: rahul bhardwaj <rahul_bhardwaj36in@yahoo.co.in>
To: bridge@lists.linux-foundation.org
Cc: Stephen Hemminger <shemminger@vyatta.com>
Subject: [Bridge] Bridge ports needlessly going through learning stage when STP is disabled
Date: Mon, 17 Nov 2008 14:43:49 +0530 (IST)	[thread overview]
Message-ID: <282915.85653.qm@web8807.mail.in.yahoo.com> (raw)

Hi,

I've noticed that in Linux 2.6.15, that even when I have STP disabled on a bridge (which I think is the default), when you add a new interface to the bridge, it still goes through the learning stage and shows STP state display such as TOPOLOGY_CHANGE TOPOLOGY_CHANGE_DETECTED". For this time interval box is unreachable from outside. I have verified this with the help of ping. I found that ping reply stops for some time around 15 to 30 secs, if you add another interface to the bridge. Which is causing some problems for the box.

Is this the right behavior ? The 15 to 30 second delay before the
port moves to Forwarding state can be frustrating, as you don't expect
it, and for that period of time, start to think there is something
else wrong in the network's configuration. Is there any place in the code where I do some change to resolve this issue.


Thanks and regards,

Rahul B




 


      Add more friends to your messenger and enjoy! Go to http://messenger.yahoo.com/invite/

             reply	other threads:[~2008-11-17  9:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17  9:13 rahul bhardwaj [this message]
2008-11-17  9:56 ` [Bridge] Bridge ports needlessly going through learning stage when STP is disabled Francesco Dolcini
2008-11-17 10:45   ` rahul bhardwaj
2009-09-02 18:24     ` [Bridge] Bridge is not forwarding packet on correct vlan port <Help Needed> rahul bhardwaj
2008-11-17 12:30   ` [Bridge] Bridge ports needlessly going through learning stage when STP is disabled rahul bhardwaj
2008-11-30 16:27   ` Uli Luckas

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=282915.85653.qm@web8807.mail.in.yahoo.com \
    --to=rahul_bhardwaj36in@yahoo.co.in \
    --cc=bridge@lists.linux-foundation.org \
    --cc=shemminger@vyatta.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