1 <?xml version='
1.0'
?> <!--*-nxml-*-->
2 <!DOCTYPE refentry PUBLIC
"-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
4 <!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
6 <refentry id=
"systemd.netdev" conditional='ENABLE_NETWORKD'
7 xmlns:
xi=
"http://www.w3.org/2001/XInclude">
10 <title>systemd.network
</title>
11 <productname>systemd
</productname>
15 <refentrytitle>systemd.netdev
</refentrytitle>
16 <manvolnum>5</manvolnum>
20 <refname>systemd.netdev
</refname>
21 <refpurpose>Virtual Network Device configuration
</refpurpose>
25 <para><filename><replaceable>netdev
</replaceable>.netdev
</filename></para>
29 <title>Description
</title>
31 <para>A plain ini-style text file that encodes configuration about a virtual network device, used by
32 <citerefentry><refentrytitle>systemd-networkd
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
33 See
<citerefentry><refentrytitle>systemd.syntax
</refentrytitle><manvolnum>7</manvolnum></citerefentry>
34 for a general description of the syntax.
</para>
36 <para>The main Virtual Network Device file must have the extension
<filename>.netdev
</filename>;
37 other extensions are ignored. Virtual network devices are created as soon as networkd is
38 started. If a netdev with the specified name already exists, networkd will use that as-is rather
39 than create its own. Note that the settings of the pre-existing netdev will not be changed by
42 <para>The
<filename>.netdev
</filename> files are read from the files located in the system
43 network directory
<filename>/usr/lib/systemd/network
</filename>, the volatile runtime network
44 directory
<filename>/run/systemd/network
</filename> and the local administration network
45 directory
<filename>/etc/systemd/network
</filename>. All configuration files are collectively
46 sorted and processed in lexical order, regardless of the directories in which they live.
47 However, files with identical filenames replace each other. Files in
<filename>/etc/
</filename>
48 have the highest priority, files in
<filename>/run/
</filename> take precedence over files with
49 the same name in
<filename>/usr/lib/
</filename>. This can be used to override a system-supplied
50 configuration file with a local file if needed. As a special case, an empty file (file size
0)
51 or symlink with the same name pointing to
<filename>/dev/null
</filename> disables the
52 configuration file entirely (it is
"masked").
</para>
54 <para>Along with the netdev file
<filename>foo.netdev
</filename>, a
"drop-in" directory
55 <filename>foo.netdev.d/
</filename> may exist. All files with the suffix
<literal>.conf
</literal>
56 from this directory will be merged in the alphanumeric order and parsed after the main file itself
57 has been parsed. This is useful to alter or add configuration settings, without having to modify
58 the main configuration file. Each drop-in file must have appropriate section headers.
</para>
60 <para>In addition to
<filename>/etc/systemd/network
</filename>, drop-in
<literal>.d
</literal>
61 directories can be placed in
<filename>/usr/lib/systemd/network
</filename> or
62 <filename>/run/systemd/network
</filename> directories. Drop-in files in
63 <filename>/etc/
</filename> take precedence over those in
<filename>/run/
</filename> which in turn
64 take precedence over those in
<filename>/usr/lib/
</filename>. Drop-in files under any of these
65 directories take precedence over the main netdev file wherever located. (Of course, since
66 <filename>/run/
</filename> is temporary and
<filename>/usr/lib/
</filename> is for vendors, it is
67 unlikely drop-ins should be used in either of those places.)
</para>
71 <title>Supported netdev kinds
</title>
73 <para>The following kinds of virtual network devices may be
74 configured in
<filename>.netdev
</filename> files:
</para>
77 <title>Supported kinds of virtual network devices
</title>
80 <colspec colname='kind'
/>
81 <colspec colname='explanation'
/>
84 <entry>Description
</entry>
87 <row><entry><varname>bond
</varname></entry>
88 <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.
</entry></row>
90 <row><entry><varname>bridge
</varname></entry>
91 <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>
93 <row><entry><varname>dummy
</varname></entry>
94 <entry>A dummy device drops all packets sent to it.
</entry></row>
96 <row><entry><varname>gre
</varname></entry>
97 <entry>A Level
3 GRE tunnel over IPv4. See
<ulink url=
"https://tools.ietf.org/html/rfc2784">RFC
2784</ulink> for details. Name
<literal>gre0
</literal> should not be used, as the kernel creates a device with this name when the corresponding kernel module is loaded.
</entry></row>
99 <row><entry><varname>gretap
</varname></entry>
100 <entry>A Level
2 GRE tunnel over IPv4. Name
<literal>gretap0
</literal> should not be used, as the kernel creates a device with this name when the corresponding kernel module is loaded.
</entry></row>
102 <row><entry><varname>erspan
</varname></entry>
103 <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. Name
<literal>erspan0
</literal> should not be used, as the kernel creates a device with this name when the corresponding kernel module is loaded.
</entry></row>
105 <row><entry><varname>ip6gre
</varname></entry>
106 <entry>A Level
3 GRE tunnel over IPv6.
</entry></row>
108 <row><entry><varname>ip6tnl
</varname></entry>
109 <entry>An IPv4 or IPv6 tunnel over IPv6
</entry></row>
111 <row><entry><varname>ip6gretap
</varname></entry>
112 <entry>A Level
2 GRE tunnel over IPv6.
</entry></row>
114 <row><entry><varname>ipip
</varname></entry>
115 <entry>An IPv4 over IPv4 tunnel.
</entry></row>
117 <row><entry><varname>ipvlan
</varname></entry>
118 <entry>An IPVLAN device is a stacked device which receives packets from its underlying device based on IP address filtering.
</entry></row>
120 <row><entry><varname>ipvtap
</varname></entry>
121 <entry>An IPVTAP device is a stacked device which receives packets from its underlying device based on IP address filtering and can be accessed using the tap user space interface.
</entry></row>
123 <row><entry><varname>macvlan
</varname></entry>
124 <entry>A macvlan device is a stacked device which receives packets from its underlying device based on MAC address filtering.
</entry></row>
126 <row><entry><varname>macvtap
</varname></entry>
127 <entry>A macvtap device is a stacked device which receives packets from its underlying device based on MAC address filtering.
</entry></row>
129 <row><entry><varname>sit
</varname></entry>
130 <entry>An IPv6 over IPv4 tunnel.
</entry></row>
132 <row><entry><varname>tap
</varname></entry>
133 <entry>A persistent Level
2 tunnel between a network device and a device node.
</entry></row>
135 <row><entry><varname>tun
</varname></entry>
136 <entry>A persistent Level
3 tunnel between a network device and a device node.
</entry></row>
138 <row><entry><varname>veth
</varname></entry>
139 <entry>An Ethernet tunnel between a pair of network devices.
</entry></row>
141 <row><entry><varname>vlan
</varname></entry>
142 <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>
144 <row><entry><varname>vti
</varname></entry>
145 <entry>An IPv4 over IPSec tunnel.
</entry></row>
147 <row><entry><varname>vti6
</varname></entry>
148 <entry>An IPv6 over IPSec tunnel.
</entry></row>
150 <row><entry><varname>vxlan
</varname></entry>
151 <entry>A virtual extensible LAN (vxlan), for connecting Cloud computing deployments.
</entry></row>
153 <row><entry><varname>geneve
</varname></entry>
154 <entry>A GEneric NEtwork Virtualization Encapsulation (GENEVE) netdev driver.
</entry></row>
156 <row><entry><varname>l2tp
</varname></entry>
157 <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>
159 <row><entry><varname>macsec
</varname></entry>
160 <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>
162 <row><entry><varname>vrf
</varname></entry>
163 <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>
165 <row><entry><varname>vcan
</varname></entry>
166 <entry>The virtual CAN driver (vcan). Similar to the network loopback devices, vcan offers a virtual local CAN interface.
</entry></row>
168 <row><entry><varname>vxcan
</varname></entry>
169 <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.
172 <row><entry><varname>wireguard
</varname></entry>
173 <entry>WireGuard Secure Network Tunnel.
</entry></row>
175 <row><entry><varname>nlmon
</varname></entry>
176 <entry>A Netlink monitor device. Use an nlmon device when you want to monitor system Netlink messages.
</entry></row>
178 <row><entry><varname>fou
</varname></entry>
179 <entry>Foo-over-UDP tunneling.
</entry></row>
181 <row><entry><varname>xfrm
</varname></entry>
182 <entry>A virtual tunnel interface like vti/vti6 but with several advantages.
</entry></row>
184 <row><entry><varname>ifb
</varname></entry>
185 <entry>The Intermediate Functional Block (ifb) pseudo network interface acts as a QoS concentrator for multiple different sources of traffic.
</entry></row>
187 <row><entry><varname>bareudp
</varname></entry>
188 <entry>Bare UDP tunnels provide a generic L3 encapsulation support for tunnelling different L3 protocols like MPLS, IP etc. inside of an UDP tunnel.
</entry></row>
190 <row><entry><varname>batadv
</varname></entry>
191 <entry><ulink url=
"https://www.open-mesh.org/projects/open-mesh/wiki">B.A.T.M.A.N. Advanced
</ulink> is a routing protocol for multi-hop mobile ad-hoc networks which operates on layer
2.
</entry></row>
193 <row><entry><varname>ipoib
</varname></entry>
194 <entry>An IP over Infiniband subinterface.
</entry></row>
202 <title>[Match] Section Options
</title>
204 <para>A virtual network device is only created if the [Match] section matches the current
205 environment, or if the section is empty. The following keys are accepted:
</para>
207 <variablelist class='network-directives'
>
208 <xi:include href=
"systemd.link.xml" xpointer=
"host" />
209 <xi:include href=
"systemd.link.xml" xpointer=
"virtualization" />
210 <xi:include href=
"systemd.link.xml" xpointer=
"kernel-command-line" />
211 <xi:include href=
"systemd.link.xml" xpointer=
"kernel-version" />
212 <xi:include href=
"systemd.link.xml" xpointer=
"architecture" />
213 <xi:include href=
"systemd.link.xml" xpointer=
"firmware" />
218 <title>[NetDev] Section Options
</title>
220 <para>The [NetDev] section accepts the
221 following keys:
</para>
223 <variablelist class='network-directives'
>
225 <term><varname>Description=
</varname></term>
227 <para>A free-form description of the netdev.
</para>
231 <term><varname>Name=
</varname></term>
233 <para>The interface name used when creating the netdev.
234 This setting is compulsory.
</para>
238 <term><varname>Kind=
</varname></term>
240 <para>The netdev kind. This setting is compulsory. See the
241 <literal>Supported netdev kinds
</literal> section for the
246 <term><varname>MTUBytes=
</varname></term>
248 <para>The maximum transmission unit in bytes to set for the device. The usual suffixes K, M, G
249 are supported and are understood to the base of
1024. For
<literal>tun
</literal> or
250 <literal>tap
</literal> devices,
<varname>MTUBytes=
</varname> setting is not currently supported in
251 [NetDev] section. Please specify it in [Link] section of
253 <citerefentry><refentrytitle>systemd.network
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
258 <term><varname>MACAddress=
</varname></term>
260 <para>Specifies the MAC address to use for the device, or takes the special value
261 <literal>none
</literal>. When
<literal>none
</literal>,
<command>systemd-networkd
</command>
262 does not request the MAC address for the device, and the kernel will assign a random MAC
263 address. For
<literal>tun
</literal>,
<literal>tap
</literal>, or
<literal>l2tp
</literal>
264 devices, the
<varname>MACAddress=
</varname> setting in the [NetDev] section is not
265 supported and will be ignored. Please specify it in the [Link] section of the corresponding
266 <citerefentry><refentrytitle>systemd.network
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
267 file. If this option is not set,
<literal>vlan
</literal> device inherits the MAC address of
268 the master interface. For other kind of netdevs, if this option is not set, then the MAC
269 address is generated based on the interface name and the
270 <citerefentry><refentrytitle>machine-id
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
272 <para>Note, even if
<literal>none
</literal> is specified,
<command>systemd-udevd
</command>
273 will assign the persistent MAC address for the device, as
<filename>99-default.link
</filename>
274 has
<varname>MACAddressPolicy=persistent
</varname>. So, it is also necessary to create a
275 custom .link file for the device, if the MAC address assignment is not desired.
</para>
282 <title>[Bridge] Section Options
</title>
284 <para>The [Bridge] section only applies for
285 netdevs of kind
<literal>bridge
</literal>, and accepts the
286 following keys:
</para>
288 <variablelist class='network-directives'
>
290 <term><varname>HelloTimeSec=
</varname></term>
292 <para>HelloTimeSec specifies the number of seconds between two hello packets
293 sent out by the root bridge and the designated bridges. Hello packets are
294 used to communicate information about the topology throughout the entire
295 bridged local area network.
</para>
299 <term><varname>MaxAgeSec=
</varname></term>
301 <para>MaxAgeSec specifies the number of seconds of maximum message age.
302 If the last seen (received) hello packet is more than this number of
303 seconds old, the bridge in question will start the takeover procedure
304 in attempt to become the Root Bridge itself.
</para>
308 <term><varname>ForwardDelaySec=
</varname></term>
310 <para>ForwardDelaySec specifies the number of seconds spent in each
311 of the Listening and Learning states before the Forwarding state is entered.
</para>
315 <term><varname>AgeingTimeSec=
</varname></term>
317 <para>This specifies the number of seconds a MAC Address will be kept in
318 the forwarding database after having a packet received from this MAC Address.
</para>
322 <term><varname>Priority=
</varname></term>
324 <para>The priority of the bridge. An integer between
0 and
65535. A lower value
325 means higher priority. The bridge having the lowest priority will be elected as root bridge.
</para>
329 <term><varname>GroupForwardMask=
</varname></term>
331 <para>A
16-bit bitmask represented as an integer which allows forwarding of link
332 local frames with
802.1D reserved addresses (
01:
80:C2:
00:
00:
0X). A logical AND
333 is performed between the specified bitmask and the exponentiation of
2^X, the
334 lower nibble of the last octet of the MAC address. For example, a value of
8
335 would allow forwarding of frames addressed to
01:
80:C2:
00:
00:
03 (
802.1X PAE).
</para>
339 <term><varname>DefaultPVID=
</varname></term>
341 <para>This specifies the default port VLAN ID of a newly attached bridge port.
342 Set this to an integer in the range
1…
4094 or
<literal>none
</literal> to disable the PVID.
</para>
346 <term><varname>MulticastQuerier=
</varname></term>
348 <para>Takes a boolean. This setting controls the IFLA_BR_MCAST_QUERIER option in the kernel.
349 If enabled, the kernel will send general ICMP queries from a zero source address.
350 This feature should allow faster convergence on startup, but it causes some
351 multicast-aware switches to misbehave and disrupt forwarding of multicast packets.
352 When unset, the kernel's default will be used.
357 <term><varname>MulticastSnooping=
</varname></term>
359 <para>Takes a boolean. This setting controls the IFLA_BR_MCAST_SNOOPING option in the kernel.
360 If enabled, IGMP snooping monitors the Internet Group Management Protocol (IGMP) traffic
361 between hosts and multicast routers. When unset, the kernel's default will be used.
366 <term><varname>VLANFiltering=
</varname></term>
368 <para>Takes a boolean. This setting controls the IFLA_BR_VLAN_FILTERING option in the kernel.
369 If enabled, the bridge will be started in VLAN-filtering mode. When unset, the kernel's default will be used.
374 <term><varname>VLANProtocol=
</varname></term>
376 <para>Allows setting the protocol used for VLAN filtering. Takes
377 <option>802.1q
</option> or,
378 <option>802.1ad
</option>, and defaults to unset and kernel's default is used.
383 <term><varname>STP=
</varname></term>
385 <para>Takes a boolean. This enables the bridge's Spanning Tree Protocol (STP).
386 When unset, the kernel's default will be used.
391 <term><varname>MulticastIGMPVersion=
</varname></term>
393 <para>Allows changing bridge's multicast Internet Group Management Protocol (IGMP) version.
394 Takes an integer
2 or
3. When unset, the kernel's default will be used.
402 <title>[VLAN] Section Options
</title>
404 <para>The [VLAN] section only applies for
405 netdevs of kind
<literal>vlan
</literal>, and accepts the
406 following key:
</para>
408 <variablelist class='network-directives'
>
410 <term><varname>Id=
</varname></term>
412 <para>The VLAN ID to use. An integer in the range
0…
4094.
413 This setting is compulsory.
</para>
417 <term><varname>Protocol=
</varname></term>
419 <para>Allows setting the protocol used for the VLAN interface. Takes
<literal>802.1q
</literal> or,
420 <literal>802.1ad
</literal>, and defaults to unset and kernel's default is used.
</para>
424 <term><varname>GVRP=
</varname></term>
426 <para>Takes a boolean. The Generic VLAN Registration Protocol (GVRP) is a protocol that
427 allows automatic learning of VLANs on a network.
428 When unset, the kernel's default will be used.
433 <term><varname>MVRP=
</varname></term>
435 <para>Takes a boolean. Multiple VLAN Registration Protocol (MVRP) formerly known as GARP VLAN
436 Registration Protocol (GVRP) is a standards-based Layer
2 network protocol,
437 for automatic configuration of VLAN information on switches. It was defined
438 in the
802.1ak amendment to
802.1Q-
2005. When unset, the kernel's default will be used.
443 <term><varname>LooseBinding=
</varname></term>
445 <para>Takes a boolean. The VLAN loose binding mode, in which only the operational state is passed
446 from the parent to the associated VLANs, but the VLAN device state is not changed.
447 When unset, the kernel's default will be used.
</para>
451 <term><varname>ReorderHeader=
</varname></term>
453 <para>Takes a boolean. When enabled, the VLAN reorder header is used and VLAN interfaces behave
454 like physical interfaces. When unset, the kernel's default will be used.
</para>
458 <term><varname>EgressQOSMaps=
</varname></term>
459 <term><varname>IngressQOSMaps=
</varname></term>
461 <para>Defines a mapping of Linux internal packet priority (
<constant>SO_PRIORITY
</constant>)
462 to VLAN header PCP field for outgoing and incoming frames, respectively. Takes a
463 whitespace-separated list of integer pairs, where each integer must be in the range
464 1…
4294967294, in the format
<literal>from
</literal>-
<literal>to
</literal>, e.g.,
465 <literal>21-
7 45-
5</literal>. Note that
<literal>from
</literal> must be greater than or equal
466 to
<literal>to
</literal>. When unset, the kernel's default will be used.
</para>
473 <title>[MACVLAN] Section Options
</title>
475 <para>The [MACVLAN] section only applies for
476 netdevs of kind
<literal>macvlan
</literal>, and accepts the
477 following key:
</para>
479 <variablelist class='network-directives'
>
481 <term><varname>Mode=
</varname></term>
483 <para>The MACVLAN mode to use. The supported options are
484 <literal>private
</literal>,
485 <literal>vepa
</literal>,
486 <literal>bridge
</literal>,
487 <literal>passthru
</literal>, and
488 <literal>source
</literal>.
493 <term><varname>SourceMACAddress=
</varname></term>
495 <para>A whitespace-separated list of remote hardware addresses allowed on the MACVLAN. This
496 option only has an effect in source mode. Use full colon-, hyphen- or dot-delimited
497 hexadecimal. This option may appear more than once, in which case the lists are merged. If
498 the empty string is assigned to this option, the list of hardware addresses defined prior
499 to this is reset. Defaults to unset.
</para>
503 <term><varname>BroadcastMulticastQueueLength=
</varname></term>
505 <para>Specifies the length of the receive queue for broadcast/multicast packets. An unsigned
506 integer in the range
0…
4294967294. Defaults to unset.
</para>
513 <title>[MACVTAP] Section Options
</title>
515 <para>The [MACVTAP] section applies for netdevs of kind
<literal>macvtap
</literal> and accepts the same
516 keys as [MACVLAN].
</para>
520 <title>[IPVLAN] Section Options
</title>
522 <para>The [IPVLAN] section only applies for
523 netdevs of kind
<literal>ipvlan
</literal>, and accepts the
524 following key:
</para>
526 <variablelist class='network-directives'
>
528 <term><varname>Mode=
</varname></term>
530 <para>The IPVLAN mode to use. The supported options are
531 <literal>L2
</literal>,
<literal>L3
</literal> and
<literal>L3S
</literal>.
536 <term><varname>Flags=
</varname></term>
538 <para>The IPVLAN flags to use. The supported options are
539 <literal>bridge
</literal>,
<literal>private
</literal> and
<literal>vepa
</literal>.
547 <title>[IPVTAP] Section Options
</title>
549 <para>The [IPVTAP] section only applies for netdevs of kind
<literal>ipvtap
</literal> and accepts the
550 same keys as [IPVLAN].
</para>
554 <title>[VXLAN] Section Options
</title>
556 <para>The [VXLAN] section only applies for
557 netdevs of kind
<literal>vxlan
</literal>, and accepts the
558 following keys:
</para>
560 <variablelist class='network-directives'
>
562 <term><varname>VNI=
</varname></term>
564 <para>The VXLAN Network Identifier (or VXLAN Segment ID). Takes a number in the range
1…
16777215.
</para>
568 <term><varname>Remote=
</varname></term>
570 <para>Configures destination IP address.
</para>
574 <term><varname>Local=
</varname></term>
576 <para>Configures local IP address. It must be an address on the underlying interface of the
577 VXLAN interface, or one of the special values
<literal>ipv4_link_local
</literal>,
578 <literal>ipv6_link_local
</literal>,
<literal>dhcp4
</literal>,
<literal>dhcp6
</literal>, and
579 <literal>slaac
</literal>. If one of the special values is specified, an address which matches
580 the corresponding type on the underlying interface will be used. Defaults to unset.
</para>
584 <term><varname>Group=
</varname></term>
586 <para>Configures VXLAN multicast group IP address. All members of a VXLAN must use the same
587 multicast group address.
</para>
591 <term><varname>TOS=
</varname></term>
593 <para>The Type Of Service byte value for a vxlan interface.
</para>
597 <term><varname>TTL=
</varname></term>
599 <para>A fixed Time To Live N on Virtual eXtensible Local Area Network packets.
600 Takes
<literal>inherit
</literal> or a number in the range
0…
255.
0 is a special
601 value meaning inherit the inner protocol's TTL value.
<literal>inherit
</literal>
602 means that it will inherit the outer protocol's TTL value.
</para>
606 <term><varname>MacLearning=
</varname></term>
608 <para>Takes a boolean. When true, enables dynamic MAC learning
609 to discover remote MAC addresses.
</para>
613 <term><varname>FDBAgeingSec=
</varname></term>
615 <para>The lifetime of Forwarding Database entry learnt by
616 the kernel, in seconds.
</para>
620 <term><varname>MaximumFDBEntries=
</varname></term>
622 <para>Configures maximum number of FDB entries.
</para>
626 <term><varname>ReduceARPProxy=
</varname></term>
628 <para>Takes a boolean. When true, bridge-connected VXLAN tunnel
629 endpoint answers ARP requests from the local bridge on behalf
630 of remote Distributed Overlay Virtual Ethernet
631 <ulink url=
"https://en.wikipedia.org/wiki/Distributed_Overlay_Virtual_Ethernet">
632 (DVOE)
</ulink> clients. Defaults to false.
</para>
636 <term><varname>L2MissNotification=
</varname></term>
638 <para>Takes a boolean. When true, enables netlink LLADDR miss
639 notifications.
</para>
643 <term><varname>L3MissNotification=
</varname></term>
645 <para>Takes a boolean. When true, enables netlink IP address miss notifications.
</para>
649 <term><varname>RouteShortCircuit=
</varname></term>
651 <para>Takes a boolean. When true, route short circuiting is turned
656 <term><varname>UDPChecksum=
</varname></term>
658 <para>Takes a boolean. When true, transmitting UDP checksums when doing VXLAN/IPv4 is turned on.
</para>
662 <term><varname>UDP6ZeroChecksumTx=
</varname></term>
664 <para>Takes a boolean. When true, sending zero checksums in VXLAN/IPv6 is turned on.
</para>
668 <term><varname>UDP6ZeroChecksumRx=
</varname></term>
670 <para>Takes a boolean. When true, receiving zero checksums in VXLAN/IPv6 is turned on.
</para>
674 <term><varname>RemoteChecksumTx=
</varname></term>
676 <para>Takes a boolean. When true, remote transmit checksum offload of VXLAN is turned on.
</para>
680 <term><varname>RemoteChecksumRx=
</varname></term>
682 <para>Takes a boolean. When true, remote receive checksum offload in VXLAN is turned on.
</para>
686 <term><varname>GroupPolicyExtension=
</varname></term>
688 <para>Takes a boolean. When true, it enables Group Policy VXLAN extension security label mechanism
689 across network peers based on VXLAN. For details about the Group Policy VXLAN, see the
690 <ulink url=
"https://tools.ietf.org/html/draft-smith-vxlan-group-policy">
691 VXLAN Group Policy
</ulink> document. Defaults to false.
</para>
695 <term><varname>GenericProtocolExtension=
</varname></term>
697 <para>Takes a boolean. When true, Generic Protocol Extension extends the existing VXLAN protocol
698 to provide protocol typing, OAM, and versioning capabilities. For details about the VXLAN GPE
699 Header, see the
<ulink url=
"https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe-07">
700 Generic Protocol Extension for VXLAN
</ulink> document. If destination port is not specified and
701 Generic Protocol Extension is set then default port of
4790 is used. Defaults to false.
</para>
705 <term><varname>DestinationPort=
</varname></term>
707 <para>Configures the default destination UDP port. If the destination port is not specified then
708 Linux kernel default will be used. Set to
4789 to get the IANA assigned value.
</para>
712 <term><varname>PortRange=
</varname></term>
714 <para>Configures the source port range for the VXLAN. The kernel assigns the source UDP port based
715 on the flow to help the receiver to do load balancing. When this option is not set, the normal
716 range of local UDP ports is used.
</para>
720 <term><varname>FlowLabel=
</varname></term>
722 <para>Specifies the flow label to use in outgoing packets.
723 The valid range is
0-
1048575.
728 <term><varname>IPDoNotFragment=
</varname></term>
730 <para>Allows setting the IPv4 Do not Fragment (DF) bit in outgoing packets, or to inherit its
731 value from the IPv4 inner header. Takes a boolean value, or
<literal>inherit
</literal>. Set
732 to
<literal>inherit
</literal> if the encapsulated protocol is IPv6. When unset, the kernel's
733 default will be used.
</para>
737 <term><varname>Independent=
</varname></term>
739 <para>Takes a boolean. When true, the vxlan interface is created without any underlying network
740 interface. Defaults to false, which means that a .network file that requests this VXLAN interface
741 using
<varname>VXLAN=
</varname> is required for the VXLAN to be created.
</para>
748 <title>[GENEVE] Section Options
</title>
750 <para>The [GENEVE] section only applies for
751 netdevs of kind
<literal>geneve
</literal>, and accepts the
752 following keys:
</para>
754 <variablelist class='network-directives'
>
756 <term><varname>Id=
</varname></term>
758 <para>Specifies the Virtual Network Identifier (VNI) to use, a number between
0 and
16777215. This
759 field is mandatory.
</para>
763 <term><varname>Remote=
</varname></term>
765 <para>Specifies the unicast destination IP address to use in outgoing packets.
</para>
769 <term><varname>TOS=
</varname></term>
771 <para>Specifies the TOS value to use in outgoing packets. Takes a number between
1 and
255.
</para>
775 <term><varname>TTL=
</varname></term>
777 <para>Accepts the same values as in the [VXLAN] section, except that when unset
778 or set to
0, the kernel's default will be used, meaning that packet TTL will be set from
779 <filename>/proc/sys/net/ipv4/ip_default_ttl
</filename>.
</para>
783 <term><varname>UDPChecksum=
</varname></term>
785 <para>Takes a boolean. When true, specifies that UDP checksum is calculated for transmitted packets
790 <term><varname>UDP6ZeroChecksumTx=
</varname></term>
792 <para>Takes a boolean. When true, skip UDP checksum calculation for transmitted packets over IPv6.
</para>
796 <term><varname>UDP6ZeroChecksumRx=
</varname></term>
798 <para>Takes a boolean. When true, allows incoming UDP packets over IPv6 with zero checksum field.
</para>
802 <term><varname>DestinationPort=
</varname></term>
804 <para>Specifies destination port. Defaults to
6081. If not set or assigned the empty string, the default
805 port of
6081 is used.
</para>
809 <term><varname>FlowLabel=
</varname></term>
811 <para>Specifies the flow label to use in outgoing packets.
</para>
815 <term><varname>IPDoNotFragment=
</varname></term>
817 <para>Accepts the same key as in [VXLAN] section.
</para>
824 <title>[BareUDP] Section Options
</title>
826 <para>The [BareUDP] section only applies for
827 netdevs of kind
<literal>bareudp
</literal>, and accepts the
828 following keys:
</para>
830 <variablelist class='network-directives'
>
832 <term><varname>DestinationPort=
</varname></term>
834 <para>Specifies the destination UDP port (in range
1…
65535). This is mandatory.
</para>
839 <term><varname>EtherType=
</varname></term>
841 <para>Specifies the L3 protocol. Takes one of
<literal>ipv4
</literal>,
<literal>ipv6
</literal>,
<literal>mpls-uc
</literal>
842 or
<literal>mpls-mc
</literal>. This is mandatory.
</para>
849 <title>[L2TP] Section Options
</title>
851 <para>The [L2TP] section only applies for
852 netdevs of kind
<literal>l2tp
</literal>, and accepts the
853 following keys:
</para>
855 <variablelist class='network-directives'
>
857 <term><varname>TunnelId=
</varname></term>
859 <para>Specifies the tunnel identifier. Takes an number in the range
1…
4294967295. The value used
860 must match the
<literal>PeerTunnelId=
</literal> value being used at the peer. This setting is
865 <term><varname>PeerTunnelId=
</varname></term>
867 <para>Specifies the peer tunnel id. Takes a number in the range
1…
4294967295. The value used must
868 match the
<literal>TunnelId=
</literal> value being used at the peer. This setting is compulsory.
873 <term><varname>Remote=
</varname></term>
875 <para>Specifies the IP address of the remote peer. This setting is compulsory.
</para>
879 <term><varname>Local=
</varname></term>
881 <para>Specifies the IP address of the local interface. Takes an IP address, or the special values
882 <literal>auto
</literal>,
<literal>static
</literal>, or
<literal>dynamic
</literal>. When an address
883 is set, then the local interface must have the address. If
<literal>auto
</literal>, then one of the
884 addresses on the local interface is used. Similarly, if
<literal>static
</literal> or
885 <literal>dynamic
</literal> is set, then one of the static or dynamic addresses on the local
886 interface is used. Defaults to
<literal>auto
</literal>.
</para>
890 <term><varname>EncapsulationType=
</varname></term>
892 <para>Specifies the encapsulation type of the tunnel. Takes one of
<literal>udp
</literal> or
893 <literal>ip
</literal>.
</para>
897 <term><varname>UDPSourcePort=
</varname></term>
899 <para>Specifies the UDP source port to be used for the tunnel. When UDP encapsulation is selected
900 it's mandatory. Ignored when IP encapsulation is selected.
</para>
904 <term><varname>UDPDestinationPort=
</varname></term>
906 <para>Specifies destination port. When UDP encapsulation is selected it's mandatory. Ignored when IP
907 encapsulation is selected.
</para>
911 <term><varname>UDPChecksum=
</varname></term>
913 <para>Takes a boolean. When true, specifies that UDP checksum is calculated for transmitted packets
918 <term><varname>UDP6ZeroChecksumTx=
</varname></term>
920 <para>Takes a boolean. When true, skip UDP checksum calculation for transmitted packets over IPv6.
</para>
924 <term><varname>UDP6ZeroChecksumRx=
</varname></term>
926 <para>Takes a boolean. When true, allows incoming UDP packets over IPv6 with zero checksum field.
</para>
933 <title>[L2TPSession] Section Options
</title>
935 <para>The [L2TPSession] section only applies for
936 netdevs of kind
<literal>l2tp
</literal>, and accepts the
937 following keys:
</para>
938 <variablelist class='network-directives'
>
940 <term><varname>Name=
</varname></term>
942 <para>Specifies the name of the session. This setting is compulsory.
</para>
946 <term><varname>SessionId=
</varname></term>
948 <para>Specifies the session identifier. Takes an number in the range
1…
4294967295. The value used
949 must match the
<literal>SessionId=
</literal> value being used at the peer. This setting is
954 <term><varname>PeerSessionId=
</varname></term>
956 <para>Specifies the peer session identifier. Takes an number in the range
1…
4294967295.
957 The value used must match the
<literal>PeerSessionId=
</literal> value being used at the peer.
958 This setting is compulsory.
</para>
962 <term><varname>Layer2SpecificHeader=
</varname></term>
964 <para>Specifies layer2specific header type of the session. One of
<literal>none
</literal> or
<literal>default
</literal>. Defaults to
<literal>default
</literal>.
</para>
971 <title>[MACsec] Section Options
</title>
973 <para>The [MACsec] section only applies for network devices of kind
974 <literal>macsec
</literal>, and accepts the following keys:
</para>
976 <variablelist class='network-directives'
>
978 <term><varname>Port=
</varname></term>
980 <para>Specifies the port to be used for the MACsec transmit channel. The port is used to make
981 secure channel identifier (SCI). Takes a value between
1 and
65535. Defaults to unset.
986 <term><varname>Encrypt=
</varname></term>
988 <para>Takes a boolean. When true, enable encryption. Defaults to unset.
</para>
995 <title>[MACsecReceiveChannel] Section Options
</title>
996 <para>The [MACsecReceiveChannel] section only applies for network devices of
997 kind
<literal>macsec
</literal>, and accepts the following keys:
</para>
999 <variablelist class='network-directives'
>
1001 <term><varname>Port=
</varname></term>
1003 <para>Specifies the port to be used for the MACsec receive channel. The port is used to make
1004 secure channel identifier (SCI). Takes a value between
1 and
65535. This option is
1005 compulsory, and is not set by default.
</para>
1009 <term><varname>MACAddress=
</varname></term>
1011 <para>Specifies the MAC address to be used for the MACsec receive channel. The MAC address
1012 used to make secure channel identifier (SCI). This setting is compulsory, and is not set by
1020 <title>[MACsecTransmitAssociation] Section Options
</title>
1022 <para>The [MACsecTransmitAssociation] section only applies for network devices
1023 of kind
<literal>macsec
</literal>, and accepts the following keys:
</para>
1025 <variablelist class='network-directives'
>
1027 <term><varname>PacketNumber=
</varname></term>
1029 <para>Specifies the packet number to be used for replay protection and the construction of
1030 the initialization vector (along with the secure channel identifier [SCI]). Takes a value
1031 between
1-
4,
294,
967,
295. Defaults to unset.
1036 <term><varname>KeyId=
</varname></term>
1038 <para>Specifies the identification for the key. Takes a number between
0-
255. This option
1039 is compulsory, and is not set by default.
</para>
1043 <term><varname>Key=
</varname></term>
1045 <para>Specifies the encryption key used in the transmission channel. The same key must be
1046 configured on the peer’s matching receive channel. This setting is compulsory, and is not set
1047 by default. Takes a
128-bit key encoded in a hexadecimal string, for example
1048 <literal>dffafc8d7b9a43d5b9a3dfbbf6a30c16
</literal>.
</para>
1052 <term><varname>KeyFile=
</varname></term>
1054 <para>Takes an absolute path to a file which contains a
128-bit key encoded in a hexadecimal string,
1055 which will be used in the transmission channel. When this option is specified,
1056 <varname>Key=
</varname> is ignored. Note that the file must be readable by the user
1057 <literal>systemd-network
</literal>, so it should be, e.g., owned by
1058 <literal>root:systemd-network
</literal> with a
<literal>0640</literal> file mode. If the path
1059 refers to an
<constant>AF_UNIX
</constant> stream socket in the file system a connection is made to
1060 it and the key read from it.
</para>
1064 <term><varname>Activate=
</varname></term>
1066 <para>Takes a boolean. If enabled, then the security association is activated. Defaults to
1071 <term><varname>UseForEncoding=
</varname></term>
1073 <para>Takes a boolean. If enabled, then the security association is used for encoding. Only
1074 one [MACsecTransmitAssociation] section can enable this option. When enabled,
1075 <varname>Activate=yes
</varname> is implied. Defaults to unset.
</para>
1082 <title>[MACsecReceiveAssociation] Section Options
</title>
1084 <para>The [MACsecReceiveAssociation] section only applies for
1085 network devices of kind
<literal>macsec
</literal>, and accepts the
1086 following keys:
</para>
1088 <variablelist class='network-directives'
>
1090 <term><varname>Port=
</varname></term>
1092 <para>Accepts the same key as in [MACsecReceiveChannel] section.
</para>
1096 <term><varname>MACAddress=
</varname></term>
1098 <para>Accepts the same key as in [MACsecReceiveChannel] section.
</para>
1102 <term><varname>PacketNumber=
</varname></term>
1104 <para>Accepts the same key as in [MACsecTransmitAssociation] section.
</para>
1108 <term><varname>KeyId=
</varname></term>
1110 <para>Accepts the same key as in [MACsecTransmitAssociation] section.
</para>
1114 <term><varname>Key=
</varname></term>
1116 <para>Accepts the same key as in [MACsecTransmitAssociation] section.
</para>
1120 <term><varname>KeyFile=
</varname></term>
1122 <para>Accepts the same key as in [MACsecTransmitAssociation] section.
</para>
1126 <term><varname>Activate=
</varname></term>
1128 <para>Accepts the same key as in [MACsecTransmitAssociation] section.
</para>
1135 <title>[Tunnel] Section Options
</title>
1137 <para>The [Tunnel] section only applies for
1139 <literal>ipip
</literal>,
1140 <literal>sit
</literal>,
1141 <literal>gre
</literal>,
1142 <literal>gretap
</literal>,
1143 <literal>ip6gre
</literal>,
1144 <literal>ip6gretap
</literal>,
1145 <literal>vti
</literal>,
1146 <literal>vti6
</literal>,
1147 <literal>ip6tnl
</literal>, and
1148 <literal>erspan
</literal> and accepts
1149 the following keys:
</para>
1151 <variablelist class='network-directives'
>
1153 <term><varname>Local=
</varname></term>
1155 <para>A static local address for tunneled packets. It must be an address on another interface
1156 of this host, or one of the special values
<literal>any
</literal>,
1157 <literal>ipv4_link_local
</literal>,
<literal>ipv6_link_local
</literal>,
1158 <literal>dhcp4
</literal>,
<literal>dhcp6
</literal>, and
<literal>slaac
</literal>. If one
1159 of the special values except for
<literal>any
</literal> is specified, an address which
1160 matches the corresponding type on the underlying interface will be used. Defaults to
1161 <literal>any
</literal>.
</para>
1165 <term><varname>Remote=
</varname></term>
1167 <para>The remote endpoint of the tunnel. Takes an IP address or the special value
1168 <literal>any
</literal>.
</para>
1172 <term><varname>TOS=
</varname></term>
1174 <para>The Type Of Service byte value for a tunnel interface.
1175 For details about the TOS, see the
1176 <ulink url=
"http://tools.ietf.org/html/rfc1349"> Type of
1177 Service in the Internet Protocol Suite
</ulink> document.
1182 <term><varname>TTL=
</varname></term>
1184 <para>A fixed Time To Live N on tunneled packets. N is a
1185 number in the range
1…
255.
0 is a special value meaning that
1186 packets inherit the TTL value. The default value for IPv4
1187 tunnels is
0 (inherit). The default value for IPv6 tunnels is
1192 <term><varname>DiscoverPathMTU=
</varname></term>
1194 <para>Takes a boolean. When true, enables Path MTU Discovery on
1199 <term><varname>IPv6FlowLabel=
</varname></term>
1201 <para>Configures the
20-bit flow label (see
<ulink url=
"https://tools.ietf.org/html/rfc6437">
1202 RFC
6437</ulink>) field in the IPv6 header (see
<ulink url=
"https://tools.ietf.org/html/rfc2460">
1203 RFC
2460</ulink>), which is used by a node to label packets of a flow.
1204 It is only used for IPv6 tunnels.
1205 A flow label of zero is used to indicate packets that have
1207 It can be configured to a value in the range
0…
0xFFFFF, or be
1208 set to
<literal>inherit
</literal>, in which case the original flowlabel is used.
</para>
1212 <term><varname>CopyDSCP=
</varname></term>
1214 <para>Takes a boolean. When true, the Differentiated Service Code
1215 Point (DSCP) field will be copied to the inner header from
1216 outer header during the decapsulation of an IPv6 tunnel
1217 packet. DSCP is a field in an IP packet that enables different
1218 levels of service to be assigned to network traffic.
1219 Defaults to
<literal>no
</literal>.
1224 <term><varname>EncapsulationLimit=
</varname></term>
1226 <para>The Tunnel Encapsulation Limit option specifies how many additional
1227 levels of encapsulation are permitted to be prepended to the packet.
1228 For example, a Tunnel Encapsulation Limit option containing a limit
1229 value of zero means that a packet carrying that option may not enter
1230 another tunnel before exiting the current tunnel.
1231 (see
<ulink url=
"https://tools.ietf.org/html/rfc2473#section-4.1.1"> RFC
2473</ulink>).
1232 The valid range is
0…
255 and
<literal>none
</literal>. Defaults to
4.
1237 <term><varname>Key=
</varname></term>
1239 <para>The
<varname>Key=
</varname> parameter specifies the same key to use in
1240 both directions (
<varname>InputKey=
</varname> and
<varname>OutputKey=
</varname>).
1241 The
<varname>Key=
</varname> is either a number or an IPv4 address-like dotted quad.
1242 It is used as mark-configured SAD/SPD entry as part of the lookup key (both in data
1243 and control path) in IP XFRM (framework used to implement IPsec protocol).
1244 See
<ulink url=
"http://man7.org/linux/man-pages/man8/ip-xfrm.8.html">
1245 ip-xfrm — transform configuration
</ulink> for details. It is only used for VTI/VTI6,
1246 GRE, GRETAP, and ERSPAN tunnels.
</para>
1250 <term><varname>InputKey=
</varname></term>
1252 <para>The
<varname>InputKey=
</varname> parameter specifies the key to use for input.
1253 The format is same as
<varname>Key=
</varname>. It is only used for VTI/VTI6, GRE, GRETAP,
1254 and ERSPAN tunnels.
</para>
1258 <term><varname>OutputKey=
</varname></term>
1260 <para>The
<varname>OutputKey=
</varname> parameter specifies the key to use for output.
1261 The format is same as
<varname>Key=
</varname>. It is only used for VTI/VTI6, GRE, GRETAP,
1262 and ERSPAN tunnels.
</para>
1266 <term><varname>Mode=
</varname></term>
1268 <para>An
<literal>ip6tnl
</literal> tunnel can be in one of three
1270 <literal>ip6ip6
</literal> for IPv6 over IPv6,
1271 <literal>ipip6
</literal> for IPv4 over IPv6 or
1272 <literal>any
</literal> for either.
1277 <term><varname>Independent=
</varname></term>
1279 <para>Takes a boolean. When false (the default), the tunnel is always created over some network
1280 device, and a .network file that requests this tunnel using
<varname>Tunnel=
</varname> is required
1281 for the tunnel to be created. When true, the tunnel is created independently of any network as
1282 "tunnel@NONE".
</para>
1286 <term><varname>AssignToLoopback=
</varname></term>
1288 <para>Takes a boolean. If set to
<literal>yes
</literal>, the loopback interface
<literal>lo
</literal>
1289 is used as the underlying device of the tunnel interface. Defaults to
<literal>no
</literal>.
</para>
1293 <term><varname>AllowLocalRemote=
</varname></term>
1295 <para>Takes a boolean. When true allows tunnel traffic on
<varname>ip6tnl
</varname> devices where the remote endpoint is a local host address.
1296 When unset, the kernel's default will be used.
1301 <term><varname>FooOverUDP=
</varname></term>
1303 <para>Takes a boolean. Specifies whether
<varname>FooOverUDP=
</varname> tunnel is to be configured.
1304 Defaults to false. This takes effects only for IPIP, SIT, GRE, and GRETAP tunnels.
1305 For more detail information see
1306 <ulink url=
"https://lwn.net/Articles/614348">Foo over UDP
</ulink></para>
1310 <term><varname>FOUDestinationPort=
</varname></term>
1312 <para>This setting specifies the UDP destination port for encapsulation.
1313 This field is mandatory when
<varname>FooOverUDP=yes
</varname>, and is not set by default.
</para>
1317 <term><varname>FOUSourcePort=
</varname></term>
1319 <para>This setting specifies the UDP source port for encapsulation. Defaults to
<constant>0</constant>
1320 — that is, the source port for packets is left to the network stack to decide.
</para>
1324 <term><varname>Encapsulation=
</varname></term>
1326 <para>Accepts the same key as in the [FooOverUDP] section.
</para>
1330 <term><varname>IPv6RapidDeploymentPrefix=
</varname></term>
1332 <para>Reconfigure the tunnel for
<ulink url=
"https://tools.ietf.org/html/rfc5569">IPv6 Rapid
1333 Deployment
</ulink>, also known as
6rd. The value is an ISP-specific IPv6 prefix with a non-zero length. Only
1334 applicable to SIT tunnels.
</para>
1338 <term><varname>ISATAP=
</varname></term>
1340 <para>Takes a boolean. If set, configures the tunnel as Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) tunnel.
1341 Only applicable to SIT tunnels. When unset, the kernel's default will be used.
</para>
1345 <term><varname>SerializeTunneledPackets=
</varname></term>
1347 <para>Takes a boolean. If set to yes, then packets are serialized. Only applies for GRE,
1348 GRETAP, and ERSPAN tunnels. When unset, the kernel's default will be used.
1353 <term><varname>ERSPANIndex=
</varname></term>
1355 <para>Specifies the ERSPAN index field for the interface, an integer in the range
1…
1048575 associated with
1356 the ERSPAN traffic's source port and direction. This field is mandatory.
1364 <title>[FooOverUDP] Section Options
</title>
1366 <para>The [FooOverUDP] section only applies for
1367 netdevs of kind
<literal>fou
</literal> and accepts the
1368 following keys:
</para>
1370 <variablelist class='network-directives'
>
1372 <term><varname>Encapsulation=
</varname></term>
1374 <para>Specifies the encapsulation mechanism used to store networking packets of various protocols
1375 inside the UDP packets. Supports the following values:
1377 <literal>FooOverUDP
</literal> provides the simplest no-frills model of UDP encapsulation, it simply
1378 encapsulates packets directly in the UDP payload.
<literal>GenericUDPEncapsulation
</literal> is a
1379 generic and extensible encapsulation, it allows encapsulation of packets for any IP protocol and
1380 optional data as part of the encapsulation. For more detailed information see
<ulink
1381 url=
"https://lwn.net/Articles/615044">Generic UDP Encapsulation
</ulink>. Defaults to
1382 <literal>FooOverUDP
</literal>.
1387 <term><varname>Port=
</varname></term>
1389 <para>Specifies the port number where the encapsulated packets will arrive. Those packets will be
1390 removed and manually fed back into the network stack with the encapsulation removed to be sent to
1391 the real destination. This option is mandatory.
</para>
1395 <term><varname>PeerPort=
</varname></term>
1397 <para>Specifies the peer port number. Defaults to unset. Note that when peer port is set
1398 <literal>Peer=
</literal> address is mandatory.
</para>
1402 <term><varname>Protocol=
</varname></term>
1404 <para>The
<varname>Protocol=
</varname> specifies the protocol number of the packets arriving
1405 at the UDP port. When
<varname>Encapsulation=FooOverUDP
</varname>, this field is mandatory
1406 and is not set by default. Takes an IP protocol name such as
<literal>gre
</literal> or
1407 <literal>ipip
</literal>, or an integer within the range
1…
255. When
1408 <varname>Encapsulation=GenericUDPEncapsulation
</varname>, this must not be specified.
</para>
1412 <term><varname>Peer=
</varname></term>
1414 <para>Configures peer IP address. Note that when peer address is set
<literal>PeerPort=
</literal>
1415 is mandatory.
</para>
1419 <term><varname>Local=
</varname></term>
1421 <para>Configures local IP address.
</para>
1428 <title>[Peer] Section Options
</title>
1430 <para>The [Peer] section only applies for
1431 netdevs of kind
<literal>veth
</literal> and accepts the
1432 following keys:
</para>
1434 <variablelist class='network-directives'
>
1436 <term><varname>Name=
</varname></term>
1438 <para>The interface name used when creating the netdev.
1439 This setting is compulsory.
</para>
1443 <term><varname>MACAddress=
</varname></term>
1445 <para>The peer MACAddress, if not set, it is generated in
1446 the same way as the MAC address of the main
1454 <title>[VXCAN] Section Options
</title>
1456 <para>The [VXCAN] section only applies for
1457 netdevs of kind
<literal>vxcan
</literal> and accepts the
1458 following key:
</para>
1460 <variablelist class='network-directives'
>
1462 <term><varname>Peer=
</varname></term>
1464 <para>The peer interface name used when creating the netdev.
1465 This setting is compulsory.
</para>
1472 <title>[Tun] Section Options
</title>
1474 <para>The [Tun] section only applies for
1475 netdevs of kind
<literal>tun
</literal>, and accepts the following
1478 <variablelist class='network-directives'
>
1480 <term><varname>MultiQueue=
</varname></term>
1481 <listitem><para>Takes a boolean. Configures whether
1482 to use multiple file descriptors (queues) to parallelize
1483 packets sending and receiving. Defaults to
1484 <literal>no
</literal>.
</para>
1488 <term><varname>PacketInfo=
</varname></term>
1489 <listitem><para>Takes a boolean. Configures whether
1490 packets should be prepended with four extra bytes (two flag
1491 bytes and two protocol bytes). If disabled, it indicates that
1492 the packets will be pure IP packets. Defaults to
1493 <literal>no
</literal>.
</para>
1497 <term><varname>VNetHeader=
</varname></term>
1498 <listitem><para>Takes a boolean. Configures
1499 IFF_VNET_HDR flag for a tun or tap device. It allows sending
1500 and receiving larger Generic Segmentation Offload (GSO)
1501 packets. This may increase throughput significantly.
1503 <literal>no
</literal>.
</para>
1507 <term><varname>User=
</varname></term>
1508 <listitem><para>User to grant access to the
1509 <filename>/dev/net/tun
</filename> device.
</para>
1513 <term><varname>Group=
</varname></term>
1514 <listitem><para>Group to grant access to the
1515 <filename>/dev/net/tun
</filename> device.
</para>
1522 <title>[Tap] Section Options
</title>
1524 <para>The [Tap] section only applies for
1525 netdevs of kind
<literal>tap
</literal>, and accepts the same keys
1526 as the [Tun] section.
</para>
1530 <title>[WireGuard] Section Options
</title>
1532 <para>The [WireGuard] section accepts the following
1535 <variablelist class='network-directives'
>
1537 <term><varname>PrivateKey=
</varname></term>
1539 <para>The Base64 encoded private key for the interface. It can be
1540 generated using the
<command>wg genkey
</command> command
1541 (see
<citerefentry project=
"wireguard"><refentrytitle>wg
</refentrytitle><manvolnum>8</manvolnum></citerefentry>).
1542 This option or
<varname>PrivateKeyFile=
</varname> is mandatory to use WireGuard.
1543 Note that because this information is secret, you may want to set
1544 the permissions of the .netdev file to be owned by
<literal>root:systemd-network
</literal>
1545 with a
<literal>0640</literal> file mode.
</para>
1549 <term><varname>PrivateKeyFile=
</varname></term>
1551 <para>Takes an absolute path to a file which contains the Base64 encoded private key for the
1552 interface. When this option is specified, then
<varname>PrivateKey=
</varname> is ignored. Note
1553 that the file must be readable by the user
<literal>systemd-network
</literal>, so it should be,
1554 e.g., owned by
<literal>root:systemd-network
</literal> with a
<literal>0640</literal> file mode. If
1555 the path refers to an
<constant>AF_UNIX
</constant> stream socket in the file system a connection is
1556 made to it and the key read from it.
</para>
1560 <term><varname>ListenPort=
</varname></term>
1562 <para>Sets UDP port for listening. Takes either value between
1 and
65535
1563 or
<literal>auto
</literal>. If
<literal>auto
</literal> is specified,
1564 the port is automatically generated based on interface name.
1565 Defaults to
<literal>auto
</literal>.
</para>
1569 <term><varname>FirewallMark=
</varname></term>
1571 <para>Sets a firewall mark on outgoing WireGuard packets from this interface. Takes a number between
1 and
4294967295.
</para>
1575 <term><varname>RouteTable=
</varname></term>
1577 <para>The table identifier for the routes to the addresses specified in the
1578 <varname>AllowedIPs=
</varname>. Takes a negative boolean value, one of the predefined names
1579 <literal>default
</literal>,
<literal>main
</literal>, and
<literal>local
</literal>, names
1580 defined in
<varname>RouteTable=
</varname> in
1581 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1582 or a number in the range
1…
4294967295. When
<literal>off
</literal> the routes to the
1583 addresses specified in the
<varname>AllowedIPs=
</varname> setting will not be configured.
1584 Defaults to false. This setting will be ignored when the same setting is specified in the
1585 [WireGuardPeer] section.
</para>
1589 <term><varname>RouteMetric=
</varname></term>
1591 <para>The priority of the routes to the addresses specified in the
1592 <varname>AllowedIPs=
</varname>. Takes an integer in the range
0…
4294967295. Defaults to
0
1593 for IPv4 addresses, and
1024 for IPv6 addresses. This setting will be ignored when the same
1594 setting is specified in the [WireGuardPeer] section.
</para>
1601 <title>[WireGuardPeer] Section Options
</title>
1603 <para>The [WireGuardPeer] section accepts the following
1606 <variablelist class='network-directives'
>
1608 <term><varname>PublicKey=
</varname></term>
1610 <para>Sets a Base64 encoded public key calculated by
<command>wg pubkey
</command>
1611 (see
<citerefentry project=
"wireguard"><refentrytitle>wg
</refentrytitle><manvolnum>8</manvolnum></citerefentry>)
1612 from a private key, and usually transmitted out of band to the
1613 author of the configuration file. This option is mandatory for this
1618 <term><varname>PresharedKey=
</varname></term>
1620 <para>Optional preshared key for the interface. It can be generated
1621 by the
<command>wg genpsk
</command> command. This option adds an
1622 additional layer of symmetric-key cryptography to be mixed into the
1623 already existing public-key cryptography, for post-quantum
1625 Note that because this information is secret, you may want to set
1626 the permissions of the .netdev file to be owned by
<literal>root:systemd-network
</literal>
1627 with a
<literal>0640</literal> file mode.
</para>
1631 <term><varname>PresharedKeyFile=
</varname></term>
1633 <para>Takes an absolute path to a file which contains the Base64 encoded preshared key for the
1634 peer. When this option is specified, then
<varname>PresharedKey=
</varname> is ignored. Note that
1635 the file must be readable by the user
<literal>systemd-network
</literal>, so it should be, e.g.,
1636 owned by
<literal>root:systemd-network
</literal> with a
<literal>0640</literal> file mode. If the
1637 path refers to an
<constant>AF_UNIX
</constant> stream socket in the file system a connection is
1638 made to it and the key read from it.
</para>
1642 <term><varname>AllowedIPs=
</varname></term>
1644 <para>Sets a comma-separated list of IP (v4 or v6) addresses with CIDR masks
1645 from which this peer is allowed to send incoming traffic and to
1646 which outgoing traffic for this peer is directed.
</para>
1648 <para>The catch-all
0.0.0.0/
0 may be specified for matching all IPv4 addresses,
1649 and ::/
0 may be specified for matching all IPv6 addresses.
</para>
1651 <para>Note that this only affects
<emphasis>routing inside the network interface itself
</emphasis>,
1652 i.e. the packets that pass through the tunnel itself. To cause packets to be sent via the tunnel in
1653 the first place, an appropriate route needs to be added as well — either in the
1654 <literal>[Routes]
</literal> section on the
<literal>.network
</literal> matching the wireguard
1655 interface, or externally to
<filename>systemd-networkd
</filename>.
</para>
1659 <term><varname>Endpoint=
</varname></term>
1661 <para>Sets an endpoint IP address or hostname, followed by a colon, and then
1662 a port number. This endpoint will be updated automatically once to
1663 the most recent source IP address and port of correctly
1664 authenticated packets from the peer at configuration time.
</para>
1668 <term><varname>PersistentKeepalive=
</varname></term>
1670 <para>Sets a seconds interval, between
1 and
65535 inclusive, of how often
1671 to send an authenticated empty packet to the peer for the purpose
1672 of keeping a stateful firewall or NAT mapping valid persistently.
1673 For example, if the interface very rarely sends traffic, but it
1674 might at anytime receive traffic from a peer, and it is behind NAT,
1675 the interface might benefit from having a persistent keepalive
1676 interval of
25 seconds. If set to
0 or
"off", this option is
1677 disabled. By default or when unspecified, this option is off.
1678 Most users will not need this.
</para>
1682 <term><varname>RouteTable=
</varname></term>
1684 <para>The table identifier for the routes to the addresses specified in the
1685 <varname>AllowedIPs=
</varname>. Takes a negative boolean value, one of the predefined names
1686 <literal>default
</literal>,
<literal>main
</literal>, and
<literal>local
</literal>, names
1687 defined in
<varname>RouteTable=
</varname> in
1688 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1689 or a number in the range
1…
4294967295. Defaults to unset, and the value specified in the
1690 same setting in the [WireGuard] section will be used.
</para>
1694 <term><varname>RouteMetric=
</varname></term>
1696 <para>The priority of the routes to the addresses specified in the
1697 <varname>AllowedIPs=
</varname>. Takes an integer in the range
0…
4294967295. Defaults to
1698 unset, and the value specified in the same setting in the [WireGuard] section will be used.
1706 <title>[Bond] Section Options
</title>
1708 <para>The [Bond] section accepts the following
1711 <variablelist class='network-directives'
>
1713 <term><varname>Mode=
</varname></term>
1715 <para>Specifies one of the bonding policies. The default is
1716 <literal>balance-rr
</literal> (round robin). Possible values are
1717 <literal>balance-rr
</literal>,
1718 <literal>active-backup
</literal>,
1719 <literal>balance-xor
</literal>,
1720 <literal>broadcast
</literal>,
1721 <literal>802.3ad
</literal>,
1722 <literal>balance-tlb
</literal>, and
1723 <literal>balance-alb
</literal>.
1729 <term><varname>TransmitHashPolicy=
</varname></term>
1731 <para>Selects the transmit hash policy to use for slave
1732 selection in balance-xor,
802.3ad, and tlb modes. Possible
1734 <literal>layer2
</literal>,
1735 <literal>layer3+
4</literal>,
1736 <literal>layer2+
3</literal>,
1737 <literal>encap2+
3</literal>, and
1738 <literal>encap3+
4</literal>.
1744 <term><varname>LACPTransmitRate=
</varname></term>
1746 <para>Specifies the rate with which link partner transmits
1747 Link Aggregation Control Protocol Data Unit packets in
1748 802.3ad mode. Possible values are
<literal>slow
</literal>,
1749 which requests partner to transmit LACPDUs every
30 seconds,
1750 and
<literal>fast
</literal>, which requests partner to
1751 transmit LACPDUs every second. The default value is
1752 <literal>slow
</literal>.
</para>
1757 <term><varname>MIIMonitorSec=
</varname></term>
1759 <para>Specifies the frequency that Media Independent
1760 Interface link monitoring will occur. A value of zero
1761 disables MII link monitoring. This value is rounded down to
1762 the nearest millisecond. The default value is
0.
</para>
1767 <term><varname>UpDelaySec=
</varname></term>
1769 <para>Specifies the delay before a link is enabled after a
1770 link up status has been detected. This value is rounded down
1771 to a multiple of
<varname>MIIMonitorSec=
</varname>. The default value is
1777 <term><varname>DownDelaySec=
</varname></term>
1779 <para>Specifies the delay before a link is disabled after a
1780 link down status has been detected. This value is rounded
1781 down to a multiple of
<varname>MIIMonitorSec=
</varname>. The default value is
1787 <term><varname>LearnPacketIntervalSec=
</varname></term>
1789 <para>Specifies the number of seconds between instances where the bonding
1790 driver sends learning packets to each slave peer switch.
1791 The valid range is
1…
0x7fffffff; the default value is
1. This option
1792 has an effect only for the balance-tlb and balance-alb modes.
</para>
1797 <term><varname>AdSelect=
</varname></term>
1799 <para>Specifies the
802.3ad aggregation selection logic to use. Possible values are
1800 <literal>stable
</literal>,
1801 <literal>bandwidth
</literal> and
1802 <literal>count
</literal>.
1808 <term><varname>AdActorSystemPriority=
</varname></term>
1810 <para>Specifies the
802.3ad actor system priority. Takes a number in the range
1…
65535.
</para>
1815 <term><varname>AdUserPortKey=
</varname></term>
1817 <para>Specifies the
802.3ad user defined portion of the port key. Takes a number in the range
1823 <term><varname>AdActorSystem=
</varname></term>
1825 <para>Specifies the
802.3ad system MAC address. This cannot be a null or multicast address.
1831 <term><varname>FailOverMACPolicy=
</varname></term>
1833 <para>Specifies whether the active-backup mode should set all slaves to
1834 the same MAC address at the time of enslavement or, when enabled, to perform special handling of the
1835 bond's MAC address in accordance with the selected policy. The default policy is none.
1837 <literal>none
</literal>,
1838 <literal>active
</literal> and
1839 <literal>follow
</literal>.
1845 <term><varname>ARPValidate=
</varname></term>
1847 <para>Specifies whether or not ARP probes and replies should be
1848 validated in any mode that supports ARP monitoring, or whether
1849 non-ARP traffic should be filtered (disregarded) for link
1850 monitoring purposes. Possible values are
1851 <literal>none
</literal>,
1852 <literal>active
</literal>,
1853 <literal>backup
</literal> and
1854 <literal>all
</literal>.
1860 <term><varname>ARPIntervalSec=
</varname></term>
1862 <para>Specifies the ARP link monitoring frequency. A value of
0 disables ARP monitoring. The
1863 default value is
0, and the default unit seconds.
1869 <term><varname>ARPIPTargets=
</varname></term>
1871 <para>Specifies the IP addresses to use as ARP monitoring peers when
1872 <varname>ARPIntervalSec=
</varname> is greater than
0. These are the targets of the ARP
1873 request sent to determine the health of the link to the targets.
1874 Specify these values in IPv4 dotted decimal format. At least one IP
1875 address must be given for ARP monitoring to function. The
1876 maximum number of targets that can be specified is
16. The
1877 default value is no IP addresses.
1883 <term><varname>ARPAllTargets=
</varname></term>
1885 <para>Specifies the quantity of
<varname>ARPIPTargets=
</varname> that must be reachable
1886 in order for the ARP monitor to consider a slave as being up.
1887 This option affects only active-backup mode for slaves with
1888 ARPValidate enabled. Possible values are
1889 <literal>any
</literal> and
1890 <literal>all
</literal>.
1896 <term><varname>PrimaryReselectPolicy=
</varname></term>
1898 <para>Specifies the reselection policy for the primary slave. This
1899 affects how the primary slave is chosen to become the active slave
1900 when failure of the active slave or recovery of the primary slave
1901 occurs. This option is designed to prevent flip-flopping between
1902 the primary slave and other slaves. Possible values are
1903 <literal>always
</literal>,
1904 <literal>better
</literal> and
1905 <literal>failure
</literal>.
1911 <term><varname>ResendIGMP=
</varname></term>
1913 <para>Specifies the number of IGMP membership reports to be issued after
1914 a failover event. One membership report is issued immediately after
1915 the failover, subsequent packets are sent in each
200ms interval.
1916 The valid range is
0…
255. Defaults to
1. A value of
0
1917 prevents the IGMP membership report from being issued in response
1918 to the failover event.
1924 <term><varname>PacketsPerSlave=
</varname></term>
1926 <para>Specify the number of packets to transmit through a slave before
1927 moving to the next one. When set to
0, then a slave is chosen at
1928 random. The valid range is
0…
65535. Defaults to
1. This option
1929 only has effect when in balance-rr mode.
1935 <term><varname>GratuitousARP=
</varname></term>
1937 <para>Specify the number of peer notifications (gratuitous ARPs and
1938 unsolicited IPv6 Neighbor Advertisements) to be issued after a
1939 failover event. As soon as the link is up on the new slave,
1940 a peer notification is sent on the bonding device and each
1941 VLAN sub-device. This is repeated at each link monitor interval
1942 (ARPIntervalSec or MIIMonitorSec, whichever is active) if the number is
1943 greater than
1. The valid range is
0…
255. The default value is
1.
1944 These options affect only the active-backup mode.
1950 <term><varname>AllSlavesActive=
</varname></term>
1952 <para>Takes a boolean. Specifies that duplicate frames (received on inactive ports)
1953 should be dropped when false, or delivered when true. Normally, bonding will drop
1954 duplicate frames (received on inactive ports), which is desirable for
1955 most users. But there are some times it is nice to allow duplicate
1956 frames to be delivered. The default value is false (drop duplicate frames
1957 received on inactive ports).
1963 <term><varname>DynamicTransmitLoadBalancing=
</varname></term>
1965 <para>Takes a boolean. Specifies if dynamic shuffling of flows is enabled. Applies only
1966 for balance-tlb mode. Defaults to unset.
1972 <term><varname>MinLinks=
</varname></term>
1974 <para>Specifies the minimum number of links that must be active before
1975 asserting carrier. The default value is
0.
1981 <para>For more detail information see
1982 <ulink url=
"https://www.kernel.org/doc/Documentation/networking/bonding.txt">
1983 Linux Ethernet Bonding Driver HOWTO
</ulink></para>
1987 <title>[Xfrm] Section Options
</title>
1989 <para>The [Xfrm] section accepts the following
1992 <variablelist class='network-directives'
>
1994 <term><varname>InterfaceId=
</varname></term>
1996 <para>Sets the ID/key of the xfrm interface which needs to be associated with a SA/policy.
1997 Can be decimal or hexadecimal, valid range is
1-
0xffffffff. This is mandatory.
</para>
2001 <term><varname>Independent=
</varname></term>
2003 <para>Takes a boolean. If false (the default), the xfrm interface must have an underlying device
2004 which can be used for hardware offloading.
</para>
2009 <para>For more detail information see
2010 <ulink url=
"https://lwn.net/Articles/757391">Virtual XFRM Interfaces
</ulink>.
</para>
2014 <title>[VRF] Section Options
</title>
2015 <para>The [VRF] section only applies for
2016 netdevs of kind
<literal>vrf
</literal> and accepts the
2017 following key:
</para>
2019 <variablelist class='network-directives'
>
2021 <term><varname>Table=
</varname></term>
2023 <para>The numeric routing table identifier. This setting is compulsory.
</para>
2030 <title>[BatmanAdvanced] Section Options
</title>
2032 <para>The [BatmanAdvanced] section only applies for netdevs of kind
<literal>batadv
</literal> and accepts
2033 the following keys:
</para>
2035 <variablelist class='network-directives'
>
2037 <term><varname>GatewayMode=
</varname></term>
2039 <para>Takes one of
<literal>off
</literal>,
<literal>server
</literal>, or
<literal>client
</literal>.
2040 A batman-adv node can either run in server mode (sharing its internet
2041 connection with the mesh) or in client mode (searching for the most suitable internet connection
2042 in the mesh) or having the gateway support turned off entirely (which is the default setting).
2047 <term><varname>Aggregation=
</varname></term>
2049 <para>Takes a boolean value. Enables or disables aggregation of originator messages. Defaults to
2055 <term><varname>BridgeLoopAvoidance=
</varname></term>
2057 <para>Takes a boolean value. Enables or disables avoidance of loops on bridges. Defaults to true.
2062 <term><varname>DistributedArpTable=
</varname></term>
2064 <para>Takes a boolean value. Enables or disables the distributed ARP table. Defaults to true.
</para>
2068 <term><varname>Fragmentation=
</varname></term>
2070 <para>Takes a boolean value. Enables or disables fragmentation. Defaults to true.
</para>
2074 <term><varname>HopPenalty=
</varname></term>
2076 <para>The hop penalty setting allows one to modify
2077 <citerefentry project='mankier'
><refentrytitle>batctl
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
2078 preference for multihop routes vs. short routes. This integer value is applied to the
2079 TQ (Transmit Quality) of each forwarded OGM (Originator Message), thereby propagating the
2080 cost of an extra hop (the packet has to be received and retransmitted which costs airtime).
2081 A higher hop penalty will make it more unlikely that other nodes will choose this node as
2082 intermediate hop towards any given destination. The default hop penalty of '
15' is a reasonable
2083 value for most setups and probably does not need to be changed. However, mobile nodes could
2084 choose a value of
255 (maximum value) to avoid being chosen as a router by other nodes.
2085 The minimum value is
0.
2090 <term><varname>OriginatorIntervalSec=
</varname></term>
2092 <para>The value specifies the interval in seconds, unless another time unit is specified in which
2093 batman-adv floods the network with its protocol information.
2094 See
<citerefentry><refentrytitle>systemd.time
</refentrytitle><manvolnum>7</manvolnum></citerefentry>
2095 for more information.
</para>
2099 <term><varname>GatewayBandwidthDown=
</varname></term>
2101 <para>If the node is a server, this
2102 parameter is used to inform other nodes in the network about
2103 this node's internet connection download bandwidth in bits per second. Just enter any number
2104 suffixed with K, M, G or T (base
1000) and the batman-adv
2105 module will propagate the entered value in the mesh.
</para>
2109 <term><varname>GatewayBandwidthUp=
</varname></term>
2111 <para>If the node is a server, this
2112 parameter is used to inform other nodes in the network about
2113 this node's internet connection upload bandwidth in bits per second. Just enter any number
2114 suffixed with K, M, G or T (base
1000) and the batman-adv
2115 module will propagate the entered value in the mesh.
</para>
2119 <term><varname>RoutingAlgorithm=
</varname></term>
2121 <para>This can be either
<literal>batman-v
</literal> or
<literal>batman-iv
</literal> and describes which routing_algo
2122 of
<citerefentry><refentrytitle>batctl
</refentrytitle><manvolnum>8</manvolnum></citerefentry> to use. The algorithm
2123 cannot be changed after interface creation. Defaults to
<literal>batman-v
</literal>.
2131 <title>[IPoIB] Section Options
</title>
2132 <para>The [IPoIB] section only applies for netdevs of kind
<literal>ipoib
</literal> and accepts the
2133 following keys:
</para>
2135 <variablelist class='network-directives'
>
2137 <term><varname>PartitionKey=
</varname></term>
2139 <para>Takes an integer in the range
1…
0xffff, except for
0x8000. Defaults to unset, and the
2140 kernel's default is used.
</para>
2144 <varlistentry id='ipoib_mode'
>
2145 <term><varname>Mode=
</varname></term>
2147 <para>Takes one of the special values
<literal>datagram
</literal> or
2148 <literal>connected
</literal>. Defaults to unset, and the kernel's default is used.
</para>
2150 <para>When
<literal>datagram
</literal>, the Infiniband unreliable datagram (UD) transport is
2151 used, and so the interface MTU is equal to the IB L2 MTU minus the IPoIB encapsulation
2152 header (
4 bytes). For example, in a typical IB fabric with a
2K MTU, the IPoIB MTU will be
2153 2048 -
4 =
2044 bytes.
</para>
2155 <para>When
<literal>connected
</literal>, the Infiniband reliable connected (RC) transport is
2156 used. Connected mode takes advantage of the connected nature of the IB transport and allows
2157 an MTU up to the maximal IP packet size of
64K, which reduces the number of IP packets needed
2158 for handling large UDP datagrams, TCP segments, etc and increases the performance for large
2163 <varlistentry id='ipoib_umcast'
>
2164 <term><varname>IgnoreUserspaceMulticastGroup=
</varname></term>
2166 <para>Takes an boolean value. When true, the kernel ignores multicast groups handled by
2167 userspace. Defaults to unset, and the kernel's default is used.
</para>
2174 <title>Examples
</title>
2176 <title>/etc/systemd/network/
25-bridge.netdev
</title>
2178 <programlisting>[NetDev]
2180 Kind=bridge
</programlisting>
2184 <title>/etc/systemd/network/
25-vlan1.netdev
</title>
2186 <programlisting>[Match]
2194 Id=
1</programlisting>
2197 <title>/etc/systemd/network/
25-ipip.netdev
</title>
2198 <programlisting>[NetDev]
2204 Local=
192.168.223.238
2205 Remote=
192.169.224.239
2206 TTL=
64</programlisting>
2209 <title>/etc/systemd/network/
1-fou-tunnel.netdev
</title>
2210 <programlisting>[NetDev]
2220 <title>/etc/systemd/network/
25-fou-ipip.netdev
</title>
2221 <programlisting>[NetDev]
2228 Remote=
10.65.208.211
2230 FOUDestinationPort=
5555
2234 <title>/etc/systemd/network/
25-tap.netdev
</title>
2235 <programlisting>[NetDev]
2241 PacketInfo=yes
</programlisting> </example>
2244 <title>/etc/systemd/network/
25-sit.netdev
</title>
2245 <programlisting>[NetDev]
2252 Remote=
10.65.223.239</programlisting>
2256 <title>/etc/systemd/network/
25-
6rd.netdev
</title>
2257 <programlisting>[NetDev]
2264 IPv6RapidDeploymentPrefix=
2602::/
24</programlisting>
2268 <title>/etc/systemd/network/
25-gre.netdev
</title>
2269 <programlisting>[NetDev]
2276 Remote=
10.65.223.239</programlisting>
2280 <title>/etc/systemd/network/
25-ip6gre.netdev
</title>
2281 <programlisting>[NetDev]
2286 Key=
123</programlisting>
2290 <title>/etc/systemd/network/
25-vti.netdev
</title>
2292 <programlisting>[NetDev]
2299 Remote=
10.65.223.239</programlisting>
2303 <title>/etc/systemd/network/
25-veth.netdev
</title>
2304 <programlisting>[NetDev]
2309 Name=veth-peer
</programlisting>
2313 <title>/etc/systemd/network/
25-bond.netdev
</title>
2314 <programlisting>[NetDev]
2320 TransmitHashPolicy=layer3+
4
2322 LACPTransmitRate=fast
2327 <title>/etc/systemd/network/
25-dummy.netdev
</title>
2328 <programlisting>[NetDev]
2331 MACAddress=
12:
34:
56:
78:
9a:bc
</programlisting>
2334 <title>/etc/systemd/network/
25-vrf.netdev
</title>
2335 <para>Create a VRF interface with table
42.
</para>
2336 <programlisting>[NetDev]
2341 Table=
42</programlisting>
2345 <title>/etc/systemd/network/
25-macvtap.netdev
</title>
2346 <para>Create a MacVTap device.
</para>
2347 <programlisting>[NetDev]
2353 <title>/etc/systemd/network/
25-wireguard.netdev
</title>
2354 <programlisting>[NetDev]
2359 PrivateKey=EEGlnEPYJV//kbvvIqxKkQwOiS+UENyPncC4bF46ong=
2363 PublicKey=RDf+LSpeEre7YEIKaxg+wbpsNV7du+ktR99uBEtIiCA=
2364 AllowedIPs=fd31:bf08:
57cb::/
48,
192.168.26.0/
24
2365 Endpoint=wireguard.example.com:
51820</programlisting>
2369 <title>/etc/systemd/network/
27-xfrm.netdev
</title>
2370 <programlisting>[NetDev]
2375 Independent=yes
</programlisting>
2380 <title>See Also
</title>
2382 <citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry>,
2383 <citerefentry><refentrytitle>systemd-networkd
</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
2384 <citerefentry><refentrytitle>systemd.link
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
2385 <citerefentry><refentrytitle>systemd.network
</refentrytitle><manvolnum>5</manvolnum></citerefentry>