All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris McHarg <chris@atmark-techno.com>
To: bridge@lists.osdl.org
Subject: [Bridge] port priority bits
Date: Fri, 21 Jul 2006 20:15:23 +0900	[thread overview]
Message-ID: <44C0B74B.7050204@atmark-techno.com> (raw)

Hello.

I'm fairly (very) new to the kernel and networking in general, but I 
thought I'd give the following a shot here...

I was reading thought the STP chapter in Understanding Linux Network 
Internals and testing out the bridging configuration with brctl, and was 
surprised to find that setportprio would only have any effect for values 
0 to 63 (on 2.6.12.3 and using bridge-utils 0.9.6). It seems the port 
priority has been handled as 6 bits since this:

http://lists.osdl.org/mailman/htdig/bridge/2004-April/000274.html

On page 322 of the book, it describes it as originally 8 bits, then 
changed to 4bits with 802.1t (in 2001).

I'm not sure if there has there been any movement/talk on working on 
conformance with 802.1t, but I wonder if it would be good to go with one 
of the two standards. In 802.1t, it seems that the bridge priority was 
changed from 16 bits to 4 bits, with changes for port cost as well.

Chris


                 reply	other threads:[~2006-07-21 11:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=44C0B74B.7050204@atmark-techno.com \
    --to=chris@atmark-techno.com \
    --cc=bridge@lists.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 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.