2014-02-25 22:30:40 +04:00
<?xml version='1.0'?> <!-- * - nxml - * -->
2019-03-14 16:40:58 +03:00
< !DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
2015-06-18 20:47:44 +03:00
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
2019-03-14 16:29:37 +03:00
<!-- SPDX - License - Identifier: LGPL - 2.1+ -->
2014-02-25 22:30:40 +04:00
<refentry id= "systemd.netdev" conditional= 'ENABLE_NETWORKD' >
2015-02-04 05:14:13 +03:00
<refentryinfo >
<title > systemd.network</title>
<productname > systemd</productname>
</refentryinfo>
<refmeta >
<refentrytitle > systemd.netdev</refentrytitle>
<manvolnum > 5</manvolnum>
</refmeta>
<refnamediv >
<refname > systemd.netdev</refname>
<refpurpose > Virtual Network Device configuration</refpurpose>
</refnamediv>
<refsynopsisdiv >
<para > <filename > <replaceable > netdev</replaceable> .netdev</filename> </para>
</refsynopsisdiv>
<refsect1 >
<title > Description</title>
<para > Network setup is performed by
<citerefentry > <refentrytitle > systemd-networkd</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> .
</para>
2016-09-10 16:34:07 +03:00
<para > The main Virtual Network Device file must have the extension <filename > .netdev</filename> ;
other extensions are ignored. Virtual network devices are created as soon as networkd is
started. If a netdev with the specified name already exists, networkd will use that as-is rather
than create its own. Note that the settings of the pre-existing netdev will not be changed by
2015-02-04 05:14:13 +03:00
networkd.</para>
2016-09-10 16:34:07 +03:00
<para > The <filename > .netdev</filename> files are read from the files located in the system
network directory <filename > /usr/lib/systemd/network</filename> , the volatile runtime network
directory <filename > /run/systemd/network</filename> and the local administration network
directory <filename > /etc/systemd/network</filename> . All configuration files are collectively
sorted and processed in lexical order, regardless of the directories in which they live.
However, files with identical filenames replace each other. Files in <filename > /etc</filename>
have the highest priority, files in <filename > /run</filename> take precedence over files with
the same name in <filename > /usr/lib</filename> . This can be used to override a system-supplied
configuration file with a local file if needed. As a special case, an empty file (file size 0)
or symlink with the same name pointing to <filename > /dev/null</filename> disables the
configuration file entirely (it is "masked").</para>
<para > Along with the netdev file <filename > foo.netdev</filename> , a "drop-in" directory
<filename > foo.netdev.d/</filename> may exist. All files with the suffix <literal > .conf</literal>
from this directory will be parsed after the file itself is parsed. This is useful to alter or
add configuration settings, without having to modify the main configuration file. Each drop-in
file must have appropriate section headers.</para>
<para > In addition to <filename > /etc/systemd/network</filename> , drop-in <literal > .d</literal>
directories can be placed in <filename > /usr/lib/systemd/network</filename> or
<filename > /run/systemd/network</filename> directories. Drop-in files in
<filename > /etc</filename> take precedence over those in <filename > /run</filename> which in turn
take precedence over those in <filename > /usr/lib</filename> . Drop-in files under any of these
directories take precedence over the main netdev file wherever located. (Of course, since
<filename > /run</filename> is temporary and <filename > /usr/lib</filename> is for vendors, it is
unlikely drop-ins should be used in either of those places.)</para>
2015-02-04 05:14:13 +03:00
</refsect1>
<refsect1 >
<title > Supported netdev kinds</title>
<para > The following kinds of virtual network devices may be
configured in <filename > .netdev</filename> files:</para>
<table >
<title > Supported kinds of virtual network devices</title>
<tgroup cols= '2' >
<colspec colname= 'kind' />
<colspec colname= 'explanation' />
<thead > <row >
<entry > Kind</entry>
<entry > Description</entry>
</row> </thead>
<tbody >
<row > <entry > <varname > bond</varname> </entry>
<entry > A bond device is an aggregation of all its slave devices. See <ulink url= "https://www.kernel.org/doc/Documentation/networking/bonding.txt" > Linux Ethernet Bonding Driver HOWTO</ulink> for details.Local configuration</entry> </row>
<row > <entry > <varname > bridge</varname> </entry>
2014-08-03 09:11:37 +04:00
<entry > A bridge device is a software switch, and each of its slave devices and the bridge itself are ports of the switch.</entry> </row>
2015-02-04 05:14:13 +03:00
<row > <entry > <varname > dummy</varname> </entry>
<entry > A dummy device drops all packets sent to it.</entry> </row>
<row > <entry > <varname > gre</varname> </entry>
<entry > A Level 3 GRE tunnel over IPv4. See <ulink url= "https://tools.ietf.org/html/rfc2784" > RFC 2784</ulink> for details.</entry> </row>
<row > <entry > <varname > gretap</varname> </entry>
<entry > A Level 2 GRE tunnel over IPv4.</entry> </row>
2018-11-26 14:50:09 +03:00
<row > <entry > <varname > erspan</varname> </entry>
2019-03-21 19:53:46 +03:00
<entry > ERSPAN mirrors traffic on one or more source ports and delivers the mirrored traffic to one or more destination ports on another switch. The traffic is encapsulated in generic routing encapsulation (GRE) and is therefore routable across a layer 3 network between the source switch and the destination switch.</entry> </row>
2018-11-26 14:50:09 +03:00
2015-02-04 05:14:13 +03:00
<row > <entry > <varname > ip6gre</varname> </entry>
<entry > A Level 3 GRE tunnel over IPv6.</entry> </row>
<row > <entry > <varname > ip6tnl</varname> </entry>
<entry > An IPv4 or IPv6 tunnel over IPv6</entry> </row>
<row > <entry > <varname > ip6gretap</varname> </entry>
2016-07-12 12:58:14 +03:00
<entry > A Level 2 GRE tunnel over IPv6.</entry> </row>
2015-02-04 05:14:13 +03:00
<row > <entry > <varname > ipip</varname> </entry>
<entry > An IPv4 over IPv4 tunnel.</entry> </row>
<row > <entry > <varname > ipvlan</varname> </entry>
<entry > An ipvlan device is a stacked device which receives packets from its underlying device based on IP address filtering.</entry> </row>
<row > <entry > <varname > macvlan</varname> </entry>
<entry > A macvlan device is a stacked device which receives packets from its underlying device based on MAC address filtering.</entry> </row>
2015-07-27 08:49:08 +03:00
<row > <entry > <varname > macvtap</varname> </entry>
<entry > A macvtap device is a stacked device which receives packets from its underlying device based on MAC address filtering.</entry> </row>
2015-02-04 05:14:13 +03:00
<row > <entry > <varname > sit</varname> </entry>
<entry > An IPv6 over IPv4 tunnel.</entry> </row>
<row > <entry > <varname > tap</varname> </entry>
<entry > A persistent Level 2 tunnel between a network device and a device node.</entry> </row>
<row > <entry > <varname > tun</varname> </entry>
<entry > A persistent Level 3 tunnel between a network device and a device node.</entry> </row>
<row > <entry > <varname > veth</varname> </entry>
2014-08-03 09:11:37 +04:00
<entry > An Ethernet tunnel between a pair of network devices.</entry> </row>
2015-02-04 05:14:13 +03:00
<row > <entry > <varname > vlan</varname> </entry>
<entry > A VLAN is a stacked device which receives packets from its underlying device based on VLAN tagging. See <ulink url= "http://www.ieee802.org/1/pages/802.1Q.html" > IEEE 802.1Q</ulink> for details.</entry> </row>
<row > <entry > <varname > vti</varname> </entry>
<entry > An IPv4 over IPSec tunnel.</entry> </row>
2015-04-22 11:44:56 +03:00
<row > <entry > <varname > vti6</varname> </entry>
<entry > An IPv6 over IPSec tunnel.</entry> </row>
2015-02-04 05:14:13 +03:00
<row > <entry > <varname > vxlan</varname> </entry>
<entry > A virtual extensible LAN (vxlan), for connecting Cloud computing deployments.</entry> </row>
2016-06-10 02:57:51 +03:00
2017-04-25 07:15:05 +03:00
<row > <entry > <varname > geneve</varname> </entry>
<entry > A GEneric NEtwork Virtualization Encapsulation (GENEVE) netdev driver.</entry> </row>
2019-03-06 22:51:29 +03:00
<row > <entry > <varname > l2tp</varname> </entry>
<entry > A Layer 2 Tunneling Protocol (L2TP) is a tunneling protocol used to support virtual private networks (VPNs) or as part of the delivery of services by ISPs. It does not provide any encryption or confidentiality by itself</entry> </row>
2019-04-03 14:27:36 +03:00
<row > <entry > <varname > macsec</varname> </entry>
<entry > Media Access Control Security (MACsec) is an 802.1AE IEEE industry-standard security technology that provides secure communication for all traffic on Ethernet links. MACsec provides point-to-point security on Ethernet links between directly connected nodes and is capable of identifying and preventing most security threats.</entry> </row>
2016-06-10 02:57:51 +03:00
<row > <entry > <varname > vrf</varname> </entry>
2016-09-14 19:15:16 +03:00
<entry > A Virtual Routing and Forwarding (<ulink url= "https://www.kernel.org/doc/Documentation/networking/vrf.txt" > VRF</ulink> ) interface to create separate routing and forwarding domains.</entry> </row>
<row > <entry > <varname > vcan</varname> </entry>
2016-10-02 14:24:54 +03:00
<entry > The virtual CAN driver (vcan). Similar to the network loopback devices, vcan offers a virtual local CAN interface.</entry> </row>
2016-06-10 02:57:51 +03:00
2017-11-22 10:23:22 +03:00
<row > <entry > <varname > vxcan</varname> </entry>
<entry > The virtual CAN tunnel driver (vxcan). Similar to the virtual ethernet driver veth, vxcan implements a local CAN traffic tunnel between two virtual CAN network devices. When creating a vxcan, two vxcan devices are created as pair. When one end receives the packet it appears on its pair and vice versa. The vxcan can be used for cross namespace communication.
</entry> </row>
2017-12-18 17:20:34 +03:00
<row > <entry > <varname > wireguard</varname> </entry>
<entry > WireGuard Secure Network Tunnel.</entry> </row>
2018-06-02 16:06:33 +03:00
<row > <entry > <varname > netdevsim</varname> </entry>
<entry > A simulator. This simulated networking device is used for testing various networking APIs and at this time is particularly focused on testing hardware offloading related interfaces.</entry> </row>
2018-06-03 10:07:41 +03:00
<row > <entry > <varname > fou</varname> </entry>
<entry > Foo-over-UDP tunneling.</entry> </row>
2015-02-04 05:14:13 +03:00
</tbody>
</tgroup>
</table>
</refsect1>
<refsect1 >
<title > [Match] Section Options</title>
<para > A virtual network device is only created if the
<literal > [Match]</literal> section matches the current
environment, or if the section is empty. The following keys are
accepted:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Host=</varname> </term>
<listitem >
2019-03-08 09:51:17 +03:00
<para > Matches against the hostname or machine ID of the host. See
<literal > ConditionHost=</literal> in
2015-02-04 05:14:13 +03:00
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2019-03-08 09:51:17 +03:00
for details. When prefixed with an exclamation mark (<literal > !</literal> ), the result is negated.
If an empty string is assigned, then previously assigned value is cleared.
2015-02-04 05:14:13 +03:00
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Virtualization=</varname> </term>
<listitem >
2019-03-08 09:51:17 +03:00
<para > Checks whether the system is executed in a virtualized environment and optionally test
whether it is a specific implementation. See <literal > ConditionVirtualization=</literal> in
2015-02-04 05:14:13 +03:00
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2019-03-08 09:51:17 +03:00
for details. When prefixed with an exclamation mark (<literal > !</literal> ), the result is negated.
If an empty string is assigned, then previously assigned value is cleared.
2015-02-04 05:14:13 +03:00
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > KernelCommandLine=</varname> </term>
<listitem >
2019-03-08 09:51:17 +03:00
<para > Checks whether a specific kernel command line option is set. See
2015-02-04 05:14:13 +03:00
<literal > ConditionKernelCommandLine=</literal> in
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2019-03-08 09:51:17 +03:00
for details. When prefixed with an exclamation mark (<literal > !</literal> ), the result is negated.
If an empty string is assigned, then previously assigned value is cleared.
2015-02-04 05:14:13 +03:00
</para>
</listitem>
</varlistentry>
core,udev,networkd: add ConditionKernelVersion=
This adds a simple condition/assert/match to the service manager, to
udev's .link handling and to networkd, for matching the kernel version
string.
In this version we only do fnmatch() based globbing, but we might want
to extend that to version comparisons later on, if we like, by slightly
extending the syntax with ">=", "<=", ">", "<" and "==" expressions.
2017-12-13 22:34:13 +03:00
<varlistentry >
<term > <varname > KernelVersion=</varname> </term>
<listitem >
2019-03-08 09:51:17 +03:00
<para > Checks whether the kernel version (as reported by <command > uname -r</command> ) matches a
certain expression. See <literal > ConditionKernelVersion=</literal> in
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
for details. When prefixed with an exclamation mark (<literal > !</literal> ), the result is negated.
If an empty string is assigned, then previously assigned value is cleared.
core,udev,networkd: add ConditionKernelVersion=
This adds a simple condition/assert/match to the service manager, to
udev's .link handling and to networkd, for matching the kernel version
string.
In this version we only do fnmatch() based globbing, but we might want
to extend that to version comparisons later on, if we like, by slightly
extending the syntax with ">=", "<=", ">", "<" and "==" expressions.
2017-12-13 22:34:13 +03:00
</para>
</listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
<varlistentry >
<term > <varname > Architecture=</varname> </term>
<listitem >
2019-03-08 09:51:17 +03:00
<para > Checks whether the system is running on a specific architecture. See
<literal > ConditionArchitecture=</literal> in
2015-02-04 05:14:13 +03:00
<citerefentry > <refentrytitle > systemd.unit</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2019-03-08 09:51:17 +03:00
for details. When prefixed with an exclamation mark (<literal > !</literal> ), the result is negated.
If an empty string is assigned, then previously assigned value is cleared.
2015-02-04 05:14:13 +03:00
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > [NetDev] Section Options</title>
<para > The <literal > [NetDev]</literal> section accepts the
following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Description=</varname> </term>
<listitem >
<para > A free-form description of the netdev.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Name=</varname> </term>
<listitem >
<para > The interface name used when creating the netdev.
This option is compulsory.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Kind=</varname> </term>
<listitem >
<para > The netdev kind. This option is compulsory. See the
<literal > Supported netdev kinds</literal> section for the
valid keys.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > MTUBytes=</varname> </term>
<listitem >
2018-06-25 19:43:33 +03:00
<para > The maximum transmission unit in bytes to set for the device. The usual suffixes K, M, G,
are supported and are understood to the base of 1024. For <literal > tun</literal> or
<literal > tap</literal> devices, <varname > MTUBytes=</varname> setting is not currently supported in
<literal > [NetDev]</literal> section. Please specify it in <literal > [Link]</literal> section of
corresponding
<citerefentry > <refentrytitle > systemd.network</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
files.</para>
2015-02-04 05:14:13 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > MACAddress=</varname> </term>
<listitem >
2019-01-29 17:28:52 +03:00
<para > The MAC address to use for the device. For <literal > tun</literal> or <literal > tap</literal>
devices, setting <varname > MACAddress=</varname> in the <literal > [NetDev]</literal> section is not
supported. Please specify it in <literal > [Link]</literal> section of the corresponding
2018-06-25 19:43:33 +03:00
<citerefentry > <refentrytitle > systemd.network</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
2019-01-29 17:28:52 +03:00
file. If this option is not set, <literal > vlan</literal> devices inherit the MAC address of the
physical interface. For other kind of netdevs, if this option is not set, then MAC address is
generated based on the interface name and the
<citerefentry > <refentrytitle > machine-id</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> .
</para>
2015-02-04 05:14:13 +03:00
</listitem>
</varlistentry>
</variablelist>
</refsect1>
2015-10-05 07:08:32 +03:00
<refsect1 >
<title > [Bridge] Section Options</title>
<para > The <literal > [Bridge]</literal> section only applies for
netdevs of kind <literal > bridge</literal> , and accepts the
2014-08-03 09:11:37 +04:00
following keys:</para>
2015-10-05 07:08:32 +03:00
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > HelloTimeSec=</varname> </term>
<listitem >
2014-08-03 09:11:37 +04:00
<para > HelloTimeSec specifies the number of seconds between two hello packets
2015-10-05 07:08:32 +03:00
sent out by the root bridge and the designated bridges. Hello packets are
used to communicate information about the topology throughout the entire
bridged local area network.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > MaxAgeSec=</varname> </term>
<listitem >
<para > MaxAgeSec specifies the number of seconds of maximum message age.
If the last seen (received) hello packet is more than this number of
seconds old, the bridge in question will start the takeover procedure
in attempt to become the Root Bridge itself.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > ForwardDelaySec=</varname> </term>
<listitem >
<para > ForwardDelaySec specifies the number of seconds spent in each
of the Listening and Learning states before the Forwarding state is entered.</para>
</listitem>
</varlistentry>
2016-08-31 21:06:23 +03:00
<varlistentry >
<term > <varname > AgeingTimeSec=</varname> </term>
<listitem >
<para > This specifies the number of seconds a MAC Address will be kept in
2016-09-26 12:32:47 +03:00
the forwarding database after having a packet received from this MAC Address.</para>
2016-08-31 21:06:23 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Priority=</varname> </term>
<listitem >
<para > The priority of the bridge. An integer between 0 and 65535. A lower value
means higher priority. The bridge having the lowest priority will be elected as root bridge.</para>
</listitem>
</varlistentry>
2017-09-08 13:36:06 +03:00
<varlistentry >
<term > <varname > GroupForwardMask=</varname> </term>
<listitem >
<para > A 16-bit bitmask represented as an integer which allows forwarding of link
local frames with 802.1D reserved addresses (01:80:C2:00:00:0X). A logical AND
is performed between the specified bitmask and the exponentiation of 2^X, the
lower nibble of the last octet of the MAC address. For example, a value of 8
would allow forwarding of frames addressed to 01:80:C2:00:00:03 (802.1X PAE).</para>
</listitem>
</varlistentry>
2016-08-31 21:06:23 +03:00
<varlistentry >
<term > <varname > DefaultPVID=</varname> </term>
<listitem >
2017-05-29 18:20:01 +03:00
<para > This specifies the default port VLAN ID of a newly attached bridge port.
Set this to an integer in the range 1– <literal > none</literal> to disable the PVID.</para>
2016-08-31 21:06:23 +03:00
</listitem>
</varlistentry>
2016-04-18 14:45:52 +03:00
<varlistentry >
<term > <varname > MulticastQuerier=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. This setting controls the IFLA_BR_MCAST_QUERIER option in the kernel.
2016-04-18 14:45:52 +03:00
If enabled, the kernel will send general ICMP queries from a zero source address.
This feature should allow faster convergence on startup, but it causes some
multicast-aware switches to misbehave and disrupt forwarding of multicast packets.
2018-11-27 08:40:25 +03:00
When unset, the kernel's default will be used.
2016-04-18 14:45:52 +03:00
</para>
</listitem>
</varlistentry>
2016-05-15 16:15:20 +03:00
<varlistentry >
<term > <varname > MulticastSnooping=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. This setting controls the IFLA_BR_MCAST_SNOOPING option in the kernel.
2016-05-15 16:15:20 +03:00
If enabled, IGMP snooping monitors the Internet Group Management Protocol (IGMP) traffic
2018-11-27 08:40:25 +03:00
between hosts and multicast routers. When unset, the kernel's default will be used.
2016-05-15 16:15:20 +03:00
</para>
</listitem>
</varlistentry>
2016-05-30 18:00:16 +03:00
<varlistentry >
<term > <varname > VLANFiltering=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. This setting controls the IFLA_BR_VLAN_FILTERING option in the kernel.
2018-11-27 08:40:25 +03:00
If enabled, the bridge will be started in VLAN-filtering mode. When unset, the kernel's default will be used.
2016-05-30 18:00:16 +03:00
</para>
</listitem>
</varlistentry>
2016-08-06 02:44:57 +03:00
<varlistentry >
<term > <varname > STP=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. This enables the bridge's Spanning Tree Protocol (STP).
2018-11-27 08:40:25 +03:00
When unset, the kernel's default will be used.
2016-08-06 02:44:57 +03:00
</para>
</listitem>
</varlistentry>
2015-10-05 07:08:32 +03:00
</variablelist>
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > [VLAN] Section Options</title>
<para > The <literal > [VLAN]</literal> section only applies for
netdevs of kind <literal > vlan</literal> , and accepts the
following key:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Id=</varname> </term>
<listitem >
<para > The VLAN ID to use. An integer in the range 0–
This option is compulsory.</para>
</listitem>
</varlistentry>
2017-04-21 12:01:59 +03:00
<varlistentry >
<term > <varname > GVRP=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. The Generic VLAN Registration Protocol (GVRP) is a protocol that
allows automatic learning of VLANs on a network.
2018-11-27 08:40:25 +03:00
When unset, the kernel's default will be used.
</para>
2017-04-21 12:01:59 +03:00
</listitem>
</varlistentry>
2017-05-09 21:25:11 +03:00
<varlistentry >
<term > <varname > MVRP=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. Multiple VLAN Registration Protocol (MVRP) formerly known as GARP VLAN
2017-05-09 21:25:11 +03:00
Registration Protocol (GVRP) is a standards-based Layer 2 network protocol,
for automatic configuration of VLAN information on switches. It was defined
2018-11-27 09:07:58 +03:00
in the 802.1ak amendment to 802.1Q-2005. When unset, the kernel's default will be used.
2018-11-27 08:40:25 +03:00
</para>
2017-05-09 21:25:11 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > LooseBinding=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. The VLAN loose binding mode, in which only the operational state is passed
2017-05-09 21:25:11 +03:00
from the parent to the associated VLANs, but the VLAN device state is not changed.
2018-11-27 09:07:58 +03:00
When unset, the kernel's default will be used.</para>
2017-05-09 21:25:11 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > ReorderHeader=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. The VLAN reorder header is set VLAN interfaces behave like physical interfaces.
When unset, the kernel's default will be used.</para>
2017-05-09 21:25:11 +03:00
</listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
</variablelist>
</refsect1>
<refsect1 >
<title > [MACVLAN] Section Options</title>
<para > The <literal > [MACVLAN]</literal> section only applies for
netdevs of kind <literal > macvlan</literal> , and accepts the
following key:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Mode=</varname> </term>
<listitem >
<para > The MACVLAN mode to use. The supported options are
<literal > private</literal> ,
<literal > vepa</literal> ,
<literal > bridge</literal> , and
<literal > passthru</literal> .
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
2015-07-27 08:49:08 +03:00
<refsect1 >
<title > [MACVTAP] Section Options</title>
<para > The <literal > [MACVTAP]</literal> section applies for
netdevs of kind <literal > macvtap</literal> and accepts the
2016-02-08 15:27:22 +03:00
same key as <literal > [MACVLAN]</literal> .</para>
2015-07-27 08:49:08 +03:00
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > [IPVLAN] Section Options</title>
<para > The <literal > [IPVLAN]</literal> section only applies for
netdevs of kind <literal > ipvlan</literal> , and accepts the
following key:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Mode=</varname> </term>
<listitem >
<para > The IPVLAN mode to use. The supported options are
2017-12-23 20:55:03 +03:00
<literal > L2</literal> ,<literal > L3</literal> and <literal > L3S</literal> .
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Flags=</varname> </term>
<listitem >
<para > The IPVLAN flags to use. The supported options are
<literal > bridge</literal> ,<literal > private</literal> and <literal > vepa</literal> .
2015-02-04 05:14:13 +03:00
</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > [VXLAN] Section Options</title>
<para > The <literal > [VXLAN]</literal> section only applies for
netdevs of kind <literal > vxlan</literal> , and accepts the
following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Id=</varname> </term>
<listitem >
<para > The VXLAN ID to use.</para>
</listitem>
</varlistentry>
<varlistentry >
2017-02-24 22:01:47 +03:00
<term > <varname > Remote=</varname> </term>
2015-02-04 05:14:13 +03:00
<listitem >
2018-02-08 12:22:46 +03:00
<para > Configures destination IP address.</para>
2015-02-04 05:14:13 +03:00
</listitem>
</varlistentry>
<varlistentry >
2017-02-24 22:01:47 +03:00
<term > <varname > Local=</varname> </term>
<listitem >
<para > Configures local IP address.</para>
</listitem>
</varlistentry>
<varlistentry >
2015-02-04 05:14:13 +03:00
<term > <varname > TOS=</varname> </term>
<listitem >
<para > The Type Of Service byte value for a vxlan interface.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > TTL=</varname> </term>
<listitem >
<para > A fixed Time To Live N on Virtual eXtensible Local
2014-08-03 09:11:12 +04:00
Area Network packets. N is a number in the range 1–
2015-02-04 05:14:13 +03:00
is a special value meaning that packets inherit the TTL
value.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > MacLearning=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, enables dynamic MAC learning
2015-02-04 05:14:13 +03:00
to discover remote MAC addresses.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > FDBAgeingSec=</varname> </term>
<listitem >
<para > The lifetime of Forwarding Database entry learnt by
2014-08-03 09:11:12 +04:00
the kernel, in seconds.</para>
2015-02-04 05:14:13 +03:00
</listitem>
</varlistentry>
<varlistentry >
2015-10-21 10:06:28 +03:00
<term > <varname > MaximumFDBEntries=</varname> </term>
<listitem >
<para > Configures maximum number of FDB entries.</para>
</listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
<varlistentry >
2016-12-21 20:59:15 +03:00
<term > <varname > ReduceARPProxy=</varname> </term>
2015-02-04 05:14:13 +03:00
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, bridge-connected VXLAN tunnel
2016-12-21 20:59:15 +03:00
endpoint answers ARP requests from the local bridge on behalf
of remote Distributed Overlay Virtual Ethernet
<ulink url= "https://en.wikipedia.org/wiki/Distributed_Overlay_Virtual_Ethernet" >
(DVOE)</ulink> clients. Defaults to false.</para>
2015-02-04 05:14:13 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > L2MissNotification=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, enables netlink LLADDR miss
2015-02-04 05:14:13 +03:00
notifications.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > L3MissNotification=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, enables netlink IP address miss
2015-02-04 05:14:13 +03:00
notifications.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > RouteShortCircuit=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, route short circuiting is turned
2015-02-04 05:14:13 +03:00
on.</para>
</listitem>
</varlistentry>
2015-03-05 19:32:47 +03:00
<varlistentry >
2016-10-10 20:52:12 +03:00
<term > <varname > UDPChecksum=</varname> </term>
2015-03-05 19:32:47 +03:00
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, transmitting UDP checksums when doing VXLAN/IPv4 is turned on.</para>
2015-03-05 19:32:47 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > UDP6ZeroChecksumTx=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, sending zero checksums in VXLAN/IPv6 is turned on.</para>
2015-03-05 19:32:47 +03:00
</listitem>
</varlistentry>
<varlistentry >
2016-10-10 20:52:12 +03:00
<term > <varname > UDP6ZeroChecksumRx=</varname> </term>
2015-03-05 19:32:47 +03:00
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, receiving zero checksums in VXLAN/IPv6 is turned on.</para>
2016-10-07 16:46:18 +03:00
</listitem>
</varlistentry>
<varlistentry >
2016-10-10 20:52:12 +03:00
<term > <varname > RemoteChecksumTx=</varname> </term>
2016-10-07 16:46:18 +03:00
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, remote transmit checksum offload of VXLAN is turned on.</para>
2016-10-07 16:46:18 +03:00
</listitem>
</varlistentry>
<varlistentry >
2016-10-10 20:52:12 +03:00
<term > <varname > RemoteChecksumRx=</varname> </term>
2016-10-07 16:46:18 +03:00
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, remote receive checksum offload in VXLAN is turned on.</para>
2015-03-05 19:32:47 +03:00
</listitem>
</varlistentry>
2015-07-29 11:36:46 +03:00
<varlistentry >
<term > <varname > GroupPolicyExtension=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, it enables Group Policy VXLAN extension security label mechanism
2014-08-03 09:11:12 +04:00
across network peers based on VXLAN. For details about the Group Policy VXLAN, see the
2015-07-29 11:36:46 +03:00
<ulink url= "https://tools.ietf.org/html/draft-smith-vxlan-group-policy" >
VXLAN Group Policy </ulink> document. Defaults to false.</para>
</listitem>
</varlistentry>
2015-11-28 05:35:28 +03:00
<varlistentry >
<term > <varname > DestinationPort=</varname> </term>
<listitem >
<para > Configures the default destination UDP port on a per-device basis.
If destination port is not specified then Linux kernel default will be used.
2017-04-29 21:04:17 +03:00
Set destination port 4789 to get the IANA assigned value. If not set or if the
destination port is assigned the empty string the default port of 4789 is used.</para>
2015-11-28 05:35:28 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > PortRange=</varname> </term>
<listitem >
<para > Configures VXLAN port range. VXLAN bases source
UDP port based on flow to help the receiver to be able
to load balance based on outer header flow. It
restricts the port range to the normal UDP local
ports, and allows overriding via configuration.</para>
</listitem>
</varlistentry>
2017-03-08 16:11:03 +03:00
<varlistentry >
<term > <varname > FlowLabel=</varname> </term>
<listitem >
<para > Specifies the flow label to use in outgoing packets.
The valid range is 0-1048575.
</para>
</listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
</variablelist>
</refsect1>
2017-04-25 07:15:05 +03:00
<refsect1 >
<title > [GENEVE] Section Options</title>
<para > The <literal > [GENEVE]</literal> section only applies for
netdevs of kind <literal > geneve</literal> , and accepts the
following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Id=</varname> </term>
<listitem >
2017-08-04 00:36:21 +03:00
<para > Specifies the Virtual Network Identifier (VNI) to use. Ranges [0-16777215].</para>
2017-04-25 07:15:05 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Remote=</varname> </term>
<listitem >
<para > Specifies the unicast destination IP address to use in outgoing packets.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > TOS=</varname> </term>
<listitem >
2017-04-29 21:04:17 +03:00
<para > Specifies the TOS value to use in outgoing packets. Ranges [1-255].</para>
2017-04-25 07:15:05 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > TTL=</varname> </term>
<listitem >
2017-04-29 21:04:17 +03:00
<para > Specifies the TTL value to use in outgoing packets. Ranges [1-255].</para>
2017-04-25 07:15:05 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > UDPChecksum=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, specifies if UDP checksum is calculated for transmitted packets over IPv4.</para>
2017-04-25 07:15:05 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > UDP6ZeroChecksumTx=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, skip UDP checksum calculation for transmitted packets over IPv6.</para>
2017-04-25 07:15:05 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > UDP6ZeroChecksumRx=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, allows incoming UDP packets over IPv6 with zero checksum field.</para>
2017-04-25 07:15:05 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > DestinationPort=</varname> </term>
<listitem >
2017-04-29 21:04:17 +03:00
<para > Specifies destination port. Defaults to 6081. If not set or assigned the empty string, the default
port of 6081 is used.</para>
2017-04-25 07:15:05 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > FlowLabel=</varname> </term>
<listitem >
<para > Specifies the flow label to use in outgoing packets.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
2019-03-06 22:51:29 +03:00
<refsect1 >
<title > [L2TP] Section Options</title>
<para > The <literal > [L2TP]</literal> section only applies for
netdevs of kind <literal > l2tp</literal> , and accepts the
following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > TunnelId=</varname> </term>
<listitem >
<para > Specifies the tunnel id. The value used must match the <literal > PeerTunnelId=</literal> value being used at the peer.
Ranges a number between 1 and 4294967295). This option is compulsory.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > PeerTunnelId=</varname> </term>
<listitem >
<para > Specifies the peer tunnel id. The value used must match the <literal > PeerTunnelId=</literal> value being used at the peer.
Ranges a number between 1 and 4294967295). This option is compulsory.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Remote=</varname> </term>
<listitem >
<para > Specifies the IP address of the remote peer. This option is compulsory.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Local=</varname> </term>
<listitem >
2019-03-12 05:35:23 +03:00
<para > Specifies the IP address of the local interface. Takes an IP address, or the special values
<literal > auto</literal> , <literal > static</literal> , or <literal > dynamic</literal> . When an address
is set, then the local interface must have the address. If <literal > auto</literal> , then one of the
addresses on the local interface is used. Similarly, if <literal > static</literal> or
<literal > dynamic</literal> is set, then one of the static or dynamic addresses on the local
interface is used. Defaults to <literal > auto</literal> .</para>
2019-03-06 22:51:29 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > EncapsulationType=</varname> </term>
<listitem >
<para > Specifies the encapsulation type of the tunnel. Takes one of <literal > udp</literal> or <literal > ip</literal> .</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > UDPSourcePort=</varname> </term>
<listitem >
<para > Specifies the UDP source port to be used for the tunnel. When UDP encapsulation is selected it's mandotory. Ignored when ip
encapsulation is selected.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > DestinationPort=</varname> </term>
<listitem >
<para > Specifies destination port. When UDP encapsulation is selected it's mandotory. Ignored when ip
encapsulation is selected.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > UDPChecksum=</varname> </term>
<listitem >
<para > Takes a boolean. When true, specifies if UDP checksum is calculated for transmitted packets over IPv4.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > UDP6ZeroChecksumTx=</varname> </term>
<listitem >
<para > Takes a boolean. When true, skip UDP checksum calculation for transmitted packets over IPv6.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > UDP6ZeroChecksumRx=</varname> </term>
<listitem >
<para > Takes a boolean. When true, allows incoming UDP packets over IPv6 with zero checksum field.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > [L2TPSession] Section Options</title>
<para > The <literal > [L2TPSession]</literal> section only applies for
netdevs of kind <literal > l2tp</literal> , and accepts the
following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Name=</varname> </term>
<listitem >
<para > Specifies the name of the sesssion. This option is compulsory.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > SessionId=</varname> </term>
<listitem >
<para > Specifies the sesssion id. The value used must match the <literal > SessionId=</literal> value being used at the peer.
Ranges a number between 1 and 4294967295). This option is compulsory.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > PeerSessionId=</varname> </term>
<listitem >
<para > Specifies the peer session id. The value used must match the <literal > PeerSessionId=</literal> value being used at the peer.
Ranges a number between 1 and 4294967295). This option is compulsory.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Layer2SpecificHeader=</varname> </term>
<listitem >
<para > Specifies layer2specific header type of the session. One of <literal > none</literal> or <literal > default</literal> . Defaults to <literal > default</literal> .</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
2019-04-03 14:27:36 +03:00
<refsect1 >
<title > [MACsec] Section Options</title>
<para > The <literal > [MACsec]</literal> section only applies for network devices of kind
<literal > macsec</literal> , and accepts the following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Port=</varname> </term>
<listitem >
<para > Specifies the port to be used for the MACsec transmit channel. The port is used to make
secure channel identifier (SCI). Takes a value between 1 and 65535. Defaults to unset.
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Encrypt=</varname> </term>
<listitem >
<para > Takes a boolean. When true, enable encryption. Defaults to unset.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > [MACsecReceiveChannel] Section Options</title>
<para > The <literal > [MACsecReceiveChannel]</literal> section only applies for network devices of
kind <literal > macsec</literal> , and accepts the following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Port=</varname> </term>
<listitem >
<para > Specifies the port to be used for the MACsec receive channel. The port is used to make
secure channel identifier (SCI). Takes a value between 1 and 65535. This option is
compulsory, and is not set by default.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > MACAddress=</varname> </term>
<listitem >
<para > Specifies the MAC address to be used for the MACsec receive channel. The MAC address
used to make secure channel identifier (SCI). This option is compulsory, and is not set by
default.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > [MACsecTransmitAssociation] Section Options</title>
<para > The <literal > [MACsecTransmitAssociation]</literal> section only applies for network devices
of kind <literal > macsec</literal> , and accepts the following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > PacketNumber=</varname> </term>
<listitem >
<para > Specifies the packet number to be used for replay protection and the construction of
the initialization vector (along with the secure channel identifier [SCI]). Takes a value
between 1-4,294,967,295. Defaults to unset.
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > KeyId=</varname> </term>
<listitem >
<para > Specifies the identification for the key. Takes a number between 0-255. This option
is compulsory, and is not set by default.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Key=</varname> </term>
<listitem >
<para > Specifies the encryption key used in the transmission channel. The same key must be
configured on the peer’
by default. Takes a 128-bit key encoded in a hexadecimal string, for example
<literal > dffafc8d7b9a43d5b9a3dfbbf6a30c16</literal> .</para>
</listitem>
</varlistentry>
2019-04-10 12:07:10 +03:00
<varlistentry >
<term > <varname > KeyFile=</varname> </term>
<listitem >
<para > Takes a absolute path to a file which contains a 128-bit key encoded in a hexadecimal
string, which will be used in the transmission channel. When this option is specified,
<varname > Key=</varname> is ignored. Note that the file must be readable by the user
<literal > systemd-network</literal> , so it should be, e.g., owned by
<literal > root:systemd-network</literal> with a <literal > 0640</literal> file mode.</para>
</listitem>
</varlistentry>
2019-04-03 14:27:36 +03:00
</variablelist>
</refsect1>
<refsect1 >
<title > [MACsecReceiveAssociation] Section Options</title>
<para > The <literal > [MACsecReceiveAssociation]</literal> section only applies for
network devices of kind <literal > macsec</literal> , and accepts the
following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Port=</varname> </term>
<listitem >
<para > Accepts the same key in <literal > [MACsecReceiveChannel]</literal> section.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > MACAddress=</varname> </term>
<listitem >
<para > Accepts the same key in <literal > [MACsecReceiveChannel]</literal> section.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > PacketNumber=</varname> </term>
<listitem >
<para > Accepts the same key in <literal > [MACsecTransmitAssociation]</literal> section.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > KeyId=</varname> </term>
<listitem >
<para > Accepts the same key in <literal > [MACsecTransmitAssociation]</literal> section.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Key=</varname> </term>
<listitem >
<para > Accepts the same key in <literal > [MACsecTransmitAssociation]</literal> section.</para>
</listitem>
</varlistentry>
2019-04-10 12:07:10 +03:00
<varlistentry >
<term > <varname > KeyFile=</varname> </term>
<listitem >
<para > Accepts the same key in <literal > [MACsecTransmitAssociation]</literal> section.</para>
</listitem>
</varlistentry>
2019-04-03 14:27:36 +03:00
</variablelist>
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > [Tunnel] Section Options</title>
<para > The <literal > [Tunnel]</literal> section only applies for
netdevs of kind
<literal > ipip</literal> ,
<literal > sit</literal> ,
<literal > gre</literal> ,
<literal > gretap</literal> ,
<literal > ip6gre</literal> ,
<literal > ip6gretap</literal> ,
2015-04-22 11:44:56 +03:00
<literal > vti</literal> ,
2019-02-03 04:54:09 +03:00
<literal > vti6</literal> ,
<literal > ip6tnl</literal> , and
<literal > erspan</literal> and accepts
2015-02-04 05:14:13 +03:00
the following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Local=</varname> </term>
<listitem >
2019-03-21 19:54:27 +03:00
<para > A static local address for tunneled packets. It must be an address on another interface of
this host, or the special value <literal > any</literal> .</para>
2015-02-04 05:14:13 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Remote=</varname> </term>
<listitem >
2019-03-21 19:54:27 +03:00
<para > The remote endpoint of the tunnel. Takes an IP address or the special value
<literal > any</literal> .</para>
2015-02-04 05:14:13 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > TOS=</varname> </term>
<listitem >
<para > The Type Of Service byte value for a tunnel interface.
2014-08-03 09:11:12 +04:00
For details about the TOS, see the
2015-02-04 05:14:13 +03:00
<ulink url= "http://tools.ietf.org/html/rfc1349" > Type of
Service in the Internet Protocol Suite </ulink> document.
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > TTL=</varname> </term>
<listitem >
<para > A fixed Time To Live N on tunneled packets. N is a
2014-08-03 09:11:12 +04:00
number in the range 1–
2015-02-04 05:14:13 +03:00
packets inherit the TTL value. The default value for IPv4
2014-08-03 09:11:12 +04:00
tunnels is: inherit. The default value for IPv6 tunnels is
2015-02-04 05:14:13 +03:00
64.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > DiscoverPathMTU=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, enables Path MTU Discovery on
2015-02-04 05:14:13 +03:00
the tunnel.</para>
</listitem>
</varlistentry>
2015-07-21 07:37:10 +03:00
<varlistentry >
<term > <varname > IPv6FlowLabel=</varname> </term>
<listitem >
2014-08-03 09:11:37 +04:00
<para > Configures the 20-bit flow label (see <ulink url= "https://tools.ietf.org/html/rfc6437" >
2015-07-21 07:37:10 +03:00
RFC 6437</ulink> ) field in the IPv6 header (see <ulink url= "https://tools.ietf.org/html/rfc2460" >
2014-08-03 09:11:37 +04:00
RFC 2460</ulink> ), which is used by a node to label packets of a flow.
It is only used for IPv6 tunnels.
A flow label of zero is used to indicate packets that have
not been labeled.
It can be configured to a value in the range 0–
set to <literal > inherit</literal> , in which case the original flowlabel is used.</para>
2015-07-21 07:37:10 +03:00
</listitem>
</varlistentry>
2015-07-23 11:08:26 +03:00
<varlistentry >
2015-07-25 05:26:00 +03:00
<term > <varname > CopyDSCP=</varname> </term>
2015-07-23 11:08:26 +03:00
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true, the Differentiated Service Code
2015-07-25 04:57:32 +03:00
Point (DSCP) field will be copied to the inner header from
2015-07-25 05:26:00 +03:00
outer header during the decapsulation of an IPv6 tunnel
2015-07-25 04:57:32 +03:00
packet. DSCP is a field in an IP packet that enables different
levels of service to be assigned to network traffic.
Defaults to <literal > no</literal> .
2015-07-23 11:08:26 +03:00
</para>
</listitem>
</varlistentry>
2015-08-31 10:52:15 +03:00
<varlistentry >
<term > <varname > EncapsulationLimit=</varname> </term>
<listitem >
<para > The Tunnel Encapsulation Limit option specifies how many additional
levels of encapsulation are permitted to be prepended to the packet.
For example, a Tunnel Encapsulation Limit option containing a limit
value of zero means that a packet carrying that option may not enter
another tunnel before exiting the current tunnel.
(see <ulink url= "https://tools.ietf.org/html/rfc2473#section-4.1.1" > RFC 2473</ulink> ).
2014-08-03 09:11:12 +04:00
The valid range is 0– <literal > none</literal> . Defaults to 4.
2015-08-31 10:52:15 +03:00
</para>
</listitem>
</varlistentry>
2016-06-14 20:11:57 +03:00
<varlistentry >
<term > <varname > Key=</varname> </term>
<listitem >
<para > The <varname > Key=</varname> parameter specifies the same key to use in
both directions (<varname > InputKey=</varname> and <varname > OutputKey=</varname> ).
The <varname > Key=</varname> is either a number or an IPv4 address-like dotted quad.
It is used as mark-configured SAD/SPD entry as part of the lookup key (both in data
and control path) in ip xfrm (framework used to implement IPsec protocol).
See <ulink url= "http://man7.org/linux/man-pages/man8/ip-xfrm.8.html" >
2019-03-29 21:49:11 +03:00
ip-xfrm — transform configuration</ulink> for details. It is only used for VTI/VTI6,
GRE, GRETAP, and ERSPAN tunnels.</para>
2016-06-14 20:11:57 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > InputKey=</varname> </term>
<listitem >
<para > The <varname > InputKey=</varname> parameter specifies the key to use for input.
2019-03-29 21:49:11 +03:00
The format is same as <varname > Key=</varname> . It is only used for VTI/VTI6, GRE, GRETAP,
and ERSPAN tunnels.</para>
2016-06-14 20:11:57 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > OutputKey=</varname> </term>
<listitem >
<para > The <varname > OutputKey=</varname> parameter specifies the key to use for output.
2019-03-29 21:49:11 +03:00
The format is same as <varname > Key=</varname> . It is only used for VTI/VTI6, GRE, GRETAP,
and ERSPAN tunnels.</para>
2016-06-14 20:11:57 +03:00
</listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
<varlistentry >
<term > <varname > Mode=</varname> </term>
<listitem >
2014-08-03 09:11:37 +04:00
<para > An <literal > ip6tnl</literal> tunnel can be in one of three
2015-02-04 05:14:13 +03:00
modes
<literal > ip6ip6</literal> for IPv6 over IPv6,
<literal > ipip6</literal> for IPv4 over IPv6 or
<literal > any</literal> for either.
</para>
</listitem>
</varlistentry>
2017-08-31 19:51:03 +03:00
<varlistentry >
<term > <varname > Independent=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true tunnel does not require .network file. Created as "tunnel@NONE".
2017-08-31 19:51:03 +03:00
Defaults to <literal > false</literal> .
</para>
</listitem>
</varlistentry>
2017-12-29 17:19:21 +03:00
<varlistentry >
<term > <varname > AllowLocalRemote=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. When true allows tunnel traffic on <varname > ip6tnl</varname> devices where the remote endpoint is a local host address.
2018-11-27 08:40:25 +03:00
When unset, the kernel's default will be used.
2017-12-29 17:19:21 +03:00
</para>
</listitem>
</varlistentry>
2018-06-03 10:07:41 +03:00
<varlistentry >
<term > <varname > FooOverUDP=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. Specifies whether <varname > FooOverUDP=</varname> tunnel is to be configured.
2019-03-31 10:31:25 +03:00
Defaults to false. This takes effects only for IPIP, SIT, GRE, and GRETAP tunnels.
For more detail information see
2018-06-03 10:07:41 +03:00
<ulink url= "https://lwn.net/Articles/614348" > Foo over UDP</ulink> </para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > FOUDestinationPort=</varname> </term>
<listitem >
2019-02-13 12:22:18 +03:00
<para > This setting specifies the UDP destination port for encapsulation.
2019-03-31 10:31:25 +03:00
This field is mandatory when <varname > FooOverUDP=yes</varname> , and is not set by default.</para>
2018-06-03 10:07:41 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > FOUSourcePort=</varname> </term>
<listitem >
2019-02-13 12:22:18 +03:00
<para > This setting specifies the UDP source port for encapsulation. Defaults to <constant > 0</constant>
— that is, the source port for packets is left to the network stack to decide.</para>
2018-06-03 10:07:41 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Encapsulation=</varname> </term>
<listitem >
2019-03-31 10:31:25 +03:00
<para > Accepts the same key as in the <literal > [FooOverUDP]</literal> section.</para>
2018-06-03 10:07:41 +03:00
</listitem>
</varlistentry>
2018-11-07 08:27:09 +03:00
<varlistentry >
<term > <varname > IPv6RapidDeploymentPrefix=</varname> </term>
<listitem >
<para > Reconfigure the tunnel for <ulink url= "https://tools.ietf.org/html/rfc5569" > IPv6 Rapid
Deployment</ulink> , also known as 6rd. The value is an ISP-specific IPv6 prefix with a non-zero length. Only
applicable to SIT tunnels.</para>
</listitem>
</varlistentry>
2018-12-01 15:51:20 +03:00
<varlistentry >
<term > <varname > ISATAP=</varname> </term>
<listitem >
<para > Takes a boolean. If set, configures the tunnel as Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunnel.
Only applicable to SIT tunnels. When unset, the kernel's default will be used.</para>
</listitem>
</varlistentry>
2018-11-26 14:50:09 +03:00
<varlistentry >
<term > <varname > SerializeTunneledPackets=</varname> </term>
<listitem >
2019-03-29 21:49:11 +03:00
<para > Takes a boolean. If set to yes, then packets are serialized. Only applies for GRE,
GRETAP, and ERSPAN tunnels. When unset, the kernel's default will be used.
2018-11-26 14:50:09 +03:00
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > ERSPANIndex=</varname> </term>
<listitem >
<para > Specifies the ERSPAN index field for the interface, an integer in the range 1-1048575 associated with
the ERSPAN traffic's source port and direction. This field is mandatory.
</para>
</listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
</variablelist>
</refsect1>
2018-06-03 10:07:41 +03:00
<refsect1 >
<title > [FooOverUDP] Section Options</title>
<para > The <literal > [FooOverUDP]</literal> section only applies for
netdevs of kind <literal > fou</literal> and accepts the
following keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Encapsulation=</varname> </term>
<listitem >
<para > Specifies the encapsulation mechanism used to store networking packets of various protocols inside the UDP packets. Supports the following values:
<literal > FooOverUDP</literal> provides the simplest no frills model of UDP encapsulation, it simply encapsulates
packets directly in the UDP payload.
<literal > GenericUDPEncapsulation</literal> is a generic and extensible encapsulation, it allows encapsulation of packets for any IP
protocol and optional data as part of the encapsulation.
For more detailed information see <ulink url= "https://lwn.net/Articles/615044" > Generic UDP Encapsulation</ulink> .
Defaults to <literal > FooOverUDP</literal> .
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Port=</varname> </term>
<listitem >
<para > Specifies the port number, where the IP encapsulation packets will arrive. Please take note that the packets
will arrive with the encapsulation will be removed. Then they will be manually fed back into the network stack, and sent ahead
for delivery to the real destination. This option is mandatory.</para>
</listitem>
</varlistentry>
2019-03-31 10:31:25 +03:00
<varlistentry >
<term > <varname > Protocol=</varname> </term>
<listitem >
<para > The <varname > Protocol=</varname> specifies the protocol number of the packets arriving
at the UDP port. When <varname > Encapsulation=FooOverUDP</varname> , this field is mandatory
and is not set by default. Takes an IP protocol name such as <literal > gre</literal> or
<literal > ipip</literal> , or an integer within the range 1-255. When
<varname > Encapsulation=GenericUDPEncapsulation</varname> , this must not be specified.</para>
</listitem>
</varlistentry>
</variablelist>
2018-06-03 10:07:41 +03:00
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > [Peer] Section Options</title>
<para > The <literal > [Peer]</literal> section only applies for
netdevs of kind <literal > veth</literal> and accepts the
2014-08-03 09:11:37 +04:00
following keys:</para>
2015-02-04 05:14:13 +03:00
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Name=</varname> </term>
<listitem >
<para > The interface name used when creating the netdev.
This option is compulsory.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > MACAddress=</varname> </term>
<listitem >
2014-08-03 09:11:12 +04:00
<para > The peer MACAddress, if not set, it is generated in
2015-02-04 05:14:13 +03:00
the same way as the MAC address of the main
interface.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
2017-11-22 10:23:22 +03:00
<refsect1 >
<title > [VXCAN] Section Options</title>
<para > The <literal > [VXCAN]</literal> section only applies for
netdevs of kind <literal > vxcan</literal> and accepts the
following key:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Peer=</varname> </term>
<listitem >
<para > The peer interface name used when creating the netdev.
This option is compulsory.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > [Tun] Section Options</title>
<para > The <literal > [Tun]</literal> section only applies for
netdevs of kind <literal > tun</literal> , and accepts the following
keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > OneQueue=</varname> </term>
2018-11-27 09:07:58 +03:00
<listitem > <para > Takes a boolean. Configures whether
2015-02-04 05:14:13 +03:00
all packets are queued at the device (enabled), or a fixed
number of packets are queued at the device and the rest at the
<literal > qdisc</literal> . Defaults to
<literal > no</literal> .</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > MultiQueue=</varname> </term>
2018-11-27 09:07:58 +03:00
<listitem > <para > Takes a boolean. Configures whether
2015-02-04 05:14:13 +03:00
to use multiple file descriptors (queues) to parallelize
packets sending and receiving. Defaults to
<literal > no</literal> .</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > PacketInfo=</varname> </term>
2018-11-27 09:07:58 +03:00
<listitem > <para > Takes a boolean. Configures whether
2015-05-11 14:49:29 +03:00
packets should be prepended with four extra bytes (two flag
2014-08-03 09:11:12 +04:00
bytes and two protocol bytes). If disabled, it indicates that
2015-02-04 05:14:13 +03:00
the packets will be pure IP packets. Defaults to
<literal > no</literal> .</para>
</listitem>
</varlistentry>
2015-07-14 18:18:09 +03:00
<varlistentry >
2015-07-27 21:24:31 +03:00
<term > <varname > VNetHeader=</varname> </term>
2018-11-27 09:07:58 +03:00
<listitem > <para > Takes a boolean. Configures
2015-07-14 18:18:09 +03:00
IFF_VNET_HDR flag for a tap device. It allows sending
and receiving larger Generic Segmentation Offload (GSO)
packets. This may increase throughput significantly.
Defaults to
<literal > no</literal> .</para>
</listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
<varlistentry >
<term > <varname > User=</varname> </term>
<listitem > <para > User to grant access to the
<filename > /dev/net/tun</filename> device.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Group=</varname> </term>
<listitem > <para > Group to grant access to the
<filename > /dev/net/tun</filename> device.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > [Tap] Section Options</title>
<para > The <literal > [Tap]</literal> section only applies for
netdevs of kind <literal > tap</literal> , and accepts the same keys
as the <literal > [Tun]</literal> section.</para>
</refsect1>
2017-12-18 17:20:34 +03:00
<refsect1 >
<title > [WireGuard] Section Options</title>
<para > The <literal > [WireGuard]</literal> section accepts the following
keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > PrivateKey=</varname> </term>
<listitem >
<para > The Base64 encoded private key for the interface. It can be
generated using the <command > wg genkey</command> command
(see <citerefentry project= "wireguard" > <refentrytitle > wg</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ).
2019-03-04 08:19:21 +03:00
This option or <varname > PrivateKeyFile=</varname> is mandatory to use WireGuard.
2018-01-29 22:43:30 +03:00
Note that because this information is secret, you may want to set
2018-07-16 21:12:19 +03:00
the permissions of the .netdev file to be owned by <literal > root:systemd-network</literal>
2018-01-29 22:43:30 +03:00
with a <literal > 0640</literal> file mode.</para>
2017-12-18 17:20:34 +03:00
</listitem>
</varlistentry>
2019-03-04 08:19:21 +03:00
<varlistentry >
<term > <varname > PrivateKeyFile=</varname> </term>
<listitem >
2019-04-05 11:33:09 +03:00
<para > Takes an absolute path to a file which contains the Base64 encoded private key for the interface.
2019-04-05 11:28:46 +03:00
When this option is specified, then <varname > PrivateKey=</varname> is ignored.
2019-03-04 08:19:21 +03:00
Note that the file must be readable by the user <literal > systemd-network</literal> , so it
should be, e.g., owned by <literal > root:systemd-network</literal> with a
<literal > 0640</literal> file mode.</para>
</listitem>
</varlistentry>
2017-12-18 17:20:34 +03:00
<varlistentry >
<term > <varname > ListenPort=</varname> </term>
<listitem >
<para > Sets UDP port for listening. Takes either value between 1 and 65535
or <literal > auto</literal> . If <literal > auto</literal> is specified,
the port is automatically generated based on interface name.
Defaults to <literal > auto</literal> .</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > FwMark=</varname> </term>
<listitem >
2018-01-29 22:38:36 +03:00
<para > Sets a firewall mark on outgoing WireGuard packets from this interface.</para>
2017-12-18 17:20:34 +03:00
</listitem>
</varlistentry>
</variablelist>
</refsect1>
<refsect1 >
<title > [WireGuardPeer] Section Options</title>
<para > The <literal > [WireGuardPeer]</literal> section accepts the following
keys:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > PublicKey=</varname> </term>
<listitem >
<para > Sets a Base64 encoded public key calculated by <command > wg pubkey</command>
(see <citerefentry project= "wireguard" > <refentrytitle > wg</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> )
from a private key, and usually transmitted out of band to the
author of the configuration file. This option is mandatory for this
section.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > PresharedKey=</varname> </term>
<listitem >
<para > Optional preshared key for the interface. It can be generated
by the <command > wg genpsk</command> command. This option adds an
additional layer of symmetric-key cryptography to be mixed into the
already existing public-key cryptography, for post-quantum
2018-01-29 22:43:30 +03:00
resistance.
Note that because this information is secret, you may want to set
the permissions of the .netdev file to be owned by <literal > root:systemd-networkd</literal>
with a <literal > 0640</literal> file mode.</para>
2017-12-18 17:20:34 +03:00
</listitem>
</varlistentry>
2019-04-05 11:33:09 +03:00
<varlistentry >
<term > <varname > PresharedKeyFile=</varname> </term>
<listitem >
<para > Takes an absolute path to a file which contains the Base64 encoded preshared key for the
peer. When this option is specified, then <varname > PresharedKey=</varname> is ignored.
Note that the file must be readable by the user <literal > systemd-network</literal> , so it
should be, e.g., owned by <literal > root:systemd-network</literal> with a
<literal > 0640</literal> file mode.</para>
</listitem>
</varlistentry>
2017-12-18 17:20:34 +03:00
<varlistentry >
<term > <varname > AllowedIPs=</varname> </term>
<listitem >
<para > Sets a comma-separated list of IP (v4 or v6) addresses with CIDR masks
from which this peer is allowed to send incoming traffic and to
which outgoing traffic for this peer is directed. The catch-all
0.0.0.0/0 may be specified for matching all IPv4 addresses, and
::/0 may be specified for matching all IPv6 addresses. </para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > Endpoint=</varname> </term>
<listitem >
<para > Sets an endpoint IP address or hostname, followed by a colon, and then
a port number. This endpoint will be updated automatically once to
the most recent source IP address and port of correctly
authenticated packets from the peer at configuration time.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > PersistentKeepalive=</varname> </term>
<listitem >
<para > Sets a seconds interval, between 1 and 65535 inclusive, of how often
to send an authenticated empty packet to the peer for the purpose
of keeping a stateful firewall or NAT mapping valid persistently.
For example, if the interface very rarely sends traffic, but it
might at anytime receive traffic from a peer, and it is behind NAT,
the interface might benefit from having a persistent keepalive
interval of 25 seconds. If set to 0 or "off", this option is
disabled. By default or when unspecified, this option is off.
Most users will not need this.</para>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
2015-02-04 05:14:13 +03:00
<refsect1 >
<title > [Bond] Section Options</title>
<para > The <literal > [Bond]</literal> section accepts the following
key:</para>
<variablelist class= 'network-directives' >
<varlistentry >
<term > <varname > Mode=</varname> </term>
<listitem >
<para > Specifies one of the bonding policies. The default is
<literal > balance-rr</literal> (round robin). Possible values are
<literal > balance-rr</literal> ,
<literal > active-backup</literal> ,
<literal > balance-xor</literal> ,
<literal > broadcast</literal> ,
<literal > 802.3ad</literal> ,
<literal > balance-tlb</literal> , and
<literal > balance-alb</literal> .
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > TransmitHashPolicy=</varname> </term>
<listitem >
<para > Selects the transmit hash policy to use for slave
selection in balance-xor, 802.3ad, and tlb modes. Possible
values are
<literal > layer2</literal> ,
<literal > layer3+4</literal> ,
<literal > layer2+3</literal> ,
2016-07-06 08:42:03 +03:00
<literal > encap2+3</literal> , and
2015-02-04 05:14:13 +03:00
<literal > encap3+4</literal> .
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > LACPTransmitRate=</varname> </term>
<listitem >
<para > Specifies the rate with which link partner transmits
Link Aggregation Control Protocol Data Unit packets in
802.3ad mode. Possible values are <literal > slow</literal> ,
which requests partner to transmit LACPDUs every 30 seconds,
and <literal > fast</literal> , which requests partner to
transmit LACPDUs every second. The default value is
<literal > slow</literal> .</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > MIIMonitorSec=</varname> </term>
<listitem >
<para > Specifies the frequency that Media Independent
Interface link monitoring will occur. A value of zero
2015-07-26 00:15:05 +03:00
disables MII link monitoring. This value is rounded down to
2015-02-04 05:14:13 +03:00
the nearest millisecond. The default value is 0.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > UpDelaySec=</varname> </term>
<listitem >
<para > Specifies the delay before a link is enabled after a
link up status has been detected. This value is rounded down
to a multiple of MIIMonitorSec. The default value is
0.</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > DownDelaySec=</varname> </term>
<listitem >
<para > Specifies the delay before a link is disabled after a
link down status has been detected. This value is rounded
down to a multiple of MIIMonitorSec. The default value is
0.</para>
</listitem>
</varlistentry>
2015-03-09 12:58:29 +03:00
<varlistentry >
2015-04-21 11:04:05 +03:00
<term > <varname > LearnPacketIntervalSec=</varname> </term>
2015-03-09 12:58:29 +03:00
<listitem >
<para > Specifies the number of seconds between instances where the bonding
2014-08-03 09:11:37 +04:00
driver sends learning packets to each slave peer switch.
The valid range is 1–
has an effect only for the balance-tlb and balance-alb modes.</para>
2015-03-09 12:58:29 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > AdSelect=</varname> </term>
<listitem >
<para > Specifies the 802.3ad aggregation selection logic to use. Possible values are
<literal > stable</literal> ,
2014-08-03 09:11:37 +04:00
<literal > bandwidth</literal> and
<literal > count</literal> .
2015-03-09 12:58:29 +03:00
</para>
</listitem>
</varlistentry>
2018-11-02 04:31:20 +03:00
<varlistentry >
2018-11-06 11:55:35 +03:00
<term > <varname > AdActorSystemPriority=</varname> </term>
2018-11-02 04:31:20 +03:00
<listitem >
2018-11-06 11:55:35 +03:00
<para > Specifies the 802.3ad actor system priority. Ranges [1-65535].</para>
2018-11-02 04:31:20 +03:00
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > AdUserPortKey=</varname> </term>
<listitem >
<para > Specifies the 802.3ad user defined portion of the port key. Ranges [0-1023].</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > AdActorSystem=</varname> </term>
<listitem >
<para > Specifies the 802.3ad system mac address. This can not be either NULL or Multicast.</para>
</listitem>
</varlistentry>
2015-03-09 12:58:29 +03:00
<varlistentry >
2015-04-21 11:04:05 +03:00
<term > <varname > FailOverMACPolicy=</varname> </term>
2015-03-09 12:58:29 +03:00
<listitem >
2014-08-03 09:11:37 +04:00
<para > Specifies whether the active-backup mode should set all slaves to
the same MAC address at the time of enslavement or, when enabled, to perform special handling of the
2015-03-09 12:58:29 +03:00
bond's MAC address in accordance with the selected policy. The default policy is none.
Possible values are
<literal > none</literal> ,
2014-08-03 09:11:37 +04:00
<literal > active</literal> and
<literal > follow</literal> .
2015-03-09 12:58:29 +03:00
</para>
</listitem>
</varlistentry>
<varlistentry >
2015-04-21 11:04:05 +03:00
<term > <varname > ARPValidate=</varname> </term>
2015-03-09 12:58:29 +03:00
<listitem >
<para > Specifies whether or not ARP probes and replies should be
2015-04-21 11:04:05 +03:00
validated in any mode that supports ARP monitoring, or whether
2015-03-09 12:58:29 +03:00
non-ARP traffic should be filtered (disregarded) for link
monitoring purposes. Possible values are
<literal > none</literal> ,
<literal > active</literal> ,
2014-08-03 09:11:37 +04:00
<literal > backup</literal> and
<literal > all</literal> .
2015-03-09 12:58:29 +03:00
</para>
</listitem>
</varlistentry>
<varlistentry >
2015-04-21 11:04:05 +03:00
<term > <varname > ARPIntervalSec=</varname> </term>
2015-03-09 12:58:29 +03:00
<listitem >
<para > Specifies the ARP link monitoring frequency in milliseconds.
A value of 0 disables ARP monitoring. The default value is 0.
</para>
</listitem>
</varlistentry>
<varlistentry >
2015-04-21 11:04:05 +03:00
<term > <varname > ARPIPTargets=</varname> </term>
2015-03-09 12:58:29 +03:00
<listitem >
<para > Specifies the IP addresses to use as ARP monitoring peers when
2015-04-21 11:04:05 +03:00
ARPIntervalSec is greater than 0. These are the targets of the ARP request
2015-03-09 12:58:29 +03:00
sent to determine the health of the link to the targets.
2014-08-03 09:11:37 +04:00
Specify these values in IPv4 dotted decimal format. At least one IP
2015-03-09 12:58:29 +03:00
address must be given for ARP monitoring to function. The
maximum number of targets that can be specified is 16. The
default value is no IP addresses.
</para>
</listitem>
</varlistentry>
<varlistentry >
2015-04-21 11:04:05 +03:00
<term > <varname > ARPAllTargets=</varname> </term>
2015-03-09 12:58:29 +03:00
<listitem >
2015-04-21 11:04:05 +03:00
<para > Specifies the quantity of ARPIPTargets that must be reachable
2015-03-09 12:58:29 +03:00
in order for the ARP monitor to consider a slave as being up.
This option affects only active-backup mode for slaves with
2015-04-21 11:04:05 +03:00
ARPValidate enabled. Possible values are
2014-08-03 09:11:37 +04:00
<literal > any</literal> and
<literal > all</literal> .
2015-03-09 12:58:29 +03:00
</para>
</listitem>
</varlistentry>
<varlistentry >
2015-04-21 11:04:05 +03:00
<term > <varname > PrimaryReselectPolicy=</varname> </term>
2015-03-09 12:58:29 +03:00
<listitem >
<para > Specifies the reselection policy for the primary slave. This
affects how the primary slave is chosen to become the active slave
when failure of the active slave or recovery of the primary slave
occurs. This option is designed to prevent flip-flopping between
the primary slave and other slaves. Possible values are
<literal > always</literal> ,
2014-08-03 09:11:37 +04:00
<literal > better</literal> and
<literal > failure</literal> .
2015-03-09 12:58:29 +03:00
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > ResendIGMP=</varname> </term>
<listitem >
<para > Specifies the number of IGMP membership reports to be issued after
a failover event. One membership report is issued immediately after
the failover, subsequent packets are sent in each 200ms interval.
2014-08-03 09:11:12 +04:00
The valid range is 0–
2015-03-09 12:58:29 +03:00
prevents the IGMP membership report from being issued in response
to the failover event.
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > PacketsPerSlave=</varname> </term>
<listitem >
2014-08-03 09:11:12 +04:00
<para > Specify the number of packets to transmit through a slave before
moving to the next one. When set to 0, then a slave is chosen at
random. The valid range is 0–
2014-08-03 09:11:37 +04:00
only has effect when in balance-rr mode.
2015-03-09 12:58:29 +03:00
</para>
</listitem>
</varlistentry>
<varlistentry >
2015-04-21 11:04:05 +03:00
<term > <varname > GratuitousARP=</varname> </term>
2015-03-09 12:58:29 +03:00
<listitem >
<para > Specify the number of peer notifications (gratuitous ARPs and
unsolicited IPv6 Neighbor Advertisements) to be issued after a
2014-08-03 09:11:12 +04:00
failover event. As soon as the link is up on the new slave,
2015-03-09 12:58:29 +03:00
a peer notification is sent on the bonding device and each
VLAN sub-device. This is repeated at each link monitor interval
2015-04-21 11:04:05 +03:00
(ARPIntervalSec or MIIMonitorSec, whichever is active) if the number is
2014-08-03 09:11:37 +04:00
greater than 1. The valid range is 0–
2015-04-21 11:04:05 +03:00
These options affect only the active-backup mode.
2015-03-09 12:58:29 +03:00
</para>
</listitem>
</varlistentry>
<varlistentry >
<term > <varname > AllSlavesActive=</varname> </term>
<listitem >
2018-11-27 09:07:58 +03:00
<para > Takes a boolean. Specifies that duplicate frames (received on inactive ports)
2014-08-03 09:11:37 +04:00
should be dropped when false, or delivered when true. Normally, bonding will drop
2015-03-09 12:58:29 +03:00
duplicate frames (received on inactive ports), which is desirable for
most users. But there are some times it is nice to allow duplicate
frames to be delivered. The default value is false (drop duplicate frames
received on inactive ports).
</para>
</listitem>
</varlistentry>
2018-12-13 12:23:07 +03:00
<varlistentry >
<term > <varname > DynamicTransmitLoadBalancing=</varname> </term>
<listitem >
<para > Takes a boolean. Specifies if dynamic shuffling of flows is enabled. Applies only
for balance-tlb mode. Defaults to unset.
</para>
</listitem>
</varlistentry>
2015-03-09 12:58:29 +03:00
<varlistentry >
<term > <varname > MinLinks=</varname> </term>
<listitem >
<para > Specifies the minimum number of links that must be active before
asserting carrier. The default value is 0.
</para>
</listitem>
</varlistentry>
2015-02-04 05:14:13 +03:00
</variablelist>
2015-03-09 12:58:29 +03:00
<para > For more detail information see
<ulink url= "https://www.kernel.org/doc/Documentation/networking/bonding.txt" >
Linux Ethernet Bonding Driver HOWTO</ulink> </para>
2015-02-04 05:14:13 +03:00
</refsect1>
<refsect1 >
2018-06-25 19:43:33 +03:00
<title > Examples</title>
2015-02-04 05:14:13 +03:00
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-bridge.netdev</title>
2015-02-04 05:14:13 +03:00
<programlisting > [NetDev]
2014-02-25 22:30:40 +04:00
Name=bridge0
Kind=bridge</programlisting>
2015-02-04 05:14:13 +03:00
</example>
2014-02-25 22:30:40 +04:00
2015-02-04 05:14:13 +03:00
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-vlan1.netdev</title>
2014-02-25 22:30:40 +04:00
2015-02-04 05:14:13 +03:00
<programlisting > [Match]
2014-02-25 22:30:40 +04:00
Virtualization=no
[NetDev]
Name=vlan1
Kind=vlan
[VLAN]
Id=1</programlisting>
2015-02-04 05:14:13 +03:00
</example>
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-ipip.netdev</title>
2015-02-04 05:14:13 +03:00
<programlisting > [NetDev]
2014-07-01 23:38:08 +04:00
Name=ipip-tun
Kind=ipip
MTUBytes=1480
[Tunnel]
Local=192.168.223.238
Remote=192.169.224.239
TTL=64</programlisting>
2015-02-04 05:14:13 +03:00
</example>
2018-06-03 10:07:41 +03:00
<example >
<title > /etc/systemd/network/1-fou-tunnel.netdev</title>
<programlisting > [NetDev]
Name=fou-tun
Kind=fou
[FooOverUDP]
Port=5555
Protocol=4
</programlisting>
</example>
<example >
<title > /etc/systemd/network/25-fou-ipip.netdev</title>
<programlisting > [NetDev]
Name=ipip-tun
Kind=ipip
[Tunnel]
2018-09-25 13:40:35 +03:00
Independent=yes
2018-06-03 10:07:41 +03:00
Local=10.65.208.212
Remote=10.65.208.211
2018-09-25 13:40:35 +03:00
FooOverUDP=yes
2018-06-03 10:07:41 +03:00
FOUDestinationPort=5555
</programlisting>
</example>
2015-02-04 05:14:13 +03:00
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-tap.netdev</title>
2015-02-04 05:14:13 +03:00
<programlisting > [NetDev]
2014-07-03 12:04:11 +04:00
Name=tap-test
Kind=tap
[Tap]
2018-09-25 13:40:35 +03:00
MultiQueue=yes
PacketInfo=yes</programlisting> </example>
2014-02-25 22:30:40 +04:00
2015-02-04 05:14:13 +03:00
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-sit.netdev</title>
2015-02-04 05:14:13 +03:00
<programlisting > [NetDev]
2014-07-01 23:38:08 +04:00
Name=sit-tun
Kind=sit
MTUBytes=1480
[Tunnel]
Local=10.65.223.238
Remote=10.65.223.239</programlisting>
2015-02-04 05:14:13 +03:00
</example>
2014-02-25 22:30:40 +04:00
2018-11-07 08:27:09 +03:00
<example >
<title > /etc/systemd/network/25-6rd.netdev</title>
<programlisting > [NetDev]
Name=6rd-tun
Kind=sit
MTUBytes=1480
[Tunnel]
Local=10.65.223.238
IPv6RapidDeploymentPrefix=2602::/24</programlisting>
</example>
2015-02-04 05:14:13 +03:00
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-gre.netdev</title>
2015-02-04 05:14:13 +03:00
<programlisting > [NetDev]
2014-07-01 23:38:08 +04:00
Name=gre-tun
Kind=gre
MTUBytes=1480
[Tunnel]
Local=10.65.223.238
Remote=10.65.223.239</programlisting>
2015-02-04 05:14:13 +03:00
</example>
2014-07-01 23:38:08 +04:00
2015-02-04 05:14:13 +03:00
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-vti.netdev</title>
2014-07-01 23:38:08 +04:00
2015-02-04 05:14:13 +03:00
<programlisting > [NetDev]
2014-07-01 23:38:08 +04:00
Name=vti-tun
Kind=vti
MTUBytes=1480
[Tunnel]
Local=10.65.223.238
Remote=10.65.223.239</programlisting>
2015-02-04 05:14:13 +03:00
</example>
2014-07-01 23:38:08 +04:00
2015-02-04 05:14:13 +03:00
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-veth.netdev</title>
2015-02-04 05:14:13 +03:00
<programlisting > [NetDev]
2014-07-01 23:38:08 +04:00
Name=veth-test
Kind=veth
[Peer]
Name=veth-peer</programlisting>
2015-02-04 05:14:13 +03:00
</example>
2014-07-01 23:38:08 +04:00
2015-08-21 06:14:49 +03:00
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-bond.netdev</title>
2015-08-21 06:14:49 +03:00
<programlisting > [NetDev]
Name=bond1
Kind=bond
[Bond]
Mode=802.3ad
TransmitHashPolicy=layer3+4
MIIMonitorSec=1s
LACPTransmitRate=fast
</programlisting>
</example>
2015-02-04 05:14:13 +03:00
<example >
2015-10-03 12:54:43 +03:00
<title > /etc/systemd/network/25-dummy.netdev</title>
2015-02-04 05:14:13 +03:00
<programlisting > [NetDev]
2014-07-01 21:45:37 +04:00
Name=dummy-test
Kind=dummy
MACAddress=12:34:56:78:9a:bc</programlisting>
2015-02-04 05:14:13 +03:00
</example>
2016-06-10 02:57:51 +03:00
<example >
<title > /etc/systemd/network/25-vrf.netdev</title>
2016-07-12 12:58:14 +03:00
<para > Create a VRF interface with table 42.</para>
2016-06-10 02:57:51 +03:00
<programlisting > [NetDev]
Name=vrf-test
Kind=vrf
2015-02-04 05:14:13 +03:00
2016-06-10 02:57:51 +03:00
[VRF]
2017-08-31 02:44:29 +03:00
Table=42</programlisting>
2016-06-10 02:57:51 +03:00
</example>
2016-12-23 20:09:29 +03:00
<example >
<title > /etc/systemd/network/25-macvtap.netdev</title>
<para > Create a MacVTap device.</para>
<programlisting > [NetDev]
Name=macvtap-test
Kind=macvtap
</programlisting>
</example>
2017-12-18 17:20:34 +03:00
<example >
<title > /etc/systemd/network/25-wireguard.netdev</title>
<programlisting > [NetDev]
Name=wg0
Kind=wireguard
[WireGuard]
PrivateKey=EEGlnEPYJV//kbvvIqxKkQwOiS+UENyPncC4bF46ong=
ListenPort=51820
[WireGuardPeer]
PublicKey=RDf+LSpeEre7YEIKaxg+wbpsNV7du+ktR99uBEtIiCA=
AllowedIPs=fd31:bf08:57cb::/48,192.168.26.0/24
Endpoint=wireguard.example.com:51820</programlisting>
</example>
2015-02-04 05:14:13 +03:00
</refsect1>
<refsect1 >
<title > See Also</title>
<para >
<citerefentry > <refentrytitle > systemd</refentrytitle> <manvolnum > 1</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd-networkd</refentrytitle> <manvolnum > 8</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.link</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry> ,
<citerefentry > <refentrytitle > systemd.network</refentrytitle> <manvolnum > 5</manvolnum> </citerefentry>
</para>
</refsect1>
2014-02-25 22:30:40 +04:00
</refentry>
