From: Stephen Hemminger <stephen@networkplumber.org>
To: Nikolay Aleksandrov <nikolay@cumulusnetworks.com>
Cc: netdev@vger.kernel.org, roopa@cumulusnetworks.com, dsahern@kernel.org
Subject: Re: [PATCH iproute2 net-next] bridge: add support for backup port
Date: Fri, 12 Oct 2018 08:40:28 -0700 [thread overview]
Message-ID: <20181012084028.5a64747f@xeon-e3> (raw)
In-Reply-To: <20181012114255.17217-1-nikolay@cumulusnetworks.com>
On Fri, 12 Oct 2018 14:42:55 +0300
Nikolay Aleksandrov <nikolay@cumulusnetworks.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@cumulusnetworks.com>
This seems a bit like feature creep in the bridge.
Why not use team or bonding?
next prev parent reply other threads:[~2018-10-12 23:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 11:42 [PATCH iproute2 net-next] bridge: add support for backup port Nikolay Aleksandrov
2018-10-12 15:40 ` Stephen Hemminger [this message]
2018-10-12 16:01 ` Nikolay Aleksandrov
2018-10-14 2:30 ` David Ahern
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=20181012084028.5a64747f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dsahern@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
/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