From: Hans Schultz <schultz.hans@gmail.com>
To: davem@davemloft.net, kuba@kernel.org
Cc: netdev@vger.kernel.org,
Hans Schultz <schultz.hans+netdev@gmail.com>,
Stephen Hemminger <stephen@networkplumber.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH iproute2-next V2 0/4] Add support for locked bridge ports (for 802.1X)
Date: Mon, 28 Feb 2022 14:36:46 +0100 [thread overview]
Message-ID: <20220228133650.31358-1-schultz.hans+netdev@gmail.com> (raw)
This patch set is to complement the kernel locked port patches, such
that iproute2 can be used to lock/unlock a port and check if a port
is locked or not. To lock or unlock a port use the command:
bridge link set dev DEV locked {on | off}
To show the detailed setting of a port, including if the locked flag is
enabled for the port(s), use the command:
bridge -d link show [dev DEV]
Hans Schultz (4):
bridge: link: add command to set port in locked mode
ip: iplink_bridge_slave: add locked port flag support
man8/bridge.8: add locked port feature description and cmd syntax
man8/ip-link.8: add locked port feature description and cmd syntax
bridge/link.c | 13 +++++++++++++
include/uapi/linux/if_link.h | 1 +
ip/iplink_bridge_slave.c | 9 +++++++++
man/man8/bridge.8 | 11 +++++++++++
man/man8/ip-link.8.in | 6 ++++++
5 files changed, 40 insertions(+)
--
2.30.2
next reply other threads:[~2022-02-28 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 13:36 Hans Schultz [this message]
2022-02-28 13:36 ` [PATCH iproute2-next V2 1/4] bridge: link: add command to set port in locked mode Hans Schultz
2022-02-28 13:36 ` [PATCH iproute2-next V2 2/4] ip: iplink_bridge_slave: add locked port flag support Hans Schultz
2022-02-28 13:36 ` [PATCH iproute2-next V2 3/4] man8/bridge.8: add locked port feature description and cmd syntax Hans Schultz
2022-02-28 13:36 ` [PATCH iproute2-next V2 4/4] man8/ip-link.8: " Hans Schultz
2022-03-04 16:20 ` [PATCH iproute2-next V2 0/4] Add support for locked bridge ports (for 802.1X) patchwork-bot+netdevbpf
2022-03-11 8:54 ` Hans Schultz
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=20220228133650.31358-1-schultz.hans+netdev@gmail.com \
--to=schultz.hans@gmail.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=schultz.hans+netdev@gmail.com \
--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 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.