[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181012084028.5a64747f@xeon-e3>
Date: Fri, 12 Oct 2018 08:40:28 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Cc: netdev@...r.kernel.org, roopa@...ulusnetworks.com,
dsahern@...nel.org
Subject: Re: [PATCH iproute2 net-next] bridge: add support for backup port
On Fri, 12 Oct 2018 14:42:55 +0300
Nikolay Aleksandrov <nikolay@...ulusnetworks.com> wrote:
> This patch adds support for the new backup port option that can be set
> on a bridge port. If the port's carrier goes down all of the traffic
> gets redirected to the configured backup port. We add the following new
> arguments:
> $ ip link set dev brport type bridge_slave backup_port brport2
> $ ip link set dev brport type bridge_slave nobackup_port
>
> $ bridge link set dev brport backup_port brport2
> $ bridge link set dev brport nobackup_port
>
> The man pages are updated respectively.
> Also 2 minor style adjustments:
> - add missing space to bridge man page's state argument
> - use lower starting case for vlan_tunnel in ip-link man page (to be
> consistent with the rest)
>
> Signed-off-by: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
This seems a bit like feature creep in the bridge.
Why not use team or bonding?
Powered by blists - more mailing lists