[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <eff656fa-1596-92e1-d885-9f92a728042c@gmail.com>
Date: Fri, 6 Jul 2018 08:59:59 -0600
From: David Ahern <dsahern@...il.com>
To: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>,
netdev@...r.kernel.org
Cc: roopa@...ulusnetworks.com, dsahern@...nel.org, idosch@...lanox.com,
stephen@...workplumber.org
Subject: Re: [PATCH iproute2 net-next] bridge: add support for isolated option
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@...ulusnetworks.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
Powered by blists - more mailing lists