* [Bridge] Bridge port states
@ 2005-01-19 17:49 Patrick Stuedi
2005-01-19 18:31 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: Patrick Stuedi @ 2005-01-19 17:49 UTC (permalink / raw)
To: bridge
Hi all,
Can anyone explain me why we need all this per port state information. A
bridge port seems to be either in BR_STATE_LISTENING, BR_STATE_LEARNING
or BR_STATE_FORWARDING. I don't get it, thought the bridge is learning
from MAC addresses of the received packets, therefore while listening.
Why a bridge port distinquishes these states?
Thanx,
Patrick
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [Bridge] Bridge port states
2005-01-19 17:49 [Bridge] Bridge port states Patrick Stuedi
@ 2005-01-19 18:31 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2005-01-19 18:31 UTC (permalink / raw)
To: stuedip; +Cc: bridge
On Wed, 19 Jan 2005 18:49:02 +0100
Patrick Stuedi <stuedip@student.ethz.ch> wrote:
> Hi all,
>
> Can anyone explain me why we need all this per port state information. A
> bridge port seems to be either in BR_STATE_LISTENING, BR_STATE_LEARNING
> or BR_STATE_FORWARDING. I don't get it, thought the bridge is learning
> from MAC addresses of the received packets, therefore while listening.
> Why a bridge port distinquishes these states?
>
> Thanx,
> Patrick
>
For full detail get the IEEE spec for bridging 802.1G
http://standards.ieee.org/getieee802/802.1.html
Port states are described in lots of detail in 7.4
--
Stephen Hemminger <shemminger@osdl.org>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2005-01-19 18:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-01-19 17:49 [Bridge] Bridge port states Patrick Stuedi
2005-01-19 18:31 ` Stephen Hemminger
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.