From: Tilman Schmidt <tilman@imap.cc>
To: netdev@vger.kernel.org
Subject: Q: State of Linux RSTP support
Date: Wed, 24 Sep 2014 20:00:02 +0200 [thread overview]
Message-ID: <542306A2.7020008@imap.cc> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
According to Stephen Hemminger's presentation at
http://www.slideshare.net/shemminger/new-bridge (which seems to be the
most recent information available on the topic) the in-kernel bridging
code only provides STP. RTSP is (should be) provided by a user space
daemon, rtspd. However, none of the distributions I routinely use
provide that daemon. Sourceforge has a project named rstpd but it
seems to be inactive.
A search for RSTP in the current git tree finds
- - in net/bridge/br_netlink.c, a comment:
/* Binary compatibility with old RSTP */
- - in net/bridge/br_private.h, an enum constant for struct net_bridge
member stp_enabled:
BR_USER_STP, /* new RSTP in userspace */
but nothing in, say, the Documentation folder.
Any pointers?
aTdHvAaNnKcSe,
Tilman
- --
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJUIwaiAAoJEFPuqx0v+F+q/dIIAI8tK2C7yVPoD3PaLwwVqcxQ
9lV3VCXiRT4v1fGTqEtzTJhoyPAqZw+iHbmoPVZow9GPEAS1m5nPYBE44cejmP6M
SL0OtQmcnYO0UNBsIpwA6F8g+e3ZraivtAv4CVoBLMXGWrAz7zrERIRTkk0XOMdG
t2Is1e+U+48DlOH8CIPhqOEu/kIABz2GMle5S94VzlBkeBsGL9ifDrFxACtxbkEN
YJIm9QKxZa/MGwksgHCoQWDafrcs8RL6FhQDBVCUVhrERlp/12+kKwYXxvH9kv+a
YAAzMXkAu+3zPTI0Bl99M4NEQ57Z0FKtb8pwug9wSKH7UWdx18pKYOsYUdMwROM=
=s37Z
-----END PGP SIGNATURE-----
next reply other threads:[~2014-09-24 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 18:00 Tilman Schmidt [this message]
2014-09-24 18:23 ` Q: State of Linux RSTP support Vlad Yasevich
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=542306A2.7020008@imap.cc \
--to=tilman@imap.cc \
--cc=netdev@vger.kernel.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.