From: Tobias Waldekranz <tobias@waldekranz.com>
To: Nikolay Aleksandrov <razor@blackwall.org>,
stephen@networkplumber.org, dsahern@kernel.org
Cc: liuhangbin@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2 iproute2 0/3] Multiple Spanning Tree (MST) Support
Date: Wed, 26 Jun 2024 08:33:31 +0200 [thread overview]
Message-ID: <87sex0fc1w.fsf@waldekranz.com> (raw)
In-Reply-To: <14415e23-a478-4385-b556-851395717142@blackwall.org>
On ons, jun 26, 2024 at 09:11, Nikolay Aleksandrov <razor@blackwall.org> wrote:
> On 24/06/2024 16:00, Tobias Waldekranz wrote:
>> This series adds support for:
>>
>> - Enabling MST on a bridge:
>>
>> ip link set dev <BR> type bridge mst_enable 1
>>
>> - (Re)associating VLANs with an MSTI:
>>
>> bridge vlan global set dev <BR> vid <X> msti <Y>
>>
>> - Setting the port state in a given MSTI:
>>
>> bridge mst set dev <PORT> msti <Y> state <Z>
>>
>> - Listing the current port MST states:
>>
>> bridge mst show
>>
>> NOTE: Multiple spanning tree support was added to Linux a couple of
>> years ago[1], but the corresponding iproute2 patches were never
>> posted. Mea culpa. Yesterday this was brought to my attention[2],
>> which is why you are seeing them today.
>>
>> [1]: https://lore.kernel.org/netdev/20220316150857.2442916-1-tobias@waldekranz.com/
>> [2]: https://lore.kernel.org/netdev/Zmsc54cVKF1wpzj7@Laptop-X1/
>>
>> v1 -> v2:
>> - Require exact match for "mst_enabled" bridge option (Liu)
>>
>> Tobias Waldekranz (3):
>> ip: bridge: add support for mst_enabled
>> bridge: vlan: Add support for setting a VLANs MSTI
>> bridge: mst: Add get/set support for MST states
>>
>> bridge/Makefile | 2 +-
>> bridge/br_common.h | 1 +
>> bridge/bridge.c | 3 +-
>> bridge/mst.c | 262 ++++++++++++++++++++++++++++++++++++++++++
>> bridge/vlan.c | 13 +++
>> ip/iplink_bridge.c | 19 +++
>> man/man8/bridge.8 | 66 ++++++++++-
>> man/man8/ip-link.8.in | 14 +++
>> 8 files changed, 377 insertions(+), 3 deletions(-)
>> create mode 100644 bridge/mst.c
>>
>
> Thanks for posting these, I was also wondering what happened with iproute2 support.
> I had to do quick hacks to test my recent mst fixes and I almost missed this set,
> please CC bridge maintainers on such changes as well.
Sorry about that, I'll make sure to remember it in the future.
Thanks for reviewing!
next prev parent reply other threads:[~2024-06-26 6:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 13:00 [PATCH v2 iproute2 0/3] Multiple Spanning Tree (MST) Support Tobias Waldekranz
2024-06-24 13:00 ` [PATCH v2 iproute2 1/3] ip: bridge: add support for mst_enabled Tobias Waldekranz
2024-06-26 2:04 ` Hangbin Liu
2024-06-26 6:12 ` Nikolay Aleksandrov
2024-06-24 13:00 ` [PATCH v2 iproute2 2/3] bridge: vlan: Add support for setting a VLANs MSTI Tobias Waldekranz
2024-06-26 2:08 ` Hangbin Liu
2024-06-26 6:12 ` Nikolay Aleksandrov
2024-06-24 13:00 ` [PATCH v2 iproute2 3/3] bridge: mst: Add get/set support for MST states Tobias Waldekranz
2024-06-26 6:21 ` Nikolay Aleksandrov
2024-06-27 16:56 ` Stephen Hemminger
2024-06-26 6:11 ` [PATCH v2 iproute2 0/3] Multiple Spanning Tree (MST) Support Nikolay Aleksandrov
2024-06-26 6:33 ` Tobias Waldekranz [this message]
2024-06-26 6:47 ` Hangbin Liu
2024-06-26 6:50 ` Nikolay Aleksandrov
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=87sex0fc1w.fsf@waldekranz.com \
--to=tobias@waldekranz.com \
--cc=dsahern@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=razor@blackwall.org \
--cc=stephen@networkplumber.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).