On October 12, 2018 6:40:28 PM GMT+03:00, Stephen Hemminger <step...@networkplumber.org> wrote: >On Fri, 12 Oct 2018 14:42:55 +0300 >Nikolay Aleksandrov <niko...@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 <niko...@cumulusnetworks.com> > >This seems a bit like feature creep in the bridge. >Why not use team or bonding?
Not really, the bond/team cannot work in such way. We did discuss it when the kernel patches were sent, for more information please check https://www.spinics.net/lists/netdev/msg514642.html Thanks, Nik
