All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: Juergen Pfeiffer <j.pfeiffer@seskion.de>
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Is bridgeing possible with kernel 2.6.10
Date: Wed, 26 Jul 2006 10:13:35 -0700	[thread overview]
Message-ID: <20060726101335.67406ee8@localhost> (raw)
In-Reply-To: <44C7979B.7040906@seskion.de>

On Wed, 26 Jul 2006 18:26:03 +0200
Juergen Pfeiffer <j.pfeiffer@seskion.de> wrote:

> Stephen Hemminger schrieb:
> >
> > Did the bridge get set up right? Did the interfaces come up (look
> > at 'brctl showstp br0') 
> $ ifconfig eth0 0.0.0.0 down
> $ ifconfig eth1 0.0.0.0 down
> $ brctl addbr br0
> $ brctl stp br0 on
> $ brctl addif br0 eth0
> $ brctl addif br0 eth1
> $ ifconfig eth0 0.0.0.0 up
> $ ifconfig eth1 0.0.0.0 up
> $ ifconfig br0 0.0.0.0 up
> 
> $ brctl showmacs br0
> port no mac addr                is local?       ageing timer
>   1     00:11:22:33:44:50       yes                0.00
>   2     00:11:22:33:44:51       yes                0.00
>   2     00:11:95:34:af:01       no                 2.91
>   2     00:c0:02:39:53:52       no                 2.76
> $ brctl showstp br0
> br0
>  bridge id              8000.001122334450
>  designated root        8000.001122334450
>  root port                 0                    path
> cost                  0 max age
> 20.00                 bridge max age            20.00
>  hello time                2.00                 bridge hello 
> time          2.00
>  forward delay            15.00                 bridge forward 
> delay      15.00
>  ageing time             300.00
>  hello timer               1.45                 tcn 
> timer                  0.00
>  topology change timer     0.00                 gc
> timer 273.04
>  flags
> 
> 
> eth0 (1)
>  port id                8001
> state learning
>  designated root        8000.001122334450       path
> cost                100 designated bridge
> 8000.001122334450       message age timer          0.00
>  designated port        8001                    forward delay 
> timer        3.48
>  designated cost           0                    hold 
> timer                 0.44
>  flags
> 
> eth1 (2)
>  port id                8002
> state learning
>  designated root        8000.001122334450       path
> cost                100 designated bridge
> 8000.001122334450       message age timer          0.00
>  designated port        8002                    forward delay 
> timer        3.45
>  designated cost           0                    hold 
> timer                 0.43
>  flags
> 

The bridge starts in the learning state doesn't forward until the
forwarding delay (30 seconds) in expired. You need to be either patient
or set the delay to a lower value.

  reply	other threads:[~2006-07-26 17:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-26 14:44 [Bridge] Is bridgeing possible with kernel 2.6.10 Juergen Pfeiffer
2006-07-26 15:34 ` Stephen Hemminger
2006-07-26 16:26   ` Juergen Pfeiffer
2006-07-26 17:13     ` Stephen Hemminger [this message]
2006-07-27  9:15       ` Juergen Pfeiffer
2006-07-27 17:39         ` Stephen Hemminger
2006-07-28 19:17   ` Bart De Schuymer
2006-08-02 23:05 ` [Bridge] [uClinux-dev] " David McCullough
2006-08-14 15:52 ` [Bridge] " Juergen Pfeiffer
     [not found] <1167297092.6795.17.camel@getafix.msbmicro.com>
2006-12-28  9:52 ` Juergen Pfeiffer

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=20060726101335.67406ee8@localhost \
    --to=shemminger@osdl.org \
    --cc=bridge@lists.osdl.org \
    --cc=j.pfeiffer@seskion.de \
    /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.