networkd: bond support primary slave and active slave (#4873)

active_slave:

Specifies the new active slave for modes that support it
(active-backup, balance-alb and balance-tlb).

primary slave:
systemd-networks currently lacks the capability to set the primary slave
in an
active-backup bonding. This is necessary if you prefer one interface
over the
other. A common example is a eth0-wlan0 bonding on a laptop where you'd
want to
switch to the wired connection whenever it's available.

Fixes: #2837
This commit is contained in:
Susant Sahani
2016-12-21 19:10:36 +01:00
committed by Lennart Poettering
parent 7dd6974c46
commit eb64b435eb
4 changed files with 89 additions and 0 deletions
+27
View File
@@ -1072,6 +1072,33 @@
</listitem>
</varlistentry>
<varlistentry>
<term><varname>ActiveSlave=</varname></term>
<listitem>
<para>A boolean. Specifies the new active slave. The <literal>ActiveSlave=</literal>
option is only valid for following modes:
<literal>active-backup</literal>,
<literal>balance-alb</literal> and
<literal>balance-tlb</literal>. Defaults to false.
</para>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>PrimarySlave=</varname></term>
<listitem>
<para>A boolean. Specifies which slave is the primary device. The specified
device will always be the active slave while it is available. Only when the
primary is off-line will alternate devices be used. This is useful when
one slave is preferred over another, e.g. when one slave has higher throughput
than another. The <literal>PrimarySlave=</literal> option is only valid for
following modes:
<literal>active-backup</literal>,
<literal>balance-alb</literal> and
<literal>balance-tlb</literal>. Defaults to false.
</para>
</listitem>
</varlistentry>
</variablelist>
<para>For more detail information see