Ethernet Bridge development
 help / color / mirror / Atom feed
From: Uli Luckas <luckas@musoft.de>
To: bridge@lists.linux-foundation.org
Cc: Stephen Hemminger <shemminger@vyatta.com>,
	rahul bhardwaj <rahul_bhardwaj36in@yahoo.co.in>
Subject: Re: [Bridge] Bridge ports needlessly going through learning stage when	STP is disabled
Date: Sun, 30 Nov 2008 17:27:43 +0100	[thread overview]
Message-ID: <200811301727.44483.luckas@musoft.de> (raw)
In-Reply-To: <49213FC5.4040001@sysnetsistemi.it>

Am Monday, 17. November 2008 schrieb Francesco Dolcini:
> rahul bhardwaj wrote:
> > 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.
>
> At the moment the normal way to handle this is "brctl setfd $BR_DEV 0"
>
Except that setting fd to zero might get you flooded. See thread "delay in 
bridge learning when forward delay is 0" here on the list. [1] 

regards,
Uli


[1] http://archives.free.net.ph/message/20081013.181016.4cbfa529.de.html

-- 
> Ich habe Zone Alarm in Hintergrund mitlaufen, das ist fuer mich
> Pflicht.
Ich habe eine Schüssel Weihwasser neben der Tastatur stehen. Das hilft
genauso.      (Jürgen Schmadlak)

      parent reply	other threads:[~2008-11-30 16:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17  9:13 [Bridge] Bridge ports needlessly going through learning stage when STP is disabled rahul bhardwaj
2008-11-17  9:56 ` 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 [this message]

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=200811301727.44483.luckas@musoft.de \
    --to=luckas@musoft.de \
    --cc=bridge@lists.linux-foundation.org \
    --cc=rahul_bhardwaj36in@yahoo.co.in \
    --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