From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Rodolfo Giometti <giometti@enneenne.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] rstpd & 2.4
Date: Tue, 27 Jul 2010 08:38:15 -0700 [thread overview]
Message-ID: <20100727083815.32972338@nehalam> (raw)
In-Reply-To: <20100727092655.GA30692@gundam.enneenne.com>
On Tue, 27 Jul 2010 11:26:55 +0200
Rodolfo Giometti <giometti@enneenne.com> wrote:
> On Fri, Jul 02, 2010 at 09:21:48AM -0700, Stephen Hemminger wrote:
>
> > The 2.4 kernel is missing all the hooks to provide user level STP.
> > The startup is not the big issue, the real problem is that the
> > kernel doesn't have hooks to control port state from user space,
> > and the spanning tree packets may not be visible to user space
> > application either.
> >
> > Sigh, 2.4 is at least 5 years old by now.
>
> Hello, I'm going to start backport of rstpd to kernel 2.4 series and
> I'd like having some advices from you.
>
> Regarding the bridge controls I can add to the current sysfs interface
> the old ioctl interface as the old bridge-utils did. Do you think I
> can contribute to the rstpd code in order to support such interface or
> you have no interest in doing it?
I won't put in 2.6 code. If you wan to put in 2.4, contact
the 2.4 kernel maintainer.
> The problem of controlling the port state from user space can be
> resolved by adding the missing netlink commands into the kernel code.
>
> In the end, spanning tree packets may be captured as tcpdump do, is
> that right?
That is how I did it since RSTP needs to see ethernet headers.
next prev parent reply other threads:[~2010-07-27 15:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 13:56 [Bridge] rstpd & 2.4 Rodolfo Giometti
2010-07-02 16:21 ` Stephen Hemminger
2010-07-02 19:22 ` Rodolfo Giometti
2010-07-27 9:26 ` Rodolfo Giometti
2010-07-27 15:38 ` Stephen Hemminger [this message]
2010-07-27 17:20 ` Rodolfo Giometti
2010-07-29 15:39 ` Rodolfo Giometti
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=20100727083815.32972338@nehalam \
--to=shemminger@linux-foundation.org \
--cc=bridge@lists.linux-foundation.org \
--cc=giometti@enneenne.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