From: Stephen Hemminger <stephen@networkplumber.org>
To: Harry Coin <hcoin@quietfountain.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Kuniyuki Iwashima <kuniyu@amazon.com>,
netdev@vger.kernel.org
Subject: Re: llc needs namespace awareness asap, was Re: Patch fixing STP if bridge in non-default namespace.
Date: Thu, 13 Jul 2023 15:37:11 -0700 [thread overview]
Message-ID: <20230713153711.763b840e@hermes.local> (raw)
In-Reply-To: <83efdb0a-559e-edbd-a833-3891f04638ac@quietfountain.com>
On Tue, 11 Jul 2023 22:06:45 -0500
Harry Coin <hcoin@quietfountain.com> wrote:
> Andrew, the only RTSP / STP provider I know of is open-vswitch and their
> docs (last I read them) provide the caution to use veth pairs to
> namespaces, but not run their daemon there--- and fair enough as no
> multicast llc would make it to that code in a namespace as currently
> kernel implemented.
There are at least two other userspace STP providers.
Multiple Spanning Tree Protocol
https://github.com/mstpd/mstpd
And older (mostly for demo) code
https://github.com/shemminger/RSTP
next prev parent reply other threads:[~2023-07-13 22:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 13:35 Patch fixing STP if bridge in non-default namespace Harry Coin
2023-07-11 3:22 ` Kuniyuki Iwashima
2023-07-11 17:08 ` llc needs namespace awareness asap, was " Harry Coin
2023-07-11 18:32 ` Kuniyuki Iwashima
2023-07-11 20:22 ` Harry Coin
2023-07-11 20:44 ` Andrew Lunn
2023-07-11 21:40 ` Harry Coin
2023-07-11 21:51 ` Kuniyuki Iwashima
2023-07-11 22:44 ` Harry Coin
2023-07-11 22:56 ` Kuniyuki Iwashima
[not found] ` <b01e5af6-e397-486d-3428-6fa30a919042@quietfountain.com>
2023-07-12 0:55 ` Andrew Lunn
2023-07-12 3:06 ` Harry Coin
2023-07-13 22:37 ` Stephen Hemminger [this message]
2023-07-12 9:44 ` Petr Machata
2023-07-12 0:49 ` Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2023-08-02 3:45 Hasenbosch, Samuel J
2023-08-02 3:50 ` Kuniyuki Iwashima
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=20230713153711.763b840e@hermes.local \
--to=stephen@networkplumber.org \
--cc=andrew@lunn.ch \
--cc=hcoin@quietfountain.com \
--cc=kuniyu@amazon.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).