From: Stephen Hemminger <shemminger@osdl.org>
To: Hai Wang <u2.ireland@gmail.com>
Cc: Ben Greear <greearb@candelatech.com>, bridge@lists.osdl.org
Subject: Re: [Bridge] Bridge question
Date: Fri, 4 Nov 2005 09:26:54 -0800 [thread overview]
Message-ID: <20051104092654.417b4ce6@dxpl.pdx.osdl.net> (raw)
In-Reply-To: <30be90270511040519o45d1dd0dr73834b6424dbe62@mail.gmail.com>
On Fri, 4 Nov 2005 08:19:35 -0500
Hai Wang <u2.ireland@gmail.com> wrote:
> Stephen,
> Since your trick is using 2 (even 4) priority bits, do you think it could
> cause some cmpatibility issue with other STP implementation which still uses
> these bits? (it seems to me that port priority is local significant. maybe
> we can use all 8 bits for port ID, can't we?)
> If we take other approaches, like create more than one bridges on one
> Linux box, I am not sure if it is feasible, since I saw all bridges created
> on the box have the same bridge ID.
> Thanks!
The port id is treated as a 16 bit ordered field by STP. So the other
side won't have any problem. Nested bridge's won't work for a bunch of
implementation related reasons, it's not impossible to change to allow
that just a lot of work getting rid of all the possible race issues.
The bridge id comes from the Mac of the first interface in bridge.
So if you have mulitple bridges they all would have different bridge ids.
--
Stephen Hemminger <shemminger@osdl.org>
OSDL http://developer.osdl.org/~shemminger
next prev parent reply other threads:[~2005-11-04 17:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <DE026503646E7F40AF97BAB98334333BF0C972@uss-republic.finepoint.com>
2005-11-03 23:17 ` [Bridge] Bridge question Hai Wang
2005-11-03 23:33 ` Stephen Hemminger
2005-11-03 23:58 ` Ben Greear
2005-11-04 13:19 ` Hai Wang
2005-11-04 17:26 ` Stephen Hemminger [this message]
2005-11-04 17:55 ` Hai Wang
[not found] ` <30be90270511041016i25b04841o18e3fdf6a855d0f7@mail.gmail.com>
[not found] ` <30be90270511041046n7b4ef6dalb3a235da6fba37a@mail.gmail.com>
[not found] ` <20051104105720.02a93a7e@dxpl.pdx.osdl.net>
[not found] ` <30be90270511041108l3c9414afp8526a70130e0f1dd@mail.gmail.com>
[not found] ` <20051104113910.322bb270@dxpl.pdx.osdl.net>
[not found] ` <30be90270511041214w2be63458s854bd8e51f850d05@mail.gmail.com>
[not found] ` <20051104123442.0d12d7ed@dxpl.pdx.osdl.net>
[not found] ` <30be90270511041319o2f97b74co83e64b2ca2937968@mail.gmail.com>
2005-11-08 13:50 ` Hai Wang
2005-11-08 17:28 ` Stephen Hemminger
[not found] <DE026503646E7F40AF97BAB98334333BF0C973@uss-republic.finepoint.com>
2005-11-03 23:48 ` Hai Wang
2005-11-03 22:16 Hai Wang
2005-11-03 23:05 ` Stephen Hemminger
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=20051104092654.417b4ce6@dxpl.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=bridge@lists.osdl.org \
--cc=greearb@candelatech.com \
--cc=u2.ireland@gmail.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