From: Stephen Hemminger <shemminger@osdl.org>
To: Miller Seth-G19426 <seth.miller@motorola.com>
Cc: Bui Khanh-E12360C <E12360C@motorola.com>, bridge@osdl.org
Subject: [Bridge] Re: Rapid Spanning Tree support
Date: Wed, 5 Apr 2006 09:09:23 -0700 [thread overview]
Message-ID: <20060405090923.7e5f468e@localhost.localdomain> (raw)
In-Reply-To: <F021020DA23B6641A05E616D5EAD146373A3F9@de01exm60.ds.mot.com>
Added bridge mailing list to RSTP discussion.
On Wed, 5 Apr 2006 11:29:42 -0400
"Miller Seth-G19426" <seth.miller@motorola.com> wrote:
>
> That's an approach we were considering as well using
> http://sourceforge.net/projects/rstplib/. Was this what you were
> planning to start with or did you want to pull the code out of the
> kernel? We're willing to work with you getting the user space app
> working and any of the infrastructure changes as well. The plan would be
> to put all this work back into the community. We're also interested in
> adding 802.1s Multiple spanning tree.
>
>
> -----Original Message-----
> Actually, I would like to make RSTP (and all the spanning tree
> protocols)
> a user space utility. There are some infrastructure changes necessary
> to propagate sufficient information to do it.
I was going to leave existing STP in kernel for now, but not enable it.
For 2.6.17, I made sure that STP packets are received so application
can receive them (via LLC).
The next part would be adding a netlink interface to bridge module
to report and modify:
* interface added/deleted from bridge
* interface status change (carrier up/down)
* interface forwarding enable/disable
* forwarding table flush by interface.
next parent reply other threads:[~2006-04-05 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <F021020DA23B6641A05E616D5EAD146373A3F9@de01exm60.ds.mot.com>
2006-04-05 16:09 ` Stephen Hemminger [this message]
2006-04-06 19:12 [Bridge] RE: Rapid Spanning Tree support Miller Seth-G19426
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=20060405090923.7e5f468e@localhost.localdomain \
--to=shemminger@osdl.org \
--cc=E12360C@motorola.com \
--cc=bridge@osdl.org \
--cc=seth.miller@motorola.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 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.