Ethernet Bridge development
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: P@draigBrady.com
Cc: bridge@osdl.org
Subject: Re: [Bridge] forwarding delay
Date: Tue, 27 Jan 2004 16:08:43 -0800	[thread overview]
Message-ID: <20040127160843.1569107c.shemminger@osdl.org> (raw)
In-Reply-To: <4016B8E3.6050701@draigBrady.com>

On Tue, 27 Jan 2004 19:15:47 +0000
P@draigBrady.com wrote:

> Hi,
> 
> I'm using linux 2.4.20 here and noticed that even
> when STP is disabled for a bridge, the forwarding delay
> still takes affect. Is this correct? I.E. Does the
> bridge need to spend time in the "listening" and
> "learning" states when STP isn't used?
> 
> It's an easy work around to set the delay to 0,
> I'm just wondering whether it's a buglet or
> by design.

I think it was a design decision to avoid forwarding data until
some state was acquired.  It is annoying if you don't expect it.

      reply	other threads:[~2004-01-28  0:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-27 19:15 [Bridge] forwarding delay P
2004-01-28  0:08 ` Stephen Hemminger [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=20040127160843.1569107c.shemminger@osdl.org \
    --to=shemminger@osdl.org \
    --cc=P@draigBrady.com \
    --cc=bridge@osdl.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