From: David Ahern <dsahern@gmail.com>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>,
netdev@vger.kernel.org
Cc: roopa@cumulusnetworks.com, dsahern@kernel.org,
idosch@mellanox.com, stephen@networkplumber.org
Subject: Re: [PATCH iproute2 net-next] bridge: add support for isolated option
Date: Fri, 6 Jul 2018 08:59:59 -0600 [thread overview]
Message-ID: <eff656fa-1596-92e1-d885-9f92a728042c@gmail.com> (raw)
In-Reply-To: <20180703124244.6864-2-nikolay@cumulusnetworks.com>
On 7/3/18 6:42 AM, Nikolay Aleksandrov wrote:
> This patch adds support for the new isolated port option which, if set,
> would allow the isolated ports to communicate only with non-isolated
> ports and the bridge device. The option can be set via the bridge or ip
> link type bridge_slave commands, e.g.:
> $ ip link set dev eth0 type bridge_slave isolated on
> $ bridge link set dev eth0 isolated on
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
> ---
> bridge/link.c | 11 +++++++++++
> ip/iplink_bridge_slave.c | 9 +++++++++
> man/man8/bridge.8 | 6 ++++++
> man/man8/ip-link.8.in | 6 ++++--
> 4 files changed, 30 insertions(+), 2 deletions(-)
>
applied to iproute2-next. Thanks
next prev parent reply other threads:[~2018-07-06 14:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 12:42 [PATCH net-next 0/2] bridge: iproute2 isolated port and selftests Nikolay Aleksandrov
2018-07-03 12:42 ` [PATCH iproute2 net-next] bridge: add support for isolated option Nikolay Aleksandrov
2018-07-06 14:59 ` David Ahern [this message]
2018-07-03 12:42 ` [PATCH net-next 1/2] selftests: forwarding: lib: extract ping and ping6 so they can be reused Nikolay Aleksandrov
2018-07-03 12:42 ` [PATCH net-next 2/2] selftests: forwarding: test for bridge port isolation Nikolay Aleksandrov
2018-07-04 12:40 ` [PATCH net-next 0/2] bridge: iproute2 isolated port and selftests David Miller
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=eff656fa-1596-92e1-d885-9f92a728042c@gmail.com \
--to=dsahern@gmail.com \
--cc=dsahern@kernel.org \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.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 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).