2 <!DOCTYPE refentry PUBLIC
"-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
4 <!-- SPDX-License-Identifier: LGPL-2.1-or-later -->
6 <refentry id=
"systemd.network" conditional='ENABLE_NETWORKD'
7 xmlns:
xi=
"http://www.w3.org/2001/XInclude">
10 <title>systemd.network
</title>
11 <productname>systemd
</productname>
15 <refentrytitle>systemd.network
</refentrytitle>
16 <manvolnum>5</manvolnum>
20 <refname>systemd.network
</refname>
21 <refpurpose>Network configuration
</refpurpose>
25 <para><filename><replaceable>network
</replaceable>.network
</filename></para>
29 <title>Description
</title>
31 <para>A plain ini-style text file that encodes network configuration for matching network
33 <citerefentry><refentrytitle>systemd-networkd
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
34 See
<citerefentry><refentrytitle>systemd.syntax
</refentrytitle><manvolnum>7</manvolnum></citerefentry>
35 for a general description of the syntax.
</para>
37 <para>The main network file must have the extension
<filename>.network
</filename>; other
38 extensions are ignored. Networks are applied to links whenever the links appear.
</para>
40 <para>The
<filename>.network
</filename> files are read from the files located in the system network
41 directories
<filename>/usr/lib/systemd/network
</filename> and
42 <filename>/usr/local/lib/systemd/network
</filename>, the volatile runtime network directory
43 <filename>/run/systemd/network
</filename> and the local administration network directory
44 <filename>/etc/systemd/network
</filename>. All configuration files are collectively sorted and
45 processed in alphanumeric order, regardless of the directories in which they live. However, files
46 with identical filenames replace each other. It is recommended that each filename is prefixed with
47 a number smaller than
<literal>70</literal> (e.g.
<filename>10-eth0.network
</filename>). Otherwise, the
48 default
<filename>.network
</filename> files or those generated by
49 <citerefentry><refentrytitle>systemd-network-generator.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
50 may take precedence over user configured files. Files in
<filename>/etc/
</filename> have the highest
51 priority, files in
<filename>/run/
</filename> take precedence over files with the same name under
52 <filename>/usr/
</filename>. This can be used to override a system-supplied configuration file with
53 a local file if needed. As a special case, an empty file (file size
0) or symlink with the same
54 name pointing to
<filename>/dev/null
</filename> disables the configuration file entirely (it is
57 <para>Along with the network file
<filename>foo.network
</filename>, a
"drop-in" directory
58 <filename>foo.network.d/
</filename> may exist. All files with the suffix
59 <literal>.conf
</literal> from this directory will be merged in the alphanumeric order and parsed
60 after the main file itself has been parsed. This is useful to alter or add configuration settings,
61 without having to modify the main configuration file. Each drop-in file must have appropriate
62 section headers.
</para>
64 <para>In addition to
<filename>/etc/systemd/network
</filename>, drop-in
<literal>.d
</literal>
65 directories can be placed in
<filename>/usr/lib/systemd/network
</filename> or
66 <filename>/run/systemd/network
</filename> directories. Drop-in files in
67 <filename>/etc/
</filename> take precedence over those in
<filename>/run/
</filename> which in turn
68 take precedence over those in
<filename>/usr/lib/
</filename>. Drop-in files under any of these
69 directories take precedence over the main network file wherever located.
</para>
73 <title>[Match] Section Options
</title>
75 <para>The network file contains a [Match] section, which determines if a given network file may
76 be applied to a given interface; and a [Network] section specifying how the interface should be
77 configured. The first (in alphanumeric order) of the network files that matches a given interface
78 is applied, all later files are ignored, even if they match as well.
</para>
80 <para>Note that any network interfaces that have the
<varname>ID_NET_MANAGED_BY=
</varname> udev property
81 set will never be matched by any .network files – unless the property's value is the string
82 <literal>io.systemd.Network
</literal> – even if the [Match] section would otherwise match. This may be
83 used to exclude specific network interfaces from
<command>systemd-networkd
</command>'s management, while
84 keeping the [Match] section generic. The
<varname>ID_NET_MANAGED_BY=
</varname> property thus declares
85 intended
<emphasis>ownership
</emphasis> of the device, and permits ensuring that concurrent network
86 management implementations do not compete for management of specific devices.
</para>
88 <para>A network file is said to match a network interface if all matches specified by the [Match]
89 section are satisfied. When a network file does not contain valid settings in [Match] section, then
90 the file will match all interfaces and
<command>systemd-networkd
</command> warns about that. Hint:
91 to avoid the warning and to make it clear that all interfaces shall be matched, add the following:
92 <programlisting>Name=*
</programlisting> The following keys are accepted:
</para>
94 <variablelist class='network-directives'
>
95 <xi:include href=
"systemd.link.xml" xpointer=
"mac-address" />
96 <xi:include href=
"systemd.link.xml" xpointer=
"permanent-mac-address" />
97 <xi:include href=
"systemd.link.xml" xpointer=
"path" />
98 <xi:include href=
"systemd.link.xml" xpointer=
"driver" />
99 <xi:include href=
"systemd.link.xml" xpointer=
"type" />
100 <xi:include href=
"systemd.link.xml" xpointer=
"kind" />
101 <xi:include href=
"systemd.link.xml" xpointer=
"property" />
104 <term><varname>Name=
</varname></term>
106 <para>A whitespace-separated list of shell-style globs matching the device name, as exposed
107 by the udev property
<literal>INTERFACE
</literal>, or device's alternative names. If the
108 list is prefixed with a
"!", the test is inverted.
</para>
110 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
115 <term><varname>WLANInterfaceType=
</varname></term>
117 <para>A whitespace-separated list of wireless network type. Supported values are
118 <literal>ad-hoc
</literal>,
<literal>station
</literal>,
<literal>ap
</literal>,
119 <literal>ap-vlan
</literal>,
<literal>wds
</literal>,
<literal>monitor
</literal>,
120 <literal>mesh-point
</literal>,
<literal>p2p-client
</literal>,
<literal>p2p-go
</literal>,
121 <literal>p2p-device
</literal>,
<literal>ocb
</literal>, and
<literal>nan
</literal>. If the
122 list is prefixed with a
"!", the test is inverted.
</para>
124 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
129 <term><varname>SSID=
</varname></term>
131 <para>A whitespace-separated list of shell-style globs matching the SSID of the currently
132 connected wireless LAN. If the list is prefixed with a
"!", the test is inverted.
</para>
134 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
139 <term><varname>BSSID=
</varname></term>
141 <para>A whitespace-separated list of hardware address of the currently connected wireless
142 LAN. Use full colon-, hyphen- or dot-delimited hexadecimal. See the example in
143 <varname>MACAddress=
</varname>. This option may appear more than once, in which case the
144 lists are merged. If the empty string is assigned to this option, the list is reset.
</para>
146 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
150 <xi:include href=
"systemd.link.xml" xpointer=
"host" />
151 <xi:include href=
"systemd.link.xml" xpointer=
"virtualization" />
152 <xi:include href=
"systemd.link.xml" xpointer=
"kernel-command-line" />
153 <xi:include href=
"systemd.link.xml" xpointer=
"kernel-version" />
154 <xi:include href=
"systemd.link.xml" xpointer=
"credential" />
155 <xi:include href=
"systemd.link.xml" xpointer=
"architecture" />
156 <xi:include href=
"systemd.link.xml" xpointer=
"firmware" />
161 <title>[Link] Section Options
</title>
163 <para>The [Link] section accepts the following keys:
</para>
165 <variablelist class='network-directives'
>
167 <term><varname>MACAddress=
</varname></term>
169 <para>The hardware address to set for the device.
</para>
171 <xi:include href=
"version-info.xml" xpointer=
"v218"/>
176 <term><varname>MTUBytes=
</varname></term>
178 <para>The maximum transmission unit in bytes to set for the device. The usual suffixes K, M,
179 G, are supported and are understood to the base of
1024.
</para>
180 <para>Note that if IPv6 is enabled on the interface, and the MTU is chosen below
1280 (the
181 minimum MTU for IPv6) it will automatically be increased to this value.
</para>
183 <xi:include href=
"version-info.xml" xpointer=
"v218"/>
188 <term><varname>ARP=
</varname></term>
190 <para>Takes a boolean. If set to true, the ARP (low-level Address Resolution Protocol)
191 for this interface is enabled. When unset, the kernel's default will be used.
</para>
192 <para> For example, disabling ARP is useful when creating multiple MACVLAN or VLAN virtual
193 interfaces atop a single lower-level physical interface, which will then only serve as a
194 link/
"bridge" device aggregating traffic to the same physical link and not participate in
195 the network otherwise. Defaults to unset.
</para>
197 <xi:include href=
"version-info.xml" xpointer=
"v232"/>
202 <term><varname>Multicast=
</varname></term>
204 <para>Takes a boolean. If set to true, the multicast flag on the device is enabled. Defaults
207 <xi:include href=
"version-info.xml" xpointer=
"v239"/>
212 <term><varname>AllMulticast=
</varname></term>
214 <para>Takes a boolean. If set to true, the driver retrieves all multicast packets from the
215 network. This happens when multicast routing is enabled. Defaults to unset.
</para>
217 <xi:include href=
"version-info.xml" xpointer=
"v239"/>
222 <term><varname>Promiscuous=
</varname></term>
224 <para>Takes a boolean. If set to true, promiscuous mode of the interface is enabled. Defaults
226 <para>If this is set to false for the underlying link of a
<literal>passthru
</literal> mode
227 MACVLAN/MACVTAP, the virtual interface will be created with the
<literal>nopromisc
</literal>
230 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
235 <term><varname>Unmanaged=
</varname></term>
237 <para>Takes a boolean. When
<literal>yes
</literal>, no attempts are made to bring up or
238 configure matching links, equivalent to when there are no matching network files. Defaults to
239 <literal>no
</literal>.
</para>
240 <para>This is useful for preventing later matching network files from interfering with
241 certain interfaces that are fully controlled by other applications.
</para>
243 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
248 <term><varname>Group=
</varname></term>
250 <para>Link groups are similar to port ranges found in managed switches. When network
251 interfaces are added to a numbered group, operations on all the interfaces from that group
252 can be performed at once. Takes an unsigned integer in the range
0…
2147483647. Defaults to
255 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
260 <term><varname>RequiredForOnline=
</varname></term>
262 <para>Takes a boolean, a minimum operational state (e.g.,
<literal>carrier
</literal>), or a range
263 of operational state separated with a colon (e.g.,
<literal>degraded:routable
</literal>).
265 <citerefentry><refentrytitle>networkctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
266 for possible operational states. When
<literal>yes
</literal>, the network is deemed required
267 when determining whether the system is online (including when running
268 <command>systemd-networkd-wait-online
</command>). When
<literal>no
</literal>, the network is
269 ignored when determining the online state. When a minimum operational state and an optional
270 maximum operational state are set,
<command>systemd-networkd-wait-online
</command> deems that the
271 interface is online when the operational state is in the specified range.
</para>
273 <para>Defaults to
<literal>yes
</literal> when
<varname>ActivationPolicy=
</varname> is not
274 set, or set to
<literal>up
</literal>,
<literal>always-up
</literal>, or
275 <literal>bound
</literal>. Defaults to
<literal>no
</literal> when
276 <varname>ActivationPolicy=
</varname> is set to
<literal>manual
</literal> or
277 <literal>down
</literal>. This is forced to
<literal>no
</literal> when
278 <varname>ActivationPolicy=
</varname> is set to
<literal>always-down
</literal>.
</para>
280 <para>The network will be brought up normally (as configured by
281 <varname>ActivationPolicy=
</varname>), but in the event that there is no address being
282 assigned by DHCP or the cable is not plugged in, the link will simply remain offline and be
283 skipped automatically by
<command>systemd-networkd-wait-online
</command> if
284 <literal>RequiredForOnline=no
</literal>.
</para>
286 <para>The boolean value
<literal>yes
</literal> is translated as follows;
289 <term><option>CAN devices
</option></term>
291 <para><literal>carrier
</literal>,
</para>
292 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
296 <term><option>Master devices, e.g. bond or bridge
</option></term>
298 <para><literal>degraded-carrier
</literal> with
<varname>RequiredFamilyForOnline=any
</varname>,
</para>
299 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
303 <term><option>Bonding port interfaces
</option></term>
305 <para><literal>enslaved
</literal>,
</para>
306 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
310 <term><option>Other interfaces
</option></term>
312 <para><literal>degraded
</literal>.
</para>
313 <xi:include href=
"version-info.xml" xpointer=
"v236"/>
319 <para>This setting can be overridden by the command line option for
320 <command>systemd-networkd-wait-online
</command>. See
321 <citerefentry><refentrytitle>systemd-networkd-wait-online.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
322 for more details.
</para>
324 <xi:include href=
"version-info.xml" xpointer=
"v236"/>
329 <term><varname>RequiredFamilyForOnline=
</varname></term>
331 <para>Takes an address family. When specified, an IP address in the given family is deemed
332 required when determining whether the link is online (including when running
333 <command>systemd-networkd-wait-online
</command>). Takes one of
<literal>ipv4
</literal>,
334 <literal>ipv6
</literal>,
<literal>both
</literal>, or
<literal>any
</literal>. Defaults to
335 <literal>no
</literal>. Note that this option has no effect if
336 <literal>RequiredForOnline=no
</literal>.
</para>
338 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
343 <term><varname>ActivationPolicy=
</varname></term>
345 <para>Specifies the policy for
<command>systemd-networkd
</command> managing the link
346 administrative state. Specifically, this controls how
<command>systemd-networkd
</command>
347 changes the network device's
<literal>IFF_UP
</literal> flag, which is sometimes
348 controlled by system administrators by running e.g.,
349 <command>ip link set dev eth0 up
</command> or
<command>ip link set dev eth0 down
</command>,
350 and can also be changed with
<command>networkctl up eth0
</command> or
351 <command>networkctl down eth0
</command>.
</para>
353 <para>Takes one of
<literal>up
</literal>,
<literal>always-up
</literal>,
354 <literal>manual
</literal>,
<literal>always-down
</literal>,
<literal>down
</literal>,
355 or
<literal>bound
</literal>. When
<literal>manual
</literal>,
356 <command>systemd-networkd
</command> will not change the link's admin state automatically;
357 the system administrator must bring the interface up or down manually, as desired. When
358 <literal>up
</literal> (the default) or
<literal>always-up
</literal>, or
359 <literal>down
</literal> or
<literal>always-down
</literal>,
360 <command>systemd-networkd
</command> will set the link up or down, respectively, when the
361 interface is (re)configured. When
<literal>always-up
</literal> or
362 <literal>always-down
</literal>,
<command>systemd-networkd
</command> will set the link up or
363 down, respectively, any time
<command>systemd-networkd
</command> detects a change in the
364 administrative state. When
<varname>BindCarrier=
</varname> is also set, this is automatically
365 set to
<literal>bound
</literal> and any other value is ignored.
</para>
367 <para>When the policy is set to
<literal>down
</literal> or
<literal>manual
</literal>, the
368 default value of
<varname>RequiredForOnline=
</varname> is
<literal>no
</literal>. When the
369 policy is set to
<literal>always-down
</literal>, the value of
370 <varname>RequiredForOnline=
</varname> forced to
<literal>no
</literal>.
</para>
372 <para>The administrative state is not the same as the carrier state, so using
373 <literal>always-up
</literal> does not mean the link will never lose carrier. The link carrier
374 depends on both the administrative state as well as the network device's physical connection.
375 However, to avoid reconfiguration failures, when using
<literal>always-up
</literal>,
376 <varname>IgnoreCarrierLoss=
</varname> is forced to true.
</para>
378 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
384 <xi:include href=
"systemd.link.xml" xpointer=
"sr-iov" />
387 <title>[Network] Section Options
</title>
389 <para>The [Network] section accepts the following keys:
</para>
391 <variablelist class='network-directives'
>
393 <term><varname>Description=
</varname></term>
395 <para>A description of the device. This is only used for presentation purposes.
</para>
397 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
402 <term><varname>DHCP=
</varname></term>
404 <para>Enables DHCPv4 and/or DHCPv6 client support. Accepts
<literal>yes
</literal>,
405 <literal>no
</literal>,
<literal>ipv4
</literal>, or
<literal>ipv6
</literal>. Defaults to
406 <literal>no
</literal>.
</para>
408 <para>Note that DHCPv6 will by default be triggered by Router Advertisements, if reception is
409 enabled, regardless of this parameter. By explicitly enabling DHCPv6 support here, the DHCPv6
410 client will be started in the mode specified by the
<varname>WithoutRA=
</varname> setting in the
411 [DHCPv6] section, regardless of the presence of routers on the link, or what flags the routers
412 pass. See
<varname>IPv6AcceptRA=
</varname>.
</para>
414 <para>Furthermore, note that by default the domain name specified through DHCP is not used
415 for name resolution. See option
<option>UseDomains=
</option> below.
</para>
417 <para>See the [DHCPv4] or [DHCPv6] sections below for further configuration options for the
418 DHCP client support.
</para>
420 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
425 <term><varname>DHCPServer=
</varname></term>
427 <para>Takes a boolean. If set to
<literal>yes
</literal>, DHCPv4 server will be started.
428 Defaults to
<literal>no
</literal>. Further settings for the DHCP server may be set in the
429 [DHCPServer] section described below.
</para>
431 <para>Even if this is enabled, the DHCP server will not be started automatically and wait for the
432 persistent storage being ready to load/save leases in the storage, unless
433 <varname>RelayTarget=
</varname> or
<varname>PersistLeases=no
</varname> are specified in the
434 [DHCPServer] section. It will be started after
435 <filename>systemd-networkd-persistent-storage.service
</filename> is started, which calls
436 <command>networkctl persistent-storage yes
</command>. See
437 <citerefentry><refentrytitle>networkctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
438 for more details.
</para>
440 <xi:include href=
"version-info.xml" xpointer=
"v215"/>
445 <term><varname>LinkLocalAddressing=
</varname></term>
447 <para>Enables link-local address autoconfiguration. Accepts
<option>yes
</option>,
448 <option>no
</option>,
<option>ipv4
</option>, and
<option>ipv6
</option>. An IPv6 link-local
449 address is configured when
<option>yes
</option> or
<option>ipv6
</option>. An IPv4 link-local
450 address is configured when
<option>yes
</option> or
<option>ipv4
</option> and when DHCPv4
451 autoconfiguration has been unsuccessful for some time. (IPv4 link-local address
452 autoconfiguration will usually happen in parallel with repeated attempts to acquire a DHCPv4
455 <para>Defaults to
<option>no
</option> when
<varname>KeepMaster=
</varname> or
456 <varname>Bridge=
</varname> is set or when the specified
457 <varname>MACVLAN=
</varname>/
<varname>MACVTAP=
</varname> has
<varname>Mode=passthru
</varname>,
458 or
<option>ipv6
</option> otherwise.
</para>
460 <xi:include href=
"version-info.xml" xpointer=
"v219"/>
465 <term><varname>IPv6LinkLocalAddressGenerationMode=
</varname></term>
467 <para>Specifies how IPv6 link-local address is generated. Takes one of
468 <literal>eui64
</literal>,
<literal>none
</literal>,
<literal>stable-privacy
</literal> and
469 <literal>random
</literal>. When unset,
<literal>stable-privacy
</literal> is used if
470 <varname>IPv6StableSecretAddress=
</varname> is specified, and if not,
471 <literal>eui64
</literal> is used. Note that if
<varname>LinkLocalAddressing=
</varname> is
472 <literal>no
</literal> or
<literal>ipv4
</literal>, then
473 <varname>IPv6LinkLocalAddressGenerationMode=
</varname> will be ignored. Also, even if
474 <varname>LinkLocalAddressing=
</varname> is
<literal>yes
</literal> or
<literal>ipv6
</literal>,
475 setting
<varname>IPv6LinkLocalAddressGenerationMode=none
</varname>
476 disables to configure an IPv6 link-local address.
</para>
478 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
483 <term><varname>IPv6StableSecretAddress=
</varname></term>
485 <para>Takes an IPv6 address. The specified address will be used as a stable secret for
486 generating IPv6 link-local address. If this setting is specified, and
487 <varname>IPv6LinkLocalAddressGenerationMode=
</varname> is unset, then
488 <varname>IPv6LinkLocalAddressGenerationMode=stable-privacy
</varname> is implied.
489 If this setting is not specified, and
<literal>stable-privacy
</literal> is set to
490 <varname>IPv6LinkLocalAddressGenerationMode=
</varname>,
491 then a stable secret address will be generated from the local machine ID and the interface
494 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
499 <term><varname>IPv4LLStartAddress=
</varname></term>
501 <para>Specifies the first IPv4 link-local address to try. Takes an IPv4 address for example
502 169.254.1.2, from the link-local address range:
169.254.0.0/
16 except for
169.254.0.0/
24 and
503 169.254.255.0/
24. This setting may be useful if the device should always have the same address
504 as long as there is no address conflict. When unset, a random address will be automatically
505 selected. Defaults to unset.
</para>
507 <xi:include href=
"version-info.xml" xpointer=
"v252"/>
512 <term><varname>IPv4LLRoute=
</varname></term>
514 <para>Takes a boolean. If set to true, sets up the route needed for non-IPv4LL hosts to
515 communicate with IPv4LL-only hosts. Defaults to false.
</para>
517 <xi:include href=
"version-info.xml" xpointer=
"v216"/>
522 <term><varname>DefaultRouteOnDevice=
</varname></term>
524 <para>Takes a boolean. If set to true, sets up the IPv4 default route bound to the interface.
525 Defaults to false. This is useful when creating routes on point-to-point interfaces. This is
526 equivalent to e.g. the following,
527 <programlisting>ip route add default dev veth99
</programlisting>
529 <programlisting>[Route]
530 Gateway=
0.0.0.0</programlisting></para>
531 <para>Currently, there are no way to specify e.g., the table for the route configured by this
532 setting. To configure the default route with such an additional property, please use the
534 <programlisting>[Route]
536 Table=
1234</programlisting></para>
537 <para>If you'd like to create an IPv6 default route bound to the interface, please use the
539 <programlisting>[Route]
541 Table=
1234</programlisting></para>
543 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
548 <term><varname>LLMNR=
</varname></term>
550 <para>Takes a boolean or
<literal>resolve
</literal>. When true, enables
551 <ulink url=
"https://tools.ietf.org/html/rfc4795">Link-Local Multicast Name Resolution
</ulink>
552 on the link. When set to
<literal>resolve
</literal>, only resolution is enabled, but not host
553 registration and announcement. Defaults to true. This setting is read by
554 <citerefentry><refentrytitle>systemd-resolved.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
557 <xi:include href=
"version-info.xml" xpointer=
"v216"/>
562 <term><varname>MulticastDNS=
</varname></term>
564 <para>Takes a boolean or
<literal>resolve
</literal>. When true, enables
565 <ulink url=
"https://tools.ietf.org/html/rfc6762">Multicast DNS
</ulink> support on the link.
566 When set to
<literal>resolve
</literal>, only resolution is enabled, but not host or service
567 registration and announcement. Defaults to false. This setting is read by
568 <citerefentry><refentrytitle>systemd-resolved.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
571 <xi:include href=
"version-info.xml" xpointer=
"v229"/>
576 <term><varname>DNSOverTLS=
</varname></term>
578 <para>Takes a boolean or
<literal>opportunistic
</literal>. When true, enables
579 <ulink url=
"https://tools.ietf.org/html/rfc7858">DNS-over-TLS
</ulink> support on the link.
580 When set to
<literal>opportunistic
</literal>, compatibility with non-DNS-over-TLS servers is
581 increased, by automatically turning off DNS-over-TLS servers in this case. This option
582 defines a per-interface setting for
583 <citerefentry><refentrytitle>resolved.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>'s
584 global
<varname>DNSOverTLS=
</varname> option. Defaults to unset, and the global setting will
585 be used. This setting is read by
586 <citerefentry><refentrytitle>systemd-resolved.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
589 <xi:include href=
"version-info.xml" xpointer=
"v239"/>
594 <term><varname>DNSSEC=
</varname></term>
596 <para>Takes a boolean or
<literal>allow-downgrade
</literal>. When true, enables
597 <ulink url=
"https://tools.ietf.org/html/rfc4033">DNSSEC
</ulink> DNS validation support on the
598 link. When set to
<literal>allow-downgrade
</literal>, compatibility with non-DNSSEC capable
599 networks is increased, by automatically turning off DNSSEC in this case. This option defines
600 a per-interface setting for
601 <citerefentry><refentrytitle>resolved.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>'s
602 global
<varname>DNSSEC=
</varname> option. Defaults to unset, and the global setting will be
603 used. This setting is read by
604 <citerefentry><refentrytitle>systemd-resolved.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
607 <xi:include href=
"version-info.xml" xpointer=
"v229"/>
612 <term><varname>DNSSECNegativeTrustAnchors=
</varname></term>
614 <para>A space-separated list of DNSSEC negative trust anchor domains. If specified and DNSSEC
615 is enabled, look-ups done via the interface's DNS server will be subject to the list of
616 negative trust anchors, and not require authentication for the specified domains, or anything
617 below it. Use this to disable DNSSEC authentication for specific private domains, that cannot
618 be proven valid using the Internet DNS hierarchy. Defaults to the empty list. This setting is
620 <citerefentry><refentrytitle>systemd-resolved.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
623 <xi:include href=
"version-info.xml" xpointer=
"v229"/>
628 <term><varname>LLDP=
</varname></term>
630 <para>Controls support for Ethernet LLDP packet reception. LLDP is a link-layer protocol
631 commonly implemented on professional routers and bridges which announces which physical port
632 a system is connected to, as well as other related data. Accepts a boolean or the special
633 value
<literal>routers-only
</literal>. When true, incoming LLDP packets are accepted and a
634 database of all LLDP neighbors maintained. If
<literal>routers-only
</literal> is set only
635 LLDP data of various types of routers is collected and LLDP data about other types of devices
636 ignored (such as stations, telephones and others). If false, LLDP reception is disabled.
637 Defaults to
<literal>routers-only
</literal>. Use
638 <citerefentry><refentrytitle>networkctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
639 to query the collected neighbor data. LLDP is only available on Ethernet links. See
640 <varname>EmitLLDP=
</varname> below for enabling LLDP packet emission from the local system.
643 <xi:include href=
"version-info.xml" xpointer=
"v219"/>
648 <term><varname>EmitLLDP=
</varname></term>
650 <para>Controls support for Ethernet LLDP packet emission. Accepts a boolean parameter or the
651 special values
<literal>nearest-bridge
</literal>,
<literal>non-tpmr-bridge
</literal> and
652 <literal>customer-bridge
</literal>. Defaults to false, which turns off LLDP packet emission.
653 If not false, a short LLDP packet with information about the local system is sent out in
654 regular intervals on the link. The LLDP packet will contain information about the local
655 hostname, the local machine ID (as stored in
656 <citerefentry><refentrytitle>machine-id
</refentrytitle><manvolnum>5</manvolnum></citerefentry>)
657 and the local interface name, as well as the pretty hostname of the system (as set in
658 <citerefentry><refentrytitle>machine-info
</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
659 LLDP emission is only available on Ethernet links. Note that this setting passes data
660 suitable for identification of host to the network and should thus not be enabled on
661 untrusted networks, where such identification data should not be made available. Use this
662 option to permit other systems to identify on which interfaces they are connected to this
663 system. The three special values control propagation of the LLDP packets. The
664 <literal>nearest-bridge
</literal> setting permits propagation only to the nearest connected
665 bridge,
<literal>non-tpmr-bridge
</literal> permits propagation across Two-Port MAC Relays,
666 but not any other bridges, and
<literal>customer-bridge
</literal> permits propagation until
667 a customer bridge is reached. For details about these concepts, see
668 <ulink url=
"https://standards.ieee.org/findstds/standard/802.1AB-2016.html">IEEE
802.1AB-
2016</ulink>.
669 Note that configuring this setting to true is equivalent to
670 <literal>nearest-bridge
</literal>, the recommended and most restricted level of propagation.
671 See
<varname>LLDP=
</varname> above for an option to enable LLDP reception.
</para>
673 <xi:include href=
"version-info.xml" xpointer=
"v230"/>
678 <term><varname>BindCarrier=
</varname></term>
680 <para>A link name or a list of link names. When set, controls the behavior of the current
681 link. When all links in the list are in an operational down state, the current link is
682 brought down. When at least one link has carrier, the current interface is brought up.
</para>
684 <para>This forces
<varname>ActivationPolicy=
</varname> to be set to
<literal>bound
</literal>.
687 <xi:include href=
"version-info.xml" xpointer=
"v220"/>
692 <term><varname>Address=
</varname></term>
694 <para>A static IPv4 or IPv6 address and its prefix length, separated by a
695 <literal>/
</literal> character. Specify this key more than once to configure several
696 addresses. The format of the address must be as described in
697 <citerefentry project='man-pages'
><refentrytitle>inet_pton
</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
698 This is a short-hand for an [Address] section only containing an Address key (see below).
699 This option may be specified more than once.
</para>
701 <para>If the specified address is
<literal>0.0.0.0</literal> (for IPv4) or
702 <literal>::
</literal> (for IPv6), a new address range of the requested size is automatically
703 allocated from a system-wide pool of unused ranges. Note that the prefix length must be equal
704 or larger than
8 for IPv4, and
64 for IPv6. The allocated range is checked against all
705 current network interfaces and all known network configuration files to avoid address range
706 conflicts. The default system-wide pool consists of
192.168.0.0/
16,
172.16.0.0/
12 and
707 10.0.0.0/
8 for IPv4, and fd00::/
8 for IPv6. This functionality is useful to manage a large
708 number of dynamically created network interfaces with the same network configuration and
709 automatic address range assignment.
</para>
711 <para>If an empty string is specified, then the all previous assignments in both [Network] and
712 [Address] sections are cleared.
</para>
714 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
719 <term><varname>Gateway=
</varname></term>
721 <para>The gateway address, which must be in the format described in
722 <citerefentry project='man-pages'
><refentrytitle>inet_pton
</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
723 This is a short-hand for a [Route] section only containing a
<varname>Gateway=
</varname> key.
724 This option may be specified more than once.
</para>
726 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
731 <term><varname>DNS=
</varname></term>
733 <para>A DNS server address, which must be in the format described in
734 <citerefentry project='man-pages'
><refentrytitle>inet_pton
</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
735 This option may be specified more than once. Each address can optionally take a port number
736 separated with
<literal>:
</literal>, a network interface name or index separated with
737 <literal>%
</literal>, and a Server Name Indication (SNI) separated with
<literal>#
</literal>.
738 When IPv6 address is specified with a port number, then the address must be in the square
739 brackets. That is, the acceptable full formats are
740 <literal>111.222.333.444:
9953%ifname#example.com
</literal> for IPv4 and
741 <literal>[
1111:
2222::
3333]:
9953%ifname#example.com
</literal> for IPv6. If an empty string is
742 assigned, then the all previous assignments are cleared. This setting is read by
743 <citerefentry><refentrytitle>systemd-resolved.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
746 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
751 <term><varname>Domains=
</varname></term>
753 <para>A whitespace-separated list of domains which should be resolved using the DNS servers
754 on this link. Each item in the list should be a domain name, optionally prefixed with a tilde
755 (
<literal>~
</literal>). The domains with the prefix are called
"routing-only domains". The
756 domains without the prefix are called
"search domains" and are first used as search suffixes
757 for extending single-label hostnames (hostnames containing no dots) to become fully qualified
758 domain names (FQDNs). If a single-label hostname is resolved on this interface, each of the
759 specified search domains are appended to it in turn, converting it into a fully qualified
760 domain name, until one of them may be successfully resolved.
</para>
762 <para>Both
"search" and
"routing-only" domains are used for routing of DNS queries: look-ups
763 for hostnames ending in those domains (hence also single label names, if any
"search domains"
764 are listed), are routed to the DNS servers configured for this interface. The domain routing
765 logic is particularly useful on multi-homed hosts with DNS servers serving particular private
766 DNS zones on each interface.
</para>
768 <para>The
"routing-only" domain
<literal>~.
</literal> (the tilde indicating definition of a
769 routing domain, the dot referring to the DNS root domain which is the implied suffix of all
770 valid DNS names) has special effect. It causes all DNS traffic which does not match another
771 configured domain routing entry to be routed to DNS servers specified for this interface.
772 This setting is useful to prefer a certain set of DNS servers if a link on which they are
773 connected is available.
</para>
775 <para>This setting is read by
776 <citerefentry><refentrytitle>systemd-resolved.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
777 "Search domains" correspond to the
<varname>domain
</varname> and
<varname>search
</varname>
779 <citerefentry project='man-pages'
><refentrytitle>resolv.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
780 Domain name routing has no equivalent in the traditional glibc API, which has no concept of
781 domain name servers limited to a specific link.
</para>
783 <xi:include href=
"version-info.xml" xpointer=
"v216"/>
788 <term><varname>DNSDefaultRoute=
</varname></term>
790 <para>Takes a boolean argument. If true, this link's configured DNS servers are used for
791 resolving domain names that do not match any link's configured
<varname>Domains=
</varname>
792 setting. If false, this link's configured DNS servers are never used for such domains, and
793 are exclusively used for resolving names that match at least one of the domains configured on
794 this link. If not specified defaults to an automatic mode: queries not matching any link's
795 configured domains will be routed to this link if it has no routing-only domains configured.
798 <xi:include href=
"version-info.xml" xpointer=
"v240"/>
803 <term><varname>NTP=
</varname></term>
805 <para>An NTP server address (either an IP address, or a hostname). This option may be
806 specified more than once. This setting is read by
807 <citerefentry><refentrytitle>systemd-timesyncd.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
810 <xi:include href=
"version-info.xml" xpointer=
"v216"/>
815 <term><varname>IPv4Forwarding=
</varname></term>
817 <para>Configures IPv4 packet forwarding for the interface. Takes a boolean value. This controls the
818 <filename>net.ipv4.conf.
<replaceable>INTERFACE
</replaceable>.forwarding
</filename> sysctl option of
819 the network interface. See
820 <ulink url=
"https://docs.kernel.org/networking/ip-sysctl.html">IP Sysctl
</ulink>
821 for more details about the sysctl option. Defaults to true if
<varname>IPMasquerade=
</varname> is
822 enabled for IPv4, otherwise the value specified to the same setting in
823 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
824 will be used. If none of them are specified, the sysctl option will not be changed.
</para>
826 <para>To control the global setting, use the same setting in
827 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
830 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
835 <term><varname>IPv6Forwarding=
</varname></term>
837 <para>Configures IPv6 packet forwarding for the interface. Takes a boolean value. This controls the
838 <filename>net.ipv6.conf.
<replaceable>INTERFACE
</replaceable>.forwarding
</filename> sysctl option of
839 the network interface. See
840 <ulink url=
"https://docs.kernel.org/networking/ip-sysctl.html">IP Sysctl
</ulink>
841 for more details about the sysctl option. Defaults to true if
<varname>IPMasquerade=
</varname> is
842 enabled for IPv6 or
<varname>IPv6SendRA=
</varname> is enabled, otherwise the value specified to the
844 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
845 will be used. If none of them are specified, the sysctl option will not be changed.
</para>
847 <para>To control the global setting, use the same setting in
848 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
851 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
856 <term><varname>IPMasquerade=
</varname></term>
858 <para>Configures IP masquerading for the network interface. If enabled, packets forwarded
859 from the network interface will be appear as coming from the local host. Takes one of
860 <literal>ipv4
</literal>,
<literal>ipv6
</literal>,
<literal>both
</literal>, or
861 <literal>no
</literal>. Defaults to
<literal>no
</literal>.
</para>
862 <para>Note. Any positive boolean values such as
<literal>yes
</literal> or
863 <literal>true
</literal> are now deprecated. Please use one of the values above.
</para>
865 <xi:include href=
"version-info.xml" xpointer=
"v219"/>
870 <term><varname>IPv6PrivacyExtensions=
</varname></term>
872 <para>Configures use of stateless temporary addresses that change over time (see
873 <ulink url=
"https://tools.ietf.org/html/rfc4941">RFC
4941</ulink>,
874 Privacy Extensions for Stateless Address Autoconfiguration in IPv6). Takes a boolean or the
875 special values
<literal>prefer-public
</literal> and
<literal>kernel
</literal>. When true,
876 enables the privacy extensions and prefers temporary addresses over public addresses. When
877 <literal>prefer-public
</literal>, enables the privacy extensions, but prefers public
878 addresses over temporary addresses. When false, the privacy extensions remain disabled. When
879 <literal>kernel
</literal>, the kernel's default setting will be left in place. When unspecified,
880 the value specified in the same setting in
881 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
882 which defaults to
<literal>no
</literal>, will be used.
</para>
884 <xi:include href=
"version-info.xml" xpointer=
"v222"/>
889 <term><varname>IPv6AcceptRA=
</varname></term>
891 <para>Takes a boolean. Controls IPv6 Router Advertisement (RA) reception support for the interface.
892 If true, RAs are accepted; if false, RAs are ignored. When RAs are accepted, they may trigger the
893 start of the DHCPv6 client if the relevant flags are set in the RA data, or if no routers are found
894 on the link. Defaults to false for bridge devices, when IP forwarding is enabled,
895 <varname>IPv6SendRA=
</varname> or
<varname>KeepMaster=
</varname> is enabled. Otherwise, enabled by
896 default. Cannot be enabled on devices aggregated in a bond device or when link-local addressing is
899 <para>Further settings for the IPv6 RA support may be configured in the [IPv6AcceptRA]
900 section, see below.
</para>
903 <ulink url=
"https://docs.kernel.org/networking/ip-sysctl.html">IP Sysctl
</ulink>
904 in the kernel documentation regarding
<literal>accept_ra
</literal>, but note that systemd's
905 setting of
<constant>1</constant> (i.e. true) corresponds to kernel's setting of
906 <constant>2</constant>.
</para>
908 <para>Note that kernel's implementation of the IPv6 RA protocol is always disabled,
909 regardless of this setting. If this option is enabled, a userspace implementation of the IPv6
910 RA protocol is used, and the kernel's own implementation remains disabled, since
911 <command>systemd-networkd
</command> needs to know all details supplied in the advertisements,
912 and these are not available from the kernel if the kernel's own implementation is used.
915 <xi:include href=
"version-info.xml" xpointer=
"v231"/>
920 <term><varname>IPv6DuplicateAddressDetection=
</varname></term>
922 <para>Configures the amount of IPv6 Duplicate Address Detection (DAD) probes to send. When
923 unset, the kernel's default will be used.
</para>
925 <xi:include href=
"version-info.xml" xpointer=
"v228"/>
930 <term><varname>IPv6HopLimit=
</varname></term>
932 <para>Configures IPv6 Hop Limit. Takes an integer in the range
1…
255. For each router that
933 forwards the packet, the hop limit is decremented by
1. When the hop limit field reaches zero, the
934 packet is discarded. When unset, the kernel's default will be used.
</para>
936 <xi:include href=
"version-info.xml" xpointer=
"v228"/>
941 <term><varname>IPv6RetransmissionTimeSec=
</varname></term>
943 <para>Configures IPv6 Retransmission Time. The time between retransmitted Neighbor
944 Solicitation messages. Used by address resolution and the Neighbor Unreachability
945 Detection algorithm. A value of zero is ignored and the kernel's current value
946 will be used. Defaults to unset, and the kernel's current value will be used.
</para>
948 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
953 <term><varname>IPv4ReversePathFilter=
</varname></term>
955 <para>Configure IPv4 Reverse Path Filtering. If enabled, when an IPv4 packet is received, the machine will first check
956 whether the
<emphasis>source
</emphasis> of the packet would be routed through the interface it came in. If there is no
957 route to the source on that interface, the machine will drop the packet. Takes one of
958 <literal>no
</literal>,
<literal>strict
</literal>, or
<literal>loose
</literal>. When
<literal>no
</literal>,
959 no source validation will be done. When
<literal>strict
</literal>, mode each incoming packet is tested against the FIB and
960 if the incoming interface is not the best reverse path, the packet check will fail. By default failed packets are discarded.
961 When
<literal>loose
</literal>, mode each incoming packet's source address is tested against the FIB. The packet is dropped
962 only if the source address is not reachable via any interface on that router.
963 See
<ulink url=
"https://tools.ietf.org/html/rfc1027">RFC
3704</ulink>.
964 When unset, the kernel's default will be used.
</para>
966 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
971 <term><varname>IPv4AcceptLocal=
</varname></term>
973 <para>Takes a boolean. Accept packets with local source addresses. In combination with
974 suitable routing, this can be used to direct packets between two local interfaces over the
975 wire and have them accepted properly. When unset, the kernel's default will be used.
</para>
977 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
982 <term><varname>IPv4RouteLocalnet=
</varname></term>
984 <para>Takes a boolean. When true, the kernel does not consider loopback addresses as martian
985 source or destination while routing. This enables the use of
127.0.0.0/
8 for local routing
986 purposes. When unset, the kernel's default will be used.
</para>
988 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
993 <term><varname>IPv4ProxyARP=
</varname></term>
995 <para>Takes a boolean. Configures proxy ARP for IPv4. Proxy ARP is the technique in which one
996 host, usually a router, answers ARP requests intended for another machine. By
"faking" its
997 identity, the router accepts responsibility for routing packets to the
"real" destination.
998 See
<ulink url=
"https://tools.ietf.org/html/rfc1027">RFC
1027</ulink>. When unset, the
999 kernel's default will be used.
</para>
1001 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
1006 <term><varname>IPv4ProxyARPPrivateVLAN=
</varname></term>
1008 <para>Takes a boolean. Configures proxy ARP private VLAN for IPv4, also known as VLAN aggregation,
1009 private VLAN, source-port filtering, port-isolation, or MAC-forced forwarding.
</para>
1011 <para>This variant of the ARP proxy technique will allow the ARP proxy to reply back to the same
1014 <para>See
<ulink url=
"https://tools.ietf.org/html/rfc3069">RFC
3069</ulink>. When unset,
1015 the kernel's default will be used.
</para>
1016 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
1021 <term><varname>IPv6ProxyNDP=
</varname></term>
1023 <para>Takes a boolean. Configures proxy NDP for IPv6. Proxy NDP (Neighbor Discovery Protocol)
1024 is a technique for IPv6 to allow routing of addresses to a different destination when peers
1025 expect them to be present on a certain physical link. In this case a router answers Neighbour
1026 Advertisement messages intended for another machine by offering its own MAC address as
1027 destination. Unlike proxy ARP for IPv4, it is not enabled globally, but will only send
1028 Neighbour Advertisement messages for addresses in the IPv6 neighbor proxy table, which can
1029 also be shown by
<command>ip -
6 neighbour show proxy
</command>. systemd-networkd will control
1030 the per-interface `proxy_ndp` switch for each configured interface depending on this option.
1031 When unset, the kernel's default will be used.
</para>
1033 <xi:include href=
"version-info.xml" xpointer=
"v234"/>
1038 <term><varname>IPv6ProxyNDPAddress=
</varname></term>
1040 <para>An IPv6 address, for which Neighbour Advertisement messages will be proxied. This
1041 option may be specified more than once. systemd-networkd will add the
1042 <varname>IPv6ProxyNDPAddress=
</varname> entries to the kernel's IPv6 neighbor proxy table.
1043 This setting implies
<varname>IPv6ProxyNDP=yes
</varname> but has no effect if
1044 <varname>IPv6ProxyNDP=
</varname> has been set to false. When unset, the kernel's default will
1047 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
1052 <term><varname>IPv6SendRA=
</varname></term>
1054 <para>Whether to enable or disable Router Advertisement sending on a link. Takes a boolean
1055 value. When enabled, prefixes configured in [IPv6Prefix] sections and routes configured in
1056 the [IPv6RoutePrefix] sections are distributed as defined in the [IPv6SendRA] section. If
1057 <varname>DHCPPrefixDelegation=
</varname> is enabled, then the delegated prefixes are also
1058 distributed. See
<varname>DHCPPrefixDelegation=
</varname> setting and the [IPv6SendRA],
1059 [IPv6Prefix], [IPv6RoutePrefix], and [DHCPPrefixDelegation] sections for more configuration
1062 <xi:include href=
"version-info.xml" xpointer=
"v247"/>
1067 <term><varname>DHCPPrefixDelegation=
</varname></term>
1069 <para>Takes a boolean value. When enabled, requests subnet prefixes on another link via the DHCPv6
1070 protocol or via the
6RD option in the DHCPv4 protocol. An address within each delegated prefix will
1071 be assigned, and the prefixes will be announced through IPv6 Router Advertisement if
1072 <varname>IPv6SendRA=
</varname> is enabled. This behaviour can be configured in the
1073 [DHCPPrefixDelegation] section. Defaults to disabled.
</para>
1075 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
1080 <term><varname>IPv6MTUBytes=
</varname></term>
1082 <para>Configures IPv6 maximum transmission unit (MTU). An integer greater than or equal to
1083 1280 bytes. When unset, the kernel's default will be used.
</para>
1085 <xi:include href=
"version-info.xml" xpointer=
"v239"/>
1090 <term><varname>KeepMaster=
</varname></term>
1092 <para>Takes a boolean value. When enabled, the current master interface index will not be
1093 changed, and
<varname>BatmanAdvanced=
</varname>,
<varname>Bond=
</varname>,
1094 <varname>Bridge=
</varname>, and
<varname>VRF=
</varname> settings are ignored. This may be
1095 useful when a netdev with a master interface is created by another program, e.g.
1096 <citerefentry><refentrytitle>systemd-nspawn
</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
1097 Defaults to false.
</para>
1099 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
1104 <term><varname>BatmanAdvanced=
</varname></term>
1105 <term><varname>Bond=
</varname></term>
1106 <term><varname>Bridge=
</varname></term>
1107 <term><varname>VRF=
</varname></term>
1109 <para>The name of the B.A.T.M.A.N. Advanced, bond, bridge, or VRF interface to add the link
1111 <citerefentry><refentrytitle>systemd.netdev
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
1114 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
1119 <term><varname>IPoIB=
</varname></term>
1120 <term><varname>IPVLAN=
</varname></term>
1121 <term><varname>IPVTAP=
</varname></term>
1122 <term><varname>MACsec=
</varname></term>
1123 <term><varname>MACVLAN=
</varname></term>
1124 <term><varname>MACVTAP=
</varname></term>
1125 <term><varname>Tunnel=
</varname></term>
1126 <term><varname>VLAN=
</varname></term>
1127 <term><varname>VXLAN=
</varname></term>
1128 <term><varname>Xfrm=
</varname></term>
1130 <para>The name of an IPoIB, IPVLAN, IPVTAP, MACsec, MACVLAN, MACVTAP, tunnel, VLAN,
1131 VXLAN, or Xfrm to be created on the link. See
1132 <citerefentry><refentrytitle>systemd.netdev
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
1133 This option may be specified more than once.
</para>
1135 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
1140 <term><varname>ActiveSlave=
</varname></term>
1142 <para>Takes a boolean. Specifies the new active slave. The
<literal>ActiveSlave=
</literal>
1143 option is only valid for following modes:
<literal>active-backup
</literal>,
1144 <literal>balance-alb
</literal>, and
<literal>balance-tlb
</literal>. Defaults to false.
</para>
1146 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1151 <term><varname>PrimarySlave=
</varname></term>
1153 <para>Takes a boolean. Specifies which slave is the primary device. The specified device will
1154 always be the active slave while it is available. Only when the primary is off-line will
1155 alternate devices be used. This is useful when one slave is preferred over another, e.g.
1156 when one slave has higher throughput than another. The
<literal>PrimarySlave=
</literal>
1157 option is only valid for following modes:
<literal>active-backup
</literal>,
1158 <literal>balance-alb
</literal>, and
<literal>balance-tlb
</literal>. Defaults to false.
</para>
1160 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1165 <term><varname>ConfigureWithoutCarrier=
</varname></term>
1167 <para>Takes a boolean. Allows networkd to configure a specific link even if it has no
1168 carrier. Defaults to false. If enabled, and the
<varname>IgnoreCarrierLoss=
</varname> setting
1169 is not explicitly set, then it is enabled as well.
</para>
1171 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1176 <term><varname>IgnoreCarrierLoss=
</varname></term>
1178 <para>Takes a boolean or a timespan. When true,
<command>systemd-networkd
</command> retains
1179 both the static and dynamic configuration of the interface even if its carrier is lost. When
1180 false,
<command>systemd-networkd
</command> drops both the static and dynamic configuration of
1181 the interface. When a timespan is specified,
<command>systemd-networkd
</command> waits for
1182 the specified timespan, and ignores the carrier loss if the link regain its carrier within
1183 the timespan. Setting
0 seconds is equivalent to
<literal>no
</literal>, and
1184 <literal>infinite
</literal> is equivalent to
<literal>yes
</literal>.
</para>
1186 <para>Setting a finite timespan may be useful when e.g. in the following cases:
1189 <para>A wireless interface connecting to a network which has multiple access points with
1190 the same SSID.
</para>
1193 <para>Enslaving a wireless interface to a bond interface, which may disconnect from the
1194 connected access point and causes its carrier to be lost.
</para>
1197 <para>The driver of the interface resets when the MTU is changed.
</para>
1202 <para>When
<varname>Bond=
</varname> is specified to a wireless interface, defaults to
3
1203 seconds. When the DHCPv4 client is enabled and
<varname>UseMTU=
</varname> in the [DHCPv4]
1204 section enabled, defaults to
5 seconds. Otherwise, defaults to the value specified with
1205 <varname>ConfigureWithoutCarrier=
</varname>. When
<varname>ActivationPolicy=
</varname> is set
1206 to
<literal>always-up
</literal>, this is forced to
<literal>yes
</literal>, and ignored any
1207 user specified values.
</para>
1209 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
1214 <term><varname>KeepConfiguration=
</varname></term>
1216 <para>Takes a boolean or one of
<literal>static
</literal>,
<literal>dhcp-on-stop
</literal>,
1217 <literal>dhcp
</literal>. When
<literal>static
</literal>,
<command>systemd-networkd
</command>
1218 will not drop static addresses and routes on starting up process. When set to
1219 <literal>dhcp-on-stop
</literal>,
<command>systemd-networkd
</command> will not drop addresses
1220 and routes on stopping the daemon. When
<literal>dhcp
</literal>,
1221 the addresses and routes provided by a DHCP server will never be dropped even if the DHCP
1222 lease expires. This is contrary to the DHCP specification, but may be the best choice if,
1223 e.g., the root filesystem relies on this connection. The setting
<literal>dhcp
</literal>
1224 implies
<literal>dhcp-on-stop
</literal>, and
<literal>yes
</literal> implies
1225 <literal>dhcp
</literal> and
<literal>static
</literal>. Defaults to
1226 <literal>dhcp-on-stop
</literal> when
<command>systemd-networkd
</command> is running in
1227 initrd,
<literal>yes
</literal> when the root filesystem is a network filesystem, and
1228 <literal>no
</literal> otherwise.
</para>
1230 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
1237 <title>[Address] Section Options
</title>
1239 <para>An [Address] section accepts the following keys. Specify several [Address] sections to
1240 configure several addresses.
</para>
1242 <variablelist class='network-directives'
>
1244 <term><varname>Address=
</varname></term>
1246 <para>As in the [Network] section. This setting is mandatory. Each [Address] section can
1247 contain one
<varname>Address=
</varname> setting.
</para>
1249 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
1254 <term><varname>Peer=
</varname></term>
1256 <para>The peer address in a point-to-point connection. Accepts the same format as the
1257 <varname>Address=
</varname> setting.
</para>
1259 <xi:include href=
"version-info.xml" xpointer=
"v216"/>
1264 <term><varname>Broadcast=
</varname></term>
1266 <para>Takes an IPv4 address or boolean value. The address must be in the format described in
1267 <citerefentry project='man-pages'
><refentrytitle>inet_pton
</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
1268 If set to true, then the IPv4 broadcast address will be derived from the
1269 <varname>Address=
</varname> setting. If set to false, then the broadcast address will not be
1270 set. Defaults to true, except for wireguard interfaces, where it default to false.
</para>
1272 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
1277 <term><varname>Label=
</varname></term>
1279 <para>Specifies the label for the IPv4 address. The label must be a
7-bit ASCII string with
1280 a length of
1…
15 characters. Defaults to unset.
</para>
1282 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
1287 <term><varname>PreferredLifetime=
</varname></term>
1289 <para>Allows the default
"preferred lifetime" of the address to be overridden. Only three
1290 settings are accepted:
<literal>forever
</literal>,
<literal>infinity
</literal>, which is the
1291 default and means that the address never expires, and
<literal>0</literal>, which means that
1292 the address is considered immediately
"expired" and will not be used, unless explicitly
1293 requested. A setting of
<option>PreferredLifetime=
0</option> is useful for addresses which
1294 are added to be used only by a specific application, which is then configured to use them
1297 <xi:include href=
"version-info.xml" xpointer=
"v230"/>
1302 <term><varname>Scope=
</varname></term>
1304 <para>The scope of the address, which can be
<literal>global
</literal> (valid everywhere on
1305 the network, even through a gateway),
<literal>link
</literal> (only valid on this device,
1306 will not traverse a gateway) or
<literal>host
</literal> (only valid within the device itself,
1307 e.g.
127.0.0.1) or an integer in the range
0…
255. Defaults to
<literal>global
</literal>.
1308 IPv4 only - IPv6 scope is automatically assigned by the kernel and cannot be set manually.
1311 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1316 <term><varname>RouteMetric=
</varname></term>
1318 <para>The metric of the prefix route, which is pointing to the subnet of the configured IP
1319 address, taking the configured prefix length into account. Takes an unsigned integer in the
1320 range
0…
4294967295. When unset or set to
0, the kernel's default value is used. This
1321 setting will be ignored when
<varname>AddPrefixRoute=
</varname> is false.
</para>
1323 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
1328 <term><varname>HomeAddress=
</varname></term>
1330 <para>Takes a boolean. Designates this address the
"home address" as defined in
1331 <ulink url=
"https://tools.ietf.org/html/rfc6275">RFC
6275</ulink>. Supported only on IPv6.
1332 Defaults to false.
</para>
1334 <xi:include href=
"version-info.xml" xpointer=
"v232"/>
1339 <term><varname>DuplicateAddressDetection=
</varname></term>
1341 <para>Takes one of
<literal>ipv4
</literal>,
<literal>ipv6
</literal>,
<literal>both
</literal>,
1342 or
<literal>none
</literal>. When
<literal>ipv4
</literal>, performs IPv4 Address Conflict
1343 Detection. See
<ulink url=
"https://tools.ietf.org/html/rfc5227">RFC
5227</ulink>.
1344 When
<literal>ipv6
</literal>, performs IPv6 Duplicate Address Detection. See
1345 <ulink url=
"https://tools.ietf.org/html/rfc4862">RFC
4862</ulink>. Defaults to
1346 <literal>ipv4
</literal> for IPv4 link-local addresses,
<literal>ipv6
</literal> for IPv6
1347 addresses, and
<literal>none
</literal> otherwise.
</para>
1349 <xi:include href=
"version-info.xml" xpointer=
"v232"/>
1354 <term><varname>ManageTemporaryAddress=
</varname></term>
1356 <para>Takes a boolean. If true the kernel manage temporary addresses created from this one as
1357 template on behalf of Privacy Extensions
1358 <ulink url=
"https://tools.ietf.org/html/rfc3041">RFC
3041</ulink>. For this to become active,
1359 the use_tempaddr sysctl setting has to be set to a value greater than zero. The given address
1360 needs to have a prefix length of
64. This flag allows using privacy extensions in a manually
1361 configured network, just like if stateless auto-configuration was active. Defaults to false.
1364 <xi:include href=
"version-info.xml" xpointer=
"v232"/>
1369 <term><varname>AddPrefixRoute=
</varname></term>
1371 <para>Takes a boolean. When true, the prefix route for the address is automatically added.
1372 Defaults to true.
</para>
1374 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
1379 <term><varname>AutoJoin=
</varname></term>
1381 <para>Takes a boolean. Joining multicast group on ethernet level via
1382 <command>ip maddr
</command> command would not work if we have an Ethernet switch that does
1383 IGMP snooping since the switch would not replicate multicast packets on ports that did not
1384 have IGMP reports for the multicast addresses. Linux vxlan interfaces created via
1385 <command>ip link add vxlan
</command> or networkd's netdev kind vxlan have the group option
1386 that enables them to do the required join. By extending
<command>ip address
</command> command
1387 with option
<literal>autojoin
</literal> we can get similar functionality for openvswitch (OVS)
1388 vxlan interfaces as well as other tunneling mechanisms that need to receive multicast traffic.
1389 Defaults to
<literal>no
</literal>.
</para>
1391 <xi:include href=
"version-info.xml" xpointer=
"v232"/>
1396 <term><varname>NetLabel=
</varname><replaceable>label
</replaceable></term>
1399 <para>This setting provides a method for integrating static and dynamic network configuration into
1400 Linux
<ulink url=
"https://docs.kernel.org/netlabel/index.html">NetLabel
</ulink> subsystem rules,
1401 used by
<ulink url=
"https://en.wikipedia.org/wiki/Linux_Security_Modules">Linux Security Modules
1402 (LSMs)
</ulink> for network access control. The label, with suitable LSM rules, can be used to
1403 control connectivity of (for example) a service with peers in the local network. At least with
1404 SELinux, only the ingress can be controlled but not egress. The benefit of using this setting is
1405 that it may be possible to apply interface independent part of NetLabel configuration at very early
1406 stage of system boot sequence, at the time when the network interfaces are not available yet, with
1408 project='man-pages'
><refentrytitle>netlabelctl
</refentrytitle><manvolnum>8</manvolnum></citerefentry>,
1409 and the per-interface configuration with
<command>systemd-networkd
</command> once the interfaces
1410 appear later. Currently this feature is only implemented for SELinux.
</para>
1412 <para>The option expects a single NetLabel label. The label must conform to lexical restrictions of
1413 LSM labels. When an interface is configured with IP addresses, the addresses and subnetwork masks
1414 will be appended to the
<ulink
1415 url=
"https://github.com/SELinuxProject/selinux-notebook/blob/main/src/network_support.md">NetLabel
1416 Fallback Peer Labeling
</ulink> rules. They will be removed when the interface is
1417 deconfigured. Failures to manage the labels will be ignored.
</para>
1420 <para>Once labeling is enabled for network traffic, a lot of LSM access control points in
1421 Linux networking stack go from dormant to active. Care should be taken to avoid getting into a
1422 situation where for example remote connectivity is broken, when the security policy hasn't been
1423 updated to consider LSM per-packet access controls and no rules would allow any network
1424 traffic. Also note that additional configuration with
<citerefentry
1425 project='man-pages'
><refentrytitle>netlabelctl
</refentrytitle><manvolnum>8</manvolnum></citerefentry>
1430 <programlisting>[Address]
1431 NetLabel=system_u:object_r:localnet_peer_t:s0
</programlisting>
1433 With the example rules applying for interface
<literal>eth0
</literal>, when the interface is
1434 configured with an IPv4 address of
10.0.0.123/
8,
<command>systemd-networkd
</command> performs the
1435 equivalent of
<command>netlabelctl
</command> operation
1437 <programlisting>netlabelctl unlbl add interface eth0 address:
10.0.0.0/
8 label:system_u:object_r:localnet_peer_t:s0
</programlisting>
1439 and the reverse operation when the IPv4 address is deconfigured. The configuration can be used with
1440 LSM rules; in case of SELinux to allow a SELinux domain to receive data from objects of SELinux
1441 <literal>peer
</literal> class. For example:
1443 <programlisting>type localnet_peer_t;
1444 allow my_server_t localnet_peer_t:peer recv;
</programlisting>
1446 The effect of the above configuration and rules (in absence of other rules as may be the case) is
1447 to only allow
<literal>my_server_t
</literal> (and nothing else) to receive data from local subnet
1448 10.0.0.0/
8 of interface
<literal>eth0
</literal>.
1451 <xi:include href=
"version-info.xml" xpointer=
"v252"/>
1456 <term><varname>NFTSet=
</varname><replaceable>source
</replaceable>:
<replaceable>family
</replaceable>:
<replaceable>table
</replaceable>:
<replaceable>set
</replaceable></term>
1458 <para>This setting provides a method for integrating network configuration into firewall rules with
1459 <ulink url=
"https://netfilter.org/projects/nftables/index.html">NFT
</ulink> sets. The benefit of
1460 using the setting is that static network configuration (or dynamically obtained network addresses,
1461 see similar directives in other sections) can be used in firewall rules with the indirection of NFT
1462 set types. For example, access could be granted for hosts in the local subnetwork only. Firewall
1463 rules using IP address of an interface are also instantly updated when the network configuration
1464 changes, for example via DHCP.
</para>
1466 <para>This option expects a whitespace separated list of NFT set definitions. Each definition
1467 consists of a colon-separated tuple of source type (one of
<literal>address
</literal>,
1468 <literal>prefix
</literal> or
<literal>ifindex
</literal>), NFT address family (one of
1469 <literal>arp
</literal>,
<literal>bridge
</literal>,
<literal>inet
</literal>,
<literal>ip
</literal>,
1470 <literal>ip6
</literal>, or
<literal>netdev
</literal>), table name and set name. The names of tables
1471 and sets must conform to lexical restrictions of NFT table names. The type of the element used in
1472 the NFT filter must match the type implied by the directive (
<literal>address
</literal>,
1473 <literal>prefix
</literal> or
<literal>ifindex
</literal>) and address type (IPv4 or IPv6) as shown
1474 in the table below.
</para>
1477 <title>Defined
<varname>source type
</varname> values
</title>
1479 <colspec colname='source type'
/>
1480 <colspec colname='description'
/>
1481 <colspec colname='NFT type name'
/>
1484 <entry>Source type
</entry>
1485 <entry>Description
</entry>
1486 <entry>Corresponding NFT type name
</entry>
1492 <entry><literal>address
</literal></entry>
1493 <entry>host IP address
</entry>
1494 <entry><literal>ipv4_addr
</literal> or
<literal>ipv6_addr
</literal></entry>
1497 <entry><literal>prefix
</literal></entry>
1498 <entry>network prefix
</entry>
1499 <entry><literal>ipv4_addr
</literal> or
<literal>ipv6_addr
</literal>, with
<literal>flags interval
</literal></entry>
1502 <entry><literal>ifindex
</literal></entry>
1503 <entry>interface index
</entry>
1504 <entry><literal>iface_index
</literal></entry>
1510 <para>When an interface is configured with IP addresses, the addresses, subnetwork masks or
1511 interface index will be appended to the NFT sets. The information will be removed when the
1512 interface is deconfigured.
<command>systemd-networkd
</command> only inserts elements to (or removes
1513 from) the sets, so the related NFT rules, tables and sets must be prepared elsewhere in
1514 advance. Failures to manage the sets will be ignored.
</para>
1517 <programlisting>[Address]
1518 NFTSet=prefix:netdev:filter:eth_ipv4_prefix
</programlisting>
1519 Corresponding NFT rules:
1520 <programlisting>table netdev filter {
1521 set eth_ipv4_prefix {
1526 type filter hook ingress device
"eth0" priority filter; policy drop;
1527 ip daddr != @eth_ipv4_prefix drop
1533 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
1540 <title>[Neighbor] Section Options
</title>
1542 <para>A [Neighbor] section accepts the following keys. The neighbor section adds a permanent,
1543 static entry to the neighbor table (IPv6) or ARP table (IPv4) for the given hardware address on the
1544 links matched for the network. Specify several [Neighbor] sections to configure several static
1547 <variablelist class='network-directives'
>
1549 <term><varname>Address=
</varname></term>
1551 <para>The IP address of the neighbor.
</para>
1553 <xi:include href=
"version-info.xml" xpointer=
"v240"/>
1558 <term><varname>LinkLayerAddress=
</varname></term>
1560 <para>The link layer address (MAC address or IP address) of the neighbor.
</para>
1562 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
1569 <title>[IPv6AddressLabel] Section Options
</title>
1571 <para>An [IPv6AddressLabel] section accepts the following keys. Specify several [IPv6AddressLabel]
1572 sections to configure several address labels. IPv6 address labels are used for address selection.
1573 See
<ulink url=
"https://tools.ietf.org/html/rfc3484">RFC
3484</ulink>. Precedence is managed by
1574 userspace, and only the label itself is stored in the kernel.
</para>
1576 <variablelist class='network-directives'
>
1578 <term><varname>Label=
</varname></term>
1580 <para>The label for the prefix, an unsigned integer in the range
0…
4294967294.
0xffffffff is
1581 reserved. This setting is mandatory.
</para>
1583 <xi:include href=
"version-info.xml" xpointer=
"v234"/>
1588 <term><varname>Prefix=
</varname></term>
1590 <para>IPv6 prefix is an address with a prefix length, separated by a slash
1591 <literal>/
</literal> character. This setting is mandatory.
</para>
1593 <xi:include href=
"version-info.xml" xpointer=
"v234"/>
1600 <title>[RoutingPolicyRule] Section Options
</title>
1602 <para>An [RoutingPolicyRule] section accepts the following settings. Specify several
1603 [RoutingPolicyRule] sections to configure several rules.
</para>
1605 <variablelist class='network-directives'
>
1607 <term><varname>TypeOfService=
</varname></term>
1610 This specifies the Type of Service (ToS) field of packets to match;
1611 it takes an unsigned integer in the range
0…
255.
1612 The field can be used to specify precedence (the first
3 bits) and ToS (the next
3 bits).
1613 The field can be also used to specify Differentiated Services Code Point (DSCP) (the first
6 bits) and
1614 Explicit Congestion Notification (ECN) (the last
2 bits).
1615 See
<ulink url=
"https://en.wikipedia.org/wiki/Type_of_service">Type of Service
</ulink>
1616 and
<ulink url=
"https://en.wikipedia.org/wiki/Differentiated_services">Differentiated services
</ulink>
1620 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1625 <term><varname>From=
</varname></term>
1627 <para>Specifies the source address prefix to match. Possibly followed by a slash and the
1628 prefix length.
</para>
1630 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1635 <term><varname>To=
</varname></term>
1637 <para>Specifies the destination address prefix to match. Possibly followed by a slash and the
1638 prefix length.
</para>
1640 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1645 <term><varname>FirewallMark=
</varname></term>
1647 <para>Specifies the iptables firewall mark value to match (a number in the range
1648 1…
4294967295). Optionally, the firewall mask (also a number between
1…
4294967295) can be
1649 suffixed with a slash (
<literal>/
</literal>), e.g.,
<literal>7/
255</literal>.
</para>
1651 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1656 <term><varname>Table=
</varname></term>
1658 <para>Specifies the routing table identifier to look up if the rule selector matches. Takes
1659 one of predefined names
<literal>default
</literal>,
<literal>main
</literal>, and
1660 <literal>local
</literal>, and names defined in
<varname>RouteTable=
</varname> in
1661 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
1662 or a number between
1 and
4294967295. Defaults to
<literal>main
</literal>.
</para>
1664 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1669 <term><varname>Priority=
</varname></term>
1671 <para>Specifies the priority of this rule.
<varname>Priority=
</varname> is an integer in the
1672 range
0…
4294967295. Higher number means lower priority, and rules get processed in order of
1673 increasing number. Defaults to unset, and the kernel will pick a value dynamically.
</para>
1675 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
1680 <term><varname>IncomingInterface=
</varname></term>
1682 <para>Specifies incoming device to match. If the interface is loopback, the rule only matches
1683 packets originating from this host.
</para>
1685 <xi:include href=
"version-info.xml" xpointer=
"v236"/>
1690 <term><varname>OutgoingInterface=
</varname></term>
1692 <para>Specifies the outgoing device to match. The outgoing interface is only available for
1693 packets originating from local sockets that are bound to a device.
</para>
1695 <xi:include href=
"version-info.xml" xpointer=
"v236"/>
1700 <term><varname>L3MasterDevice=
</varname></term>
1702 <para>A boolean. Specifies whether the rule is to direct lookups to the tables associated with
1703 level
3 master devices (also known as Virtual Routing and Forwarding or VRF devices).
1704 For further details see
<ulink url=
"https://docs.kernel.org/networking/vrf.html">
1705 Virtual Routing and Forwarding (VRF)
</ulink>. Defaults to false.
</para>
1707 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
1712 <term><varname>SourcePort=
</varname></term>
1714 <para>Specifies the source IP port or IP port range match in forwarding information base
1715 (FIB) rules. A port range is specified by the lower and upper port separated by a dash.
1716 Defaults to unset.
</para>
1718 <xi:include href=
"version-info.xml" xpointer=
"v240"/>
1723 <term><varname>DestinationPort=
</varname></term>
1725 <para>Specifies the destination IP port or IP port range match in forwarding information base
1726 (FIB) rules. A port range is specified by the lower and upper port separated by a dash.
1727 Defaults to unset.
</para>
1729 <xi:include href=
"version-info.xml" xpointer=
"v240"/>
1734 <term><varname>IPProtocol=
</varname></term>
1736 <para>Specifies the IP protocol to match in forwarding information base (FIB) rules. Takes IP
1737 protocol name such as
<literal>tcp
</literal>,
<literal>udp
</literal> or
1738 <literal>sctp
</literal>, or IP protocol number such as
<literal>6</literal> for
1739 <literal>tcp
</literal> or
<literal>17</literal> for
<literal>udp
</literal>. Defaults to unset.
1742 <xi:include href=
"version-info.xml" xpointer=
"v240"/>
1747 <term><varname>InvertRule=
</varname></term>
1749 <para>A boolean. Specifies whether the rule is to be inverted. Defaults to false.
</para>
1751 <xi:include href=
"version-info.xml" xpointer=
"v240"/>
1756 <term><varname>Family=
</varname></term>
1758 <para>Takes a special value
<literal>ipv4
</literal>,
<literal>ipv6
</literal>, or
1759 <literal>both
</literal>. By default, the address family is determined by the address
1760 specified in
<varname>To=
</varname> or
<varname>From=
</varname>. If neither
1761 <varname>To=
</varname> nor
<varname>From=
</varname> are specified, then defaults to
1762 <literal>ipv4
</literal>.
</para>
1764 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
1769 <term><varname>User=
</varname></term>
1771 <para>Takes a username, a user ID, or a range of user IDs separated by a dash. Defaults to
1774 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
1779 <term><varname>SuppressPrefixLength=
</varname></term>
1781 <para>Takes a number
<replaceable>N
</replaceable> in the range
0…
128 and rejects routing
1782 decisions that have a prefix length of
<replaceable>N
</replaceable> or less. Defaults to
1785 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
1790 <term><varname>SuppressInterfaceGroup=
</varname></term>
1792 <para>Takes an integer in the range
0…
2147483647 and rejects routing decisions that have
1793 an interface with the same group id. It has the same meaning as
1794 <option>suppress_ifgroup
</option> in
<command>ip rule
</command>. Defaults to unset.
</para>
1796 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
1801 <term><varname>Type=
</varname></term>
1803 <para>Specifies Routing Policy Database (RPDB) rule type. Takes one of
1804 <literal>blackhole
</literal>,
<literal>unreachable
</literal> or
<literal>prohibit
</literal>.
1807 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
1814 <title>[NextHop] Section Options
</title>
1816 <para>The [NextHop] section is used to manipulate entries in the kernel's
"nexthop" tables. The
1817 [NextHop] section accepts the following settings. Specify several [NextHop] sections to configure
1818 several hops.
</para>
1820 <variablelist class='network-directives'
>
1822 <term><varname>Id=
</varname></term>
1824 <para>The id of the next hop. Takes an integer in the range
1…
4294967295.
1825 This is mandatory if
<varname>ManageForeignNextHops=no
</varname> is specified in
1826 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
1827 Otherwise, if unspecified, an unused ID will be automatically picked.
</para>
1829 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
1834 <term><varname>Gateway=
</varname></term>
1836 <para>As in the [Network] section.
</para>
1838 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
1843 <term><varname>Family=
</varname></term>
1845 <para>Takes one of the special values
<literal>ipv4
</literal> or
<literal>ipv6
</literal>.
1846 By default, the family is determined by the address specified in
1847 <varname>Gateway=
</varname>. If
<varname>Gateway=
</varname> is not specified, then defaults
1848 to
<literal>ipv4
</literal>.
</para>
1850 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
1855 <term><varname>OnLink=
</varname></term>
1857 <para>Takes a boolean. If set to true, the kernel does not have to check if the gateway is
1858 reachable directly by the current machine (i.e., attached to the local network), so that we
1859 can insert the nexthop in the kernel table without it being complained about. Defaults to
1860 <literal>no
</literal>.
</para>
1862 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
1867 <term><varname>Blackhole=
</varname></term>
1869 <para>Takes a boolean. If enabled, packets to the corresponding routes are discarded
1870 silently, and
<varname>Gateway=
</varname> cannot be specified. Defaults to
1871 <literal>no
</literal>.
</para>
1873 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
1878 <term><varname>Group=
</varname></term>
1880 <para>Takes a whitespace separated list of nexthop IDs. Each ID must be in the range
1881 1…
4294967295. Optionally, each nexthop ID can take a weight after a colon
1882 (
<literal><replaceable>id
</replaceable><optional>:
<replaceable>weight
</replaceable></optional></literal>).
1883 The weight must be in the range
1…
255. If the weight is not specified, then it is assumed
1884 that the weight is
1. This setting cannot be specified with
<varname>Gateway=
</varname>,
1885 <varname>Family=
</varname>,
<varname>Blackhole=
</varname>. This setting can be specified
1886 multiple times. If an empty string is assigned, then the all previous assignments are
1887 cleared. Defaults to unset.
</para>
1889 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
1896 <title>[Route] Section Options
</title>
1898 <para>The [Route] section accepts the following settings. Specify several [Route] sections to
1899 configure several routes.
</para>
1901 <variablelist class='network-directives'
>
1903 <term><varname>Gateway=
</varname></term>
1905 <para>Takes the gateway address or the special values
<literal>_dhcp4
</literal> and
1906 <literal>_ipv6ra
</literal>. If
<literal>_dhcp4
</literal> or
<literal>_ipv6ra
</literal> is
1907 set, then the gateway address provided by DHCPv4 or IPv6 RA is used.
</para>
1909 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
1914 <term><varname>GatewayOnLink=
</varname></term>
1916 <para>Takes a boolean. If set to true, the kernel does not have to check if the gateway is
1917 reachable directly by the current machine (i.e., attached to the local network), so that we
1918 can insert the route in the kernel table without it being complained about. Defaults to
1919 <literal>no
</literal>.
</para>
1921 <xi:include href=
"version-info.xml" xpointer=
"v234"/>
1926 <term><varname>Destination=
</varname></term>
1928 <para>The destination prefix of the route. Possibly followed by a slash and the prefix
1929 length. If omitted, a full-length host route is assumed.
</para>
1931 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
1936 <term><varname>Source=
</varname></term>
1938 <para>The source prefix of the route. Possibly followed by a slash and the prefix length. If
1939 omitted, a full-length host route is assumed.
</para>
1941 <xi:include href=
"version-info.xml" xpointer=
"v218"/>
1946 <term><varname>Metric=
</varname></term>
1948 <para>The metric of the route. Takes an unsigned integer in the range
0…
4294967295. Defaults
1949 to unset, and the kernel's default will be used.
</para>
1951 <xi:include href=
"version-info.xml" xpointer=
"v216"/>
1956 <term><varname>IPv6Preference=
</varname></term>
1958 <para>Specifies the route preference as defined in
1959 <ulink url=
"https://tools.ietf.org/html/rfc4191">RFC
4191</ulink> for Router Discovery
1960 messages. Which can be one of
<literal>low
</literal> the route has a lowest priority,
1961 <literal>medium
</literal> the route has a default priority or
<literal>high
</literal> the
1962 route has a highest priority.
</para>
1964 <xi:include href=
"version-info.xml" xpointer=
"v234"/>
1969 <term><varname>Scope=
</varname></term>
1971 <para>The scope of the IPv4 route, which can be
<literal>global
</literal>,
1972 <literal>site
</literal>,
<literal>link
</literal>,
<literal>host
</literal>, or
1973 <literal>nowhere
</literal>:
</para>
1976 <para><literal>global
</literal> means the route can reach hosts more than one hop away.
1981 <para><literal>site
</literal> means an interior route in the local autonomous system.
1986 <para><literal>link
</literal> means the route can only reach hosts on the local network
1987 (one hop away).
</para>
1991 <para><literal>host
</literal> means the route will not leave the local machine (used for
1992 internal addresses like
127.0.0.1).
</para>
1996 <para><literal>nowhere
</literal> means the destination doesn't exist.
</para>
2000 <para>For IPv4 route, defaults to
<literal>host
</literal> if
<varname>Type=
</varname> is
2001 <literal>local
</literal> or
<literal>nat
</literal>, and
<literal>link
</literal> if
2002 <varname>Type=
</varname> is
<literal>broadcast
</literal>,
<literal>multicast
</literal>,
2003 <literal>anycast
</literal>, or
<literal>unicast
</literal>. In other cases,
2004 defaults to
<literal>global
</literal>. The value is not used for IPv6.
</para>
2006 <xi:include href=
"version-info.xml" xpointer=
"v219"/>
2011 <term><varname>PreferredSource=
</varname></term>
2013 <para>The preferred source address of the route. The address must be in the format described
2015 <citerefentry project='man-pages'
><refentrytitle>inet_pton
</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
2018 <xi:include href=
"version-info.xml" xpointer=
"v227"/>
2023 <term><varname>Table=
</varname></term>
2025 <para>The table identifier for the route. Takes one of predefined names
2026 <literal>default
</literal>,
<literal>main
</literal>, and
<literal>local
</literal>, and names
2027 defined in
<varname>RouteTable=
</varname> in
2028 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
2029 or a number between
1 and
4294967295. The table can be retrieved using
2030 <command>ip route show table
<replaceable>num
</replaceable></command>. If unset and
2031 <varname>Type=
</varname> is
<literal>local
</literal>,
<literal>broadcast
</literal>,
2032 <literal>anycast
</literal>, or
<literal>nat
</literal>, then
<literal>local
</literal> is used.
2033 In other cases, defaults to
<literal>main
</literal>. Ignored if
<varname>L3MasterDevice=
</varname> is true.
</para>
2035 <xi:include href=
"version-info.xml" xpointer=
"v230"/>
2040 <term><varname>HopLimit=
</varname></term>
2042 <para>Configures per route hop limit. Takes an integer in the range
1…
255. See also
2043 <varname>IPv6HopLimit=
</varname>.
</para>
2045 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2050 <term><varname>Protocol=
</varname></term>
2052 <para>The protocol identifier for the route. Takes a number between
0 and
255 or the special
2053 values
<literal>kernel
</literal>,
<literal>boot
</literal>,
<literal>static
</literal>,
2054 <literal>ra
</literal> and
<literal>dhcp
</literal>. Defaults to
<literal>static
</literal>.
2057 <xi:include href=
"version-info.xml" xpointer=
"v234"/>
2062 <term><varname>Type=
</varname></term>
2064 <para>Specifies the type for the route. Takes one of
<literal>unicast
</literal>,
2065 <literal>local
</literal>,
<literal>broadcast
</literal>,
<literal>anycast
</literal>,
2066 <literal>multicast
</literal>,
<literal>blackhole
</literal>,
<literal>unreachable
</literal>,
2067 <literal>prohibit
</literal>,
<literal>throw
</literal>,
<literal>nat
</literal>, and
2068 <literal>xresolve
</literal>. If
<literal>unicast
</literal>, a regular route is defined, i.e.
2069 a route indicating the path to take to a destination network address. If
2070 <literal>blackhole
</literal>, packets to the defined route are discarded silently. If
2071 <literal>unreachable
</literal>, packets to the defined route are discarded and the ICMP
2072 message
"Host Unreachable" is generated. If
<literal>prohibit
</literal>, packets to the
2073 defined route are discarded and the ICMP message
"Communication Administratively Prohibited"
2074 is generated. If
<literal>throw
</literal>, route lookup in the current routing table will
2075 fail and the route selection process will return to Routing Policy Database (RPDB). Defaults
2076 to
<literal>unicast
</literal>.
</para>
2078 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
2083 <term><varname>InitialCongestionWindow=
</varname></term>
2085 <para>The TCP initial congestion window is used during the start of a TCP connection.
2086 During the start of a TCP session, when a client requests a resource, the server's initial
2087 congestion window determines how many packets will be sent during the initial burst of data
2088 without waiting for acknowledgement. Takes a number between
1 and
1023. Note that
100 is
2089 considered an extremely large value for this option. When unset, the kernel's default
2090 (typically
10) will be used.
</para>
2092 <xi:include href=
"version-info.xml" xpointer=
"v237"/>
2097 <term><varname>InitialAdvertisedReceiveWindow=
</varname></term>
2099 <para>The TCP initial advertised receive window is the amount of receive data (in bytes)
2100 that can initially be buffered at one time on a connection. The sending host can send only
2101 that amount of data before waiting for an acknowledgment and window update from the
2102 receiving host. Takes a number between
1 and
1023. Note that
100 is considered an extremely
2103 large value for this option. When unset, the kernel's default will be used.
</para>
2105 <xi:include href=
"version-info.xml" xpointer=
"v237"/>
2110 <term><varname>QuickAck=
</varname></term>
2112 <para>Takes a boolean. When true, the TCP quick ACK mode for the route is enabled. When unset,
2113 the kernel's default will be used.
</para>
2115 <xi:include href=
"version-info.xml" xpointer=
"v237"/>
2120 <term><varname>FastOpenNoCookie=
</varname></term>
2122 <para>Takes a boolean. When true enables TCP fastopen without a cookie on a per-route basis.
2123 When unset, the kernel's default will be used.
</para>
2125 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
2130 <term><varname>MTUBytes=
</varname></term>
2132 <para>The maximum transmission unit in bytes to set for the route. The usual suffixes K, M,
2133 G, are supported and are understood to the base of
1024.
</para>
2135 <xi:include href=
"version-info.xml" xpointer=
"v239"/>
2140 <term><varname>TCPAdvertisedMaximumSegmentSize=
</varname></term>
2142 <para>Specifies the Path MSS (in bytes) hints given on TCP layer. The usual suffixes K, M, G,
2143 are supported and are understood to the base of
1024. An unsigned integer in the range
2144 1…
4294967294. When unset, the kernel's default will be used.
</para>
2146 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
2151 <term><varname>TCPCongestionControlAlgorithm=
</varname></term>
2153 <para>Specifies the TCP congestion control algorithm for the route. Takes a name of the algorithm,
2154 e.g.
<literal>bbr
</literal>,
<literal>dctcp
</literal>, or
<literal>vegas
</literal>. When unset,
2155 the kernel's default will be used.
</para>
2157 <xi:include href=
"version-info.xml" xpointer=
"v252"/>
2162 <term><varname>TCPRetransmissionTimeoutSec=
</varname></term>
2164 <para>Specifies the TCP Retransmission Timeout (RTO) for the route. Takes time values in seconds.
2165 This value specifies the timeout of an alive TCP connection, when retransmissions remain
2166 unacknowledged. When unset, the kernel's default will be used.
</para>
2168 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2173 <term><varname>MultiPathRoute=
<replaceable>address
</replaceable>[@
<replaceable>name
</replaceable>] [
<replaceable>weight
</replaceable>]
</varname></term>
2175 <para>Configures multipath route. Multipath routing is the technique of using multiple
2176 alternative paths through a network. Takes gateway address. Optionally, takes a network
2177 interface name or index separated with
<literal>@
</literal>, and a weight in
1.
.256 for this
2178 multipath route separated with whitespace. This setting can be specified multiple times. If
2179 an empty string is assigned, then the all previous assignments are cleared.
</para>
2181 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
2186 <term><varname>NextHop=
</varname></term>
2188 <para>Specifies the nexthop id. Takes an unsigned integer in the range
1…
4294967295. If set,
2189 the corresponding [NextHop] section must be configured. Defaults to unset.
</para>
2191 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
2198 <title>[DHCPv4] Section Options
</title>
2200 <para>The [DHCPv4] section configures the DHCPv4 client, if it is enabled with the
2201 <varname>DHCP=
</varname> setting described above:
</para>
2203 <variablelist class='network-directives'
>
2205 <!-- DHCP packet contents -->
2208 <term><varname>RequestAddress=
</varname></term>
2210 <para>Takes an IPv4 address. When specified, the Requested IP Address option (option code
50) is
2211 added with it to the initial DHCPDISCOVER message sent by the DHCP client. Defaults to unset, and
2212 an already assigned dynamic address to the interface is automatically picked.
</para>
2214 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2219 <term><varname>SendHostname=
</varname></term>
2221 <para>When true (the default), the machine's hostname (or the value specified with
2222 <varname>Hostname=
</varname>, described below) will be sent to the DHCP server. Note that the
2223 hostname must consist only of
7-bit ASCII lower-case characters and no spaces or dots, and be
2224 formatted as a valid DNS domain name. Otherwise, the hostname is not sent even if this option
2227 <xi:include href=
"version-info.xml" xpointer=
"v215"/>
2232 <term><varname>Hostname=
</varname></term>
2234 <para>Use this value for the hostname which is sent to the DHCP server, instead of machine's
2235 hostname. Note that the specified hostname must consist only of
7-bit ASCII lower-case
2236 characters and no spaces or dots, and be formatted as a valid DNS domain name.
</para>
2238 <xi:include href=
"version-info.xml" xpointer=
"v223"/>
2243 <term><varname>MUDURL=
</varname></term>
2245 <para>When configured, the specified Manufacturer Usage Description (MUD) URL will be sent
2246 to the DHCPv4 server. Takes a URL of length up to
255 characters. A superficial verification
2247 that the string is a valid URL will be performed. DHCPv4 clients are intended to have at most
2248 one MUD URL associated with them. See
2249 <ulink url=
"https://tools.ietf.org/html/rfc8520">RFC
8520</ulink>.
</para>
2251 <para>MUD is an embedded software standard defined by the IETF that allows IoT device makers
2252 to advertise device specifications, including the intended communication patterns for their
2253 device when it connects to the network. The network can then use this to author a
2254 context-specific access policy, so the device functions only within those parameters.
</para>
2256 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2261 <term><varname>ClientIdentifier=
</varname></term>
2263 <para>The DHCPv4 client identifier to use. Takes one of
<option>mac
</option> or
2264 <option>duid
</option>. If set to
<option>mac
</option>, the MAC address of the link is used. If set
2265 to
<option>duid
</option>, an RFC4361-compliant Client ID, which is the combination of IAID and
2266 DUID, is used. IAID can be configured by
<varname>IAID=
</varname>. DUID can be configured by
2267 <varname>DUIDType=
</varname> and
<varname>DUIDRawData=
</varname>. Defaults to
2268 <option>duid
</option>.
</para>
2270 <xi:include href=
"version-info.xml" xpointer=
"v220"/>
2275 <term><varname>VendorClassIdentifier=
</varname></term>
2277 <para>The vendor class identifier used to identify vendor type and configuration.
</para>
2279 <xi:include href=
"version-info.xml" xpointer=
"v216"/>
2284 <term><varname>UserClass=
</varname></term>
2286 <para>A DHCPv4 client can use UserClass option to identify the type or category of user or
2287 applications it represents. The information contained in this option is a string that
2288 represents the user class of which the client is a member. Each class sets an identifying
2289 string of information to be used by the DHCP service to classify clients. Takes a
2290 whitespace-separated list of strings.
</para>
2292 <xi:include href=
"version-info.xml" xpointer=
"v239"/>
2297 <term><varname>DUIDType=
</varname></term>
2299 <para>Override the global
<varname>DUIDType=
</varname> setting for this network. See
2300 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
2301 for a description of possible values.
</para>
2303 <xi:include href=
"version-info.xml" xpointer=
"v230"/>
2308 <term><varname>DUIDRawData=
</varname></term>
2310 <para>Override the global
<varname>DUIDRawData=
</varname> setting for this network. See
2311 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>
2312 for a description of possible values.
</para>
2314 <xi:include href=
"version-info.xml" xpointer=
"v230"/>
2319 <term><varname>IAID=
</varname></term>
2321 <para>The DHCP Identity Association Identifier (IAID) for the interface, a
32-bit unsigned
2324 <xi:include href=
"version-info.xml" xpointer=
"v230"/>
2329 <term><varname>RapidCommit=
</varname></term>
2331 <para>Takes a boolean. The DHCPv4 client can obtain configuration parameters from a DHCPv4 server
2332 through a rapid two-message exchange (discover and ack). When the rapid commit option is set by
2333 both the DHCPv4 client and the DHCPv4 server, the two-message exchange is used. Otherwise, the
2334 four-message exchange (discover, offer, request, and ack) is used. The two-message exchange
2335 provides faster client configuration. See
2336 <ulink url=
"https://tools.ietf.org/html/rfc4039">RFC
4039</ulink> for details.
2337 Defaults to true when
<varname>Anonymize=no
</varname> and neither
<varname>AllowList=
</varname>
2338 nor
<varname>DenyList=
</varname> is specified, and false otherwise.
</para>
2340 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2345 <term><varname>Anonymize=
</varname></term>
2347 <para>Takes a boolean. When true, the options sent to the DHCP server will follow the
2348 <ulink url=
"https://tools.ietf.org/html/rfc7844">RFC
7844</ulink> (Anonymity Profiles for
2349 DHCP Clients) to minimize disclosure of identifying information. Defaults to false.
</para>
2351 <para>This option should only be set to true when
<varname>MACAddressPolicy=
</varname> is set
2352 to
<option>random
</option> (see
2353 <citerefentry><refentrytitle>systemd.link
</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
2357 <varname>ClientIdentifier=mac
</varname>,
2358 <varname>RapidCommit=no
</varname>,
2359 <varname>SendHostname=no
</varname>,
2360 <varname>Use6RD=no
</varname>,
2361 <varname>UseCaptivePortal=no
</varname>,
2362 <varname>UseMTU=no
</varname>,
2363 <varname>UseNTP=no
</varname>,
2364 <varname>UseSIP=no
</varname>, and
2365 <varname>UseTimezone=no
</varname>
2366 are implied and these settings in the .network file are silently ignored. Also,
2367 <varname>Hostname=
</varname>,
2368 <varname>MUDURL=
</varname>,
2369 <varname>RequestAddress=
</varname>,
2370 <varname>RequestOptions=
</varname>,
2371 <varname>SendOption=
</varname>,
2372 <varname>SendVendorOption=
</varname>,
2373 <varname>UserClass=
</varname>, and
2374 <varname>VendorClassIdentifier=
</varname>
2375 are silently ignored.
</para>
2377 <para>With this option enabled DHCP requests will mimic those generated by Microsoft
2378 Windows, in order to reduce the ability to fingerprint and recognize installations. This
2379 means DHCP request sizes will grow and lease data will be more comprehensive than normally,
2380 though most of the requested data is not actually used.
</para>
2382 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
2387 <term><varname>RequestOptions=
</varname></term>
2389 <para>Sets request options to be sent to the server in the DHCPv4 request options list. A
2390 whitespace-separated list of integers in the range
1…
254. Defaults to unset.
</para>
2392 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
2397 <term><varname>SendOption=
</varname></term>
2399 <para>Send an arbitrary raw option in the DHCPv4 request. Takes a DHCP option number, data
2400 type and data separated with a colon
2401 (
<literal><replaceable>option
</replaceable>:
<replaceable>type
</replaceable>:
<replaceable>value
</replaceable></literal>).
2402 The option number must be an integer in the range
1…
254. The type takes one of
2403 <literal>uint8
</literal>,
<literal>uint16
</literal>,
<literal>uint32
</literal>,
2404 <literal>ipv4address
</literal>, or
<literal>string
</literal>. Special characters in the data
2405 string may be escaped using
2406 <ulink url=
"https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
2407 escapes
</ulink>. This setting can be specified multiple times. If an empty string is
2408 specified, then all options specified earlier are cleared. Defaults to unset.
</para>
2410 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
2415 <term><varname>SendVendorOption=
</varname></term>
2417 <para>Send an arbitrary vendor option in the DHCPv4 request. Takes a DHCP option number, data
2418 type and data separated with a colon
2419 (
<literal><replaceable>option
</replaceable>:
<replaceable>type
</replaceable>:
<replaceable>value
</replaceable></literal>).
2420 The option number must be an integer in the range
1…
254. The type takes one of
2421 <literal>uint8
</literal>,
<literal>uint16
</literal>,
<literal>uint32
</literal>,
2422 <literal>ipv4address
</literal>, or
<literal>string
</literal>. Special characters in the data
2423 string may be escaped using
2424 <ulink url=
"https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
2425 escapes
</ulink>. This setting can be specified multiple times. If an empty string is specified,
2426 then all options specified earlier are cleared. Defaults to unset.
</para>
2428 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2433 <term><varname>IPServiceType=
</varname></term>
2435 <para>Takes one of the special values
<literal>none
</literal>,
<literal>CS6
</literal>, or
2436 <literal>CS4
</literal>. When
<literal>none
</literal> no IP service type is set to the packet
2437 sent from the DHCPv4 client. When
<literal>CS6
</literal> (network control) or
2438 <literal>CS4
</literal> (realtime), the corresponding service type will be set. Defaults to
2439 <literal>CS6
</literal>.
</para>
2441 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
2446 <term><varname>SocketPriority=
</varname></term>
2448 <para>The Linux socket option
<constant>SO_PRIORITY
</constant> applied to the raw IP socket used for
2449 initial DHCPv4 messages. Unset by default. Usual values range from
0 to
6.
2450 More details about
<constant>SO_PRIORITY
</constant> socket option in
2451 <citerefentry project='man-pages'
><refentrytitle>socket
</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
2452 Can be used in conjunction with [VLAN] section
<varname>EgressQOSMaps=
</varname> setting of .netdev
2453 file to set the
802.1Q VLAN ethernet tagged header priority, see
2454 <citerefentry><refentrytitle>systemd.netdev
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
2457 <xi:include href=
"version-info.xml" xpointer=
"v253"/>
2461 <!-- How to use the DHCP lease -->
2464 <term><varname>Label=
</varname></term>
2466 <para>Specifies the label for the IPv4 address received from the DHCP server. The label must
2467 be a
7-bit ASCII string with a length of
1…
15 characters. Defaults to unset.
</para>
2469 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
2474 <term><varname>UseDNS=
</varname></term>
2476 <para>When true (the default), the DNS servers received from the DHCP server will be used.
2479 <para>This corresponds to the
<option>nameserver
</option> option in
2480 <citerefentry project='man-pages'
><refentrytitle>resolv.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
2483 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
2488 <term><varname>RoutesToDNS=
</varname></term>
2490 <para>When true, the routes to the DNS servers received from the DHCP server will be
2491 configured. When
<varname>UseDNS=
</varname> is disabled, this setting is ignored. Defaults to
2494 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
2499 <term><varname>UseNTP=
</varname></term>
2501 <para>When true (the default), the NTP servers received from the DHCP server will be used by
2502 <filename>systemd-timesyncd.service
</filename>.
</para>
2504 <xi:include href=
"version-info.xml" xpointer=
"v220"/>
2509 <term><varname>RoutesToNTP=
</varname></term>
2511 <para>When true, the routes to the NTP servers received from the DHCP server will be
2512 configured. When
<varname>UseNTP=
</varname> is disabled, this setting is ignored. Defaults to
2515 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
2520 <term><varname>UseSIP=
</varname></term>
2522 <para>When true (the default), the SIP servers received from the DHCP server will be collected
2523 and made available to client programs.
</para>
2525 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
2530 <term><varname>UseCaptivePortal=
</varname></term>
2532 <para>When true (the default), the captive portal advertised by the DHCP server will be recorded
2533 and made available to client programs and displayed in the
2534 <citerefentry><refentrytitle>networkctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
2535 status output per-link.
</para>
2537 <xi:include href=
"version-info.xml" xpointer=
"v254"/>
2542 <term><varname>UseMTU=
</varname></term>
2544 <para>When true, the interface maximum transmission unit from the DHCP server will be used on
2545 the current link. If
<varname>MTUBytes=
</varname> is set, then this setting is ignored.
2546 Defaults to false.
</para>
2548 <para>Note, some drivers will reset the interfaces if the MTU is changed. For such
2549 interfaces, please try to use
<varname>IgnoreCarrierLoss=
</varname> with a short timespan,
2550 e.g.
<literal>3 seconds
</literal>.
</para>
2552 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
2557 <term><varname>UseHostname=
</varname></term>
2559 <para>When true (the default), the hostname received from the DHCP server will be set as the
2560 transient hostname of the system.
</para>
2562 <xi:include href=
"version-info.xml" xpointer=
"v211"/>
2567 <term><varname>UseDomains=
</varname></term>
2569 <para>Takes a boolean, or the special value
<option>route
</option>. When true, the domain name
2570 received from the DHCP server will be used as DNS search domain over this link, similarly to the
2571 effect of the
<option>Domains=
</option> setting. If set to
<option>route
</option>, the domain name
2572 received from the DHCP server will be used for routing DNS queries only, but not for searching,
2573 similarly to the effect of the
<option>Domains=
</option> setting when the argument is prefixed with
2574 <literal>~
</literal>. When unspecified, the value specified in the same setting in
2575 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
2576 which defaults to
<literal>no
</literal>, will be used.
</para>
2578 <para>It is recommended to enable this option only on trusted networks, as setting this
2579 affects resolution of all hostnames, in particular of single-label names. It is generally
2580 safer to use the supplied domain only as routing domain, rather than as search domain, in
2581 order to not have it affect local resolution of single-label names.
</para>
2583 <para>When set to true, this setting corresponds to the
<option>domain
</option> option in
2584 <citerefentry project='man-pages'
><refentrytitle>resolv.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
2587 <xi:include href=
"version-info.xml" xpointer=
"v216"/>
2592 <term><varname>UseRoutes=
</varname></term>
2594 <para>When true (the default), the static routes will be requested from the DHCP server and
2595 added to the routing table with a metric of
1024, and a scope of
<option>global
</option>,
2596 <option>link
</option> or
<option>host
</option>, depending on the route's destination and
2597 gateway. If the destination is on the local host, e.g.,
127.x.x.x, or the same as the link's
2598 own address, the scope will be set to
<option>host
</option>. Otherwise if the gateway is null
2599 (a direct route), a
<option>link
</option> scope will be used. For anything else, scope
2600 defaults to
<option>global
</option>.
</para>
2602 <xi:include href=
"version-info.xml" xpointer=
"v215"/>
2607 <term><varname>RouteMetric=
</varname></term>
2609 <para>Set the routing metric for routes specified by the DHCP server (including the prefix
2610 route added for the specified prefix). Takes an unsigned integer in the range
0…
4294967295.
2611 Defaults to
1024.
</para>
2613 <xi:include href=
"version-info.xml" xpointer=
"v217"/>
2618 <term><varname>RouteTable=
<replaceable>num
</replaceable></varname></term>
2620 <para>The table identifier for DHCP routes. Takes one of predefined names
2621 <literal>default
</literal>,
<literal>main
</literal>, and
<literal>local
</literal>, and names
2622 defined in
<varname>RouteTable=
</varname> in
2623 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
2624 or a number between
1…
4294967295.
</para>
2626 <para>When used in combination with
<varname>VRF=
</varname>, the VRF's routing table is
2627 used when this parameter is not specified.
</para>
2629 <xi:include href=
"version-info.xml" xpointer=
"v232"/>
2634 <term><varname>RouteMTUBytes=
</varname></term>
2636 <para>Specifies the MTU for the DHCP routes. Please see the [Route] section for further
2639 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
2644 <term><varname>QuickAck=
</varname></term>
2646 <para>Takes a boolean. When true, the TCP quick ACK mode is enabled for the routes configured by
2647 the acquired DHCPv4 lease. When unset, the kernel's default will be used.
</para>
2649 <xi:include href=
"version-info.xml" xpointer=
"v253"/>
2654 <term><varname>InitialCongestionWindow=
</varname></term>
2656 <para>As in the [Route] section.
</para>
2658 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2663 <term><varname>InitialAdvertisedReceiveWindow=
</varname></term>
2665 <para>As in the [Route] section.
</para>
2667 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2672 <term><varname>UseGateway=
</varname></term>
2674 <para>When true, and the DHCP server provides a Router option, the default gateway based on the
2675 router address will be configured. Defaults to unset, and the value specified with
2676 <varname>UseRoutes=
</varname> will be used.
</para>
2678 <para>Note, when the server provides both the Router and Classless Static Routes option, and
2679 <varname>UseRoutes=
</varname> is enabled, the Router option is always ignored regardless of this
2680 setting. See
<ulink url=
"https://datatracker.ietf.org/doc/html/rfc3442">RFC
3442</ulink>.
</para>
2682 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2687 <term><varname>UseTimezone=
</varname></term>
2688 <listitem><para>When true, the timezone received from the DHCP server will be set as timezone
2689 of the local system. Defaults to false.
</para>
2691 <xi:include href=
"version-info.xml" xpointer=
"v226"/></listitem>
2695 <term><varname>Use6RD=
</varname></term>
2697 <para>When true, subnets of the received IPv6 prefix are assigned to downstream interfaces
2698 which enables
<varname>DHCPPrefixDelegation=
</varname>. See also
2699 <varname>DHCPPrefixDelegation=
</varname> in the [Network] section, the [DHCPPrefixDelegation]
2700 section, and
<ulink url=
"https://tools.ietf.org/html/rfc5969">RFC
5969</ulink>. Defaults to
2703 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
2708 <term><varname>IPv6OnlyMode=
</varname></term>
2710 <para>When true, the DHCPv4 configuration will be delayed by the timespan provided by the DHCP
2711 server and skip to configure dynamic IPv4 network connectivity if IPv6 connectivity is provided
2712 within the timespan. See
<ulink url=
"https://tools.ietf.org/html/rfc8925">RFC
8925</ulink>.
2713 Defaults to false.
</para>
2715 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2720 <term><varname>FallbackLeaseLifetimeSec=
</varname></term>
2722 <para>Allows one to set DHCPv4 lease lifetime when DHCPv4 server does not send the lease
2723 lifetime. Takes one of
<literal>forever
</literal> or
<literal>infinity
</literal>. If
2724 specified, the acquired address never expires. Defaults to unset.
</para>
2726 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2730 <!-- How to communicate with the server -->
2733 <term><varname>RequestBroadcast=
</varname></term>
2735 <para>Request the server to use broadcast messages before the IP address has been configured.
2736 This is necessary for devices that cannot receive RAW packets, or that cannot receive packets
2737 at all before an IP address has been configured. On the other hand, this must not be enabled
2738 on networks where broadcasts are filtered out.
</para>
2740 <xi:include href=
"version-info.xml" xpointer=
"v216"/>
2745 <term><varname>MaxAttempts=
</varname></term>
2747 <para>Specifies how many times the DHCPv4 client configuration should be attempted. Takes a
2748 number or
<literal>infinity
</literal>. Defaults to
<literal>infinity
</literal>. Note that the
2749 time between retries is increased exponentially, up to approximately one per minute, so the
2750 network will not be overloaded even if this number is high. The default is suitable in most
2751 circumstances.
</para>
2753 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
2758 <term><varname>ListenPort=
</varname></term>
2760 <para>Set the port from which the DHCP client packets originate.
</para>
2762 <xi:include href=
"version-info.xml" xpointer=
"v233"/>
2767 <term><varname>ServerPort=
</varname></term>
2769 <para>Set the port on which the DHCP server is listening.
</para>
2771 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
2776 <term><varname>DenyList=
</varname></term>
2778 <para>A whitespace-separated list of IPv4 addresses. Each address can optionally take a
2779 prefix length after
<literal>/
</literal>. DHCP offers from servers in the list are rejected.
2780 Note that if
<varname>AllowList=
</varname> is configured then
<varname>DenyList=
</varname> is
2782 <para>Note that this filters only DHCP offers, so the filtering may not work when
2783 <varname>RapidCommit=
</varname> is enabled. See also
<varname>RapidCommit=
</varname> in the above.
2786 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2791 <term><varname>AllowList=
</varname></term>
2793 <para>A whitespace-separated list of IPv4 addresses. Each address can optionally take a
2794 prefix length after
<literal>/
</literal>. DHCP offers from servers in the list are accepted.
2796 <para>Note that this filters only DHCP offers, so the filtering may not work when
2797 <varname>RapidCommit=
</varname> is enabled. See also
<varname>RapidCommit=
</varname> in the above.
2800 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2805 <term><varname>SendRelease=
</varname></term>
2807 <para>When true, the DHCPv4 client sends a DHCP release packet when it stops. Defaults to
2810 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
2815 <term><varname>SendDecline=
</varname></term>
2817 <para>A boolean. When true,
<command>systemd-networkd
</command> performs IPv4 Duplicate
2818 Address Detection to the acquired address by the DHCPv4 client. If duplicate is detected,
2819 the DHCPv4 client rejects the address by sending a
<constant>DHCPDECLINE
</constant> packet to
2820 the DHCP server, and tries to obtain an IP address again. See
2821 <ulink url=
"https://tools.ietf.org/html/rfc5227">RFC
5227</ulink>. Defaults to false.
</para>
2823 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
2828 <term><varname>NetLabel=
</varname></term>
2830 <para>This applies the NetLabel for the addresses received with DHCP, like
2831 <varname>NetLabel=
</varname> in [Address] section applies it to statically configured
2832 addresses. See
<varname>NetLabel=
</varname> in [Address] section for more details.
</para>
2834 <xi:include href=
"version-info.xml" xpointer=
"v252"/>
2839 <term><varname>NFTSet=
</varname></term>
2841 <para>This applies the NFT set for the network configuration received with DHCP, like
2842 <varname>NFTSet=
</varname> in [Address] section applies it to static configuration. See
2843 <varname>NFTSet=
</varname> in [Address] section for more details. For
<literal>address
</literal> or
2844 <literal>prefix
</literal> source types, the type of the element used in the NFT filter must be
2845 <literal>ipv4_addr
</literal>.
</para>
2847 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2854 <title>[DHCPv6] Section Options
</title>
2856 <para>The [DHCPv6] section configures the DHCPv6 client, if it is enabled with the
2857 <varname>DHCP=
</varname> setting described above, or invoked by the IPv6 Router Advertisement:
2860 <variablelist class='network-directives'
>
2862 <!-- DHCP packet contents -->
2865 <term><varname>MUDURL=
</varname></term>
2866 <term><varname>IAID=
</varname></term>
2867 <term><varname>DUIDType=
</varname></term>
2868 <term><varname>DUIDRawData=
</varname></term>
2869 <term><varname>RequestOptions=
</varname></term>
2871 <para>As in the [DHCPv4] section.
</para>
2873 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2878 <term><varname>SendOption=
</varname></term>
2880 <para>As in the [DHCPv4] section, however because DHCPv6 uses
16-bit fields to store option
2881 numbers, the option number is an integer in the range
1…
65536.
</para>
2883 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2888 <term><varname>SendVendorOption=
</varname></term>
2890 <para>Send an arbitrary vendor option in the DHCPv6 request. Takes an enterprise identifier,
2891 DHCP option number, data type, and data separated with a colon
2892 (
<literal><replaceable>enterprise identifier
</replaceable>:
<replaceable>option
</replaceable>:
<replaceable>type
</replaceable>:
<replaceable>value
</replaceable></literal>).
2893 Enterprise identifier is an unsigned integer in the range
1…
4294967294. The option number
2894 must be an integer in the range
1…
254. Data type takes one of
<literal>uint8
</literal>,
2895 <literal>uint16
</literal>,
<literal>uint32
</literal>,
<literal>ipv4address
</literal>,
2896 <literal>ipv6address
</literal>, or
<literal>string
</literal>. Special characters in the data
2897 string may be escaped using
2898 <ulink url=
"https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
2899 escapes
</ulink>. This setting can be specified multiple times. If an empty string is
2900 specified, then all options specified earlier are cleared. Defaults to unset.
</para>
2902 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2907 <term><varname>UserClass=
</varname></term>
2909 <para>A DHCPv6 client can use User Class option to identify the type or category of user or
2910 applications it represents. The information contained in this option is a string that
2911 represents the user class of which the client is a member. Each class sets an identifying
2912 string of information to be used by the DHCP service to classify clients. Special characters
2913 in the data string may be escaped using
2914 <ulink url=
"https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
2915 escapes
</ulink>. This setting can be specified multiple times. If an empty string is
2916 specified, then all options specified earlier are cleared. Takes a whitespace-separated list
2917 of strings. Note that currently
<constant>NUL
</constant> bytes are not allowed.
</para>
2919 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2924 <term><varname>VendorClass=
</varname></term>
2926 <para>A DHCPv6 client can use VendorClass option to identify the vendor that manufactured the
2927 hardware on which the client is running. The information contained in the data area of this
2928 option is contained in one or more opaque fields that identify details of the hardware
2929 configuration. Takes a whitespace-separated list of strings.
</para>
2931 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
2936 <term><varname>PrefixDelegationHint=
</varname></term>
2938 <para>Takes an IPv6 address with prefix length in the same format as the
2939 <varname>Address=
</varname> in the [Network] section. The DHCPv6 client will include a prefix
2940 hint in the DHCPv6 solicitation sent to the server. The prefix length must be in the range
2941 1…
128. Defaults to unset.
</para>
2943 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
2948 <term><varname>RapidCommit=
</varname></term>
2950 <para>Takes a boolean. The DHCPv6 client can obtain configuration parameters from a DHCPv6 server
2951 through a rapid two-message exchange (solicit and reply). When the rapid commit option is set by
2952 both the DHCPv6 client and the DHCPv6 server, the two-message exchange is used. Otherwise, the
2953 four-message exchange (solicit, advertise, request, and reply) is used. The two-message exchange
2954 provides faster client configuration. See
2955 <ulink url=
"https://tools.ietf.org/html/rfc3315#section-17.2.1">RFC
3315</ulink> for details.
2956 Defaults to true, and the two-message exchange will be used if the server support it.
</para>
2958 <xi:include href=
"version-info.xml" xpointer=
"v252"/>
2963 <term><varname>SendHostname=
</varname></term>
2965 <para>When true (the default), the machine's hostname (or the value specified with
2966 <varname>Hostname=
</varname>, described below) will be sent to the DHCPv6 server. Note that the
2967 hostname must consist only of
7-bit ASCII lower-case characters and no spaces or dots, and be
2968 formatted as a valid DNS domain name. Otherwise, the hostname is not sent even if this option
2971 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2976 <term><varname>Hostname=
</varname></term>
2978 <para>Use this value for the hostname which is sent to the DHCPv6 server, instead of machine's
2979 hostname. Note that the specified hostname must consist only of
7-bit ASCII lower-case
2980 characters and no spaces or dots, and be formatted as a valid DNS domain name.
</para>
2982 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
2986 <!-- How to use the DHCP lease -->
2989 <term><varname>UseAddress=
</varname></term>
2991 <para>When true (the default), the IP addresses provided by the DHCPv6 server will be
2994 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
2999 <term><varname>UseCaptivePortal=
</varname></term>
3001 <para>When true (the default), the captive portal advertised by the DHCPv6 server will be recorded
3002 and made available to client programs and displayed in the
3003 <citerefentry><refentrytitle>networkctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
3004 status output per-link.
</para>
3006 <xi:include href=
"version-info.xml" xpointer=
"v254"/>
3011 <term><varname>UseDelegatedPrefix=
</varname></term>
3013 <para>When true (the default), the client will request the DHCPv6 server to delegate
3014 prefixes. If the server provides prefixes to be delegated, then subnets of the prefixes are
3015 assigned to the interfaces that have
<varname>DHCPPrefixDelegation=yes
</varname>.
3016 See also the
<varname>DHCPPrefixDelegation=
</varname> setting in the [Network] section,
3017 settings in the [DHCPPrefixDelegation] section, and
3018 <ulink url=
"https://www.rfc-editor.org/rfc/rfc8415.html#section-6.3">RFC
8415</ulink>.
3021 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
3026 <term><varname>UseDNS=
</varname></term>
3027 <term><varname>UseNTP=
</varname></term>
3028 <term><varname>UseHostname=
</varname></term>
3029 <term><varname>UseDomains=
</varname></term>
3030 <term><varname>NetLabel=
</varname></term>
3031 <term><varname>SendRelease=
</varname></term>
3033 <para>As in the [DHCPv4] section.
</para>
3035 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
3040 <term><varname>NFTSet=
</varname></term>
3042 <para>This applies the NFT set for the network configuration received with DHCP, like
3043 <varname>NFTSet=
</varname> in [Address] section applies it to static configuration. See
3044 <varname>NFTSet=
</varname> in [Address] section for more details. For
<literal>address
</literal>
3045 or
<literal>prefix
</literal> source types, the type of the element used in the NFT filter must be
3046 <literal>ipv6_addr
</literal>.
</para>
3048 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
3052 <!-- How to communicate with the server -->
3055 <term><varname>WithoutRA=
</varname></term>
3057 <para>Allows DHCPv6 client to start without router advertisements's
3058 <literal>managed
</literal> or
<literal>other configuration
</literal> flag. Takes one of
3059 <literal>no
</literal>,
<literal>solicit
</literal>, or
3060 <literal>information-request
</literal>. If this is not specified,
3061 <literal>solicit
</literal> is used when
<varname>DHCPPrefixDelegation=
</varname> is enabled
3062 and
<varname>UplinkInterface=:self
</varname> is specified in the [DHCPPrefixDelegation]
3063 section. Otherwise, defaults to
<literal>no
</literal>, and the DHCPv6 client will be started
3064 when an RA is received. See also the
<varname>DHCPv6Client=
</varname> setting in the
3065 [IPv6AcceptRA] section.
</para>
3067 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
3074 <title>[DHCPPrefixDelegation] Section Options
</title>
3075 <para>The [DHCPPrefixDelegation] section configures subnet prefixes of the delegated prefixes
3076 acquired by a DHCPv6 client or by a DHCPv4 client through the
6RD option on another interface.
3077 The settings in this section are used only when the
<varname>DHCPPrefixDelegation=
</varname>
3078 setting in the [Network] section is enabled.
</para>
3080 <variablelist class='network-directives'
>
3082 <term><varname>UplinkInterface=
</varname></term>
3084 <para>Specifies the name or the index of the uplink interface, or one of the special values
3085 <literal>:self
</literal> and
<literal>:auto
</literal>. When
<literal>:self
</literal>, the
3086 interface itself is considered the uplink interface, and
3087 <varname>WithoutRA=solicit
</varname> is implied if the setting is not explicitly specified.
3088 When
<literal>:auto
</literal>, the first link which acquired prefixes to be delegated from
3089 the DHCPv6 or DHCPv4 server is selected. Defaults to
<literal>:auto
</literal>.
</para>
3091 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
3096 <term><varname>SubnetId=
</varname></term>
3098 <para>Configure a specific subnet ID on the interface from a (previously) received prefix
3099 delegation. You can either set
"auto" (the default) or a specific subnet ID (as defined in
3100 <ulink url=
"https://tools.ietf.org/html/rfc4291#section-2.5.4">RFC
4291</ulink>, section
3101 2.5.4), in which case the allowed value is hexadecimal, from
0 to
0x7fffffffffffffff
3104 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
3109 <term><varname>Announce=
</varname></term>
3111 <para>Takes a boolean. When enabled, and
<varname>IPv6SendRA=
</varname> in [Network] section
3112 is enabled, the delegated prefixes are distributed through the IPv6 Router Advertisement.
3113 This setting will be ignored when the
<varname>DHCPPrefixDelegation=
</varname> setting is
3114 enabled on the upstream interface. Defaults to yes.
</para>
3116 <xi:include href=
"version-info.xml" xpointer=
"v247"/>
3121 <term><varname>Assign=
</varname></term>
3123 <para>Takes a boolean. Specifies whether to add an address from the delegated prefixes which
3124 are received from the WAN interface by the DHCPv6 Prefix Delegation. When true (on LAN
3125 interface), the EUI-
64 algorithm will be used by default to form an interface identifier from
3126 the delegated prefixes. See also
<varname>Token=
</varname> setting below. Defaults to yes.
3129 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
3134 <term><varname>Token=
</varname></term>
3136 <para>Specifies an optional address generation mode for assigning an address in each
3137 delegated prefix. This accepts the same syntax as
<varname>Token=
</varname> in the
3138 [IPv6AcceptRA] section. If
<varname>Assign=
</varname> is set to false, then this setting will
3139 be ignored. Defaults to unset, which means the EUI-
64 algorithm will be used.
</para>
3141 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
3146 <term><varname>ManageTemporaryAddress=
</varname></term>
3148 <para>As in the [Address] section, but defaults to true.
</para>
3150 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
3155 <term><varname>RouteMetric=
</varname></term>
3157 <para>The metric of the route to the delegated prefix subnet. Takes an unsigned integer in
3158 the range
0…
4294967295. When set to
0, the kernel's default value is used. Defaults to
256.
3161 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
3166 <term><varname>NetLabel=
</varname></term>
3168 <para>This applies the NetLabel for the addresses received with DHCP, like
3169 <varname>NetLabel=
</varname> in [Address] section applies it to statically configured
3170 addresses. See
<varname>NetLabel=
</varname> in [Address] section for more details.
</para>
3172 <xi:include href=
"version-info.xml" xpointer=
"v252"/>
3177 <term><varname>NFTSet=
</varname></term>
3179 <para>This applies the NFT set for the network configuration received with DHCP, like
3180 <varname>NFTSet=
</varname> in [Address] section applies it to static configuration. See
3181 <varname>NFTSet=
</varname> in [Address] section for more details. For
<literal>address
</literal> or
3182 <literal>prefix
</literal> source types, the type of the element used in the NFT filter must be
3183 <literal>ipv6_addr
</literal>.
</para>
3185 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
3192 <title>[IPv6AcceptRA] Section Options
</title>
3193 <para>The [IPv6AcceptRA] section configures the IPv6 Router Advertisement (RA) client, if it is enabled
3194 with the
<varname>IPv6AcceptRA=
</varname> setting described above:
</para>
3196 <variablelist class='network-directives'
>
3198 <term><varname>UseRedirect=
</varname></term>
3200 <para>When true (the default), Redirect message sent by the current first-hop router will be
3201 accepted, and configures routes to redirected nodes will be configured.
</para>
3203 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
3208 <term><varname>Token=
</varname></term>
3210 <para>Specifies an optional address generation mode for the Stateless Address
3211 Autoconfiguration (SLAAC). The following values are supported:
</para>
3215 <term><option>eui64
</option></term>
3218 The EUI-
64 algorithm will be used to generate an address for that prefix. Only
3219 supported by Ethernet or InfiniBand interfaces.
3222 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
3226 <term><option>static:
<replaceable>ADDRESS
</replaceable></option></term>
3229 An IPv6 address must be specified after a colon (
<literal>:
</literal>), and the
3230 lower bits of the supplied address are combined with the upper bits of a prefix
3231 received in a Router Advertisement (RA) message to form a complete address. Note
3232 that if multiple prefixes are received in an RA message, or in multiple RA messages,
3233 addresses will be formed from each of them using the supplied address. This mode
3234 implements SLAAC but uses a static interface identifier instead of an identifier
3235 generated by using the EUI-
64 algorithm. Because the interface identifier is static,
3236 if Duplicate Address Detection detects that the computed address is a duplicate
3237 (in use by another node on the link), then this mode will fail to provide an address
3238 for that prefix. If an IPv6 address without mode is specified, then
3239 <literal>static
</literal> mode is assumed.
3242 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
3246 <term><option>prefixstable[:
<replaceable>ADDRESS
</replaceable>][,
<replaceable>UUID
</replaceable>]
</option></term>
3249 The algorithm specified in
3250 <ulink url=
"https://tools.ietf.org/html/rfc7217">RFC
7217</ulink> will be used to
3251 generate interface identifiers. This mode can optionally take an IPv6 address
3252 separated with a colon (
<literal>:
</literal>). If an IPv6 address is specified,
3253 then an interface identifier is generated only when a prefix received in an RA
3254 message matches the supplied address.
3257 This mode can also optionally take a non-null UUID in the format which
3258 <function>sd_id128_from_string()
</function> accepts, e.g.
3259 <literal>86b123b969ba4b7eb8b3d8605123525a
</literal> or
3260 <literal>86b123b9-
69ba-
4b7e-b8b3-d8605123525a
</literal>. If a UUID is specified, the
3261 value is used as the secret key to generate interface identifiers. If not specified,
3262 then an application specific ID generated with the system's machine-ID will be used
3263 as the secret key. See
3264 <citerefentry><refentrytitle>sd-id128
</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
3265 <citerefentry><refentrytitle>sd_id128_from_string
</refentrytitle><manvolnum>3</manvolnum></citerefentry>,
3267 <citerefentry><refentrytitle>sd_id128_get_machine
</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
3270 Note that the
<literal>prefixstable
</literal> algorithm uses both the interface
3271 name and MAC address as input to the hash to compute the interface identifier, so
3272 if either of those are changed the resulting interface identifier (and address)
3273 will be changed, even if the prefix received in the RA message has not been
3277 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
3282 <para>If no address generation mode is specified (which is the default), or a received
3283 prefix does not match any of the addresses provided in
<literal>prefixstable
</literal>
3284 mode, then the EUI-
64 algorithm will be used for Ethernet or InfiniBand interfaces,
3285 otherwise
<literal>prefixstable
</literal> will be used to form an interface identifier for
3288 <para>This setting can be specified multiple times. If an empty string is assigned, then
3289 the all previous assignments are cleared.
</para>
3292 <programlisting>Token=eui64
3294 Token=static:::
1a:
2b:
3c:
4d
3296 Token=prefixstable:
2002:da8:
1::
</programlisting></para>
3298 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
3303 <term><varname>UseDNS=
</varname></term>
3305 <para>When true (the default), the DNS servers received in the Router Advertisement will be used.
</para>
3307 <para>This corresponds to the
<option>nameserver
</option> option in
<citerefentry
3308 project='man-pages'
><refentrytitle>resolv.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
3310 <xi:include href=
"version-info.xml" xpointer=
"v231"/>
3315 <term><varname>UseDomains=
</varname></term>
3317 <para>Takes a boolean, or the special value
<literal>route
</literal>. When true, the domain name
3318 received via IPv6 Router Advertisement (RA) will be used as DNS search domain over this link,
3319 similarly to the effect of the
<option>Domains=
</option> setting. If set to
3320 <literal>route
</literal>, the domain name received via IPv6 RA will be used for routing DNS queries
3321 only, but not for searching, similarly to the effect of the
<option>Domains=
</option> setting when
3322 the argument is prefixed with
<literal>~
</literal>. Defaults to false.
</para>
3324 <para>It is recommended to enable this option only on trusted networks, as setting this affects resolution
3325 of all hostnames, in particular of single-label names. It is generally safer to use the supplied domain
3326 only as routing domain, rather than as search domain, in order to not have it affect local resolution of
3327 single-label names.
</para>
3329 <para>When set to true, this setting corresponds to the
<option>domain
</option> option in
<citerefentry
3330 project='man-pages'
><refentrytitle>resolv.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
3332 <xi:include href=
"version-info.xml" xpointer=
"v231"/>
3337 <term><varname>RouteTable=
<replaceable>num
</replaceable></varname></term>
3339 <para>The table identifier for the routes received in the Router Advertisement. Takes one of
3340 predefined names
<literal>default
</literal>,
<literal>main
</literal>, and
<literal>local
</literal>,
3341 and names defined in
<varname>RouteTable=
</varname> in
3342 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
3343 or a number between
1…
4294967295.
</para>
3345 <para>When used in combination with
<varname>VRF=
</varname>, the VRF's routing table is
3346 used when this parameter is not specified.
</para>
3348 <xi:include href=
"version-info.xml" xpointer=
"v232"/>
3353 <term><varname>RouteMetric=
</varname></term>
3355 <para>Set the routing metric for the routes received in the Router Advertisement. Takes an unsigned
3356 integer in the range
0…
4294967295, or three unsigned integer separated with
<literal>:
</literal>,
3357 in that case the first one is used when the router preference is high, the second is for medium
3358 preference, and the last is for low preference
3359 (
<literal><replaceable>high
</replaceable>:
<replaceable>medium
</replaceable>:
<replaceable>low
</replaceable></literal>).
3360 Defaults to
<literal>512:
1024:
2048</literal>.
</para>
3362 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
3367 <term><varname>QuickAck=
</varname></term>
3369 <para>Takes a boolean. When true, the TCP quick ACK mode is enabled for the routes configured by
3370 the received RAs. When unset, the kernel's default will be used.
</para>
3372 <xi:include href=
"version-info.xml" xpointer=
"v253"/>
3377 <term><varname>UseMTU=
</varname></term>
3379 <para>Takes a boolean. When true, the MTU received in the Router Advertisement will be
3380 used. Defaults to true.
</para>
3382 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
3387 <term><varname>UseHopLimit=
</varname></term>
3389 <para>Takes a boolean. When true, the hop limit received in the Router Advertisement will be set to routes
3390 configured based on the advertisement. See also
<varname>IPv6HopLimit=
</varname>. Defaults to true.
</para>
3392 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
3397 <term><varname>UseReachableTime=
</varname></term>
3399 <para>Takes a boolean. When true, the reachable time received in the Router Advertisement will be
3400 set on the interface receiving the advertisement. It is used as the base timespan of the validity
3401 of a neighbor entry. Defaults to true.
</para>
3403 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
3408 <term><varname>UseRetransmissionTime=
</varname></term>
3410 <para>Takes a boolean. When true, the retransmission time received in the Router Advertisement will be set
3411 on the interface receiving the advertisement. It is used as the time between retransmissions of Neighbor
3412 Solicitation messages to a neighbor when resolving the address or when probing the reachability of a neighbor.
3413 Defaults to true.
</para>
3415 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
3420 <term><varname>UseGateway=
</varname></term>
3422 <para>When true (the default), the router address will be configured as the default gateway.
3425 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
3430 <term><varname>UseRoutePrefix=
</varname></term>
3432 <para>When true (the default), the routes corresponding to the route prefixes received in
3433 the Router Advertisement will be configured.
</para>
3435 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
3440 <term><varname>UseCaptivePortal=
</varname></term>
3442 <para>When true (the default), the captive portal received in the Router Advertisement will be recorded
3443 and made available to client programs and displayed in the
3444 <citerefentry><refentrytitle>networkctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
3445 status output per-link.
</para>
3447 <xi:include href=
"version-info.xml" xpointer=
"v254"/>
3452 <term><varname>UsePREF64=
</varname></term>
3454 <para>When true, the IPv6 PREF64 (or NAT64) prefixes received in the Router Advertisement will be
3455 recorded and made available to client programs and displayed in the
3456 <citerefentry><refentrytitle>networkctl
</refentrytitle><manvolnum>1</manvolnum></citerefentry>
3457 status output per-link. See
<ulink url=
"https://tools.ietf.org/html/rfc8781">RFC
8781</ulink>.
3458 Defaults to false.
</para>
3460 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
3465 <term><varname>UseAutonomousPrefix=
</varname></term>
3467 <para>When true (the default), the autonomous prefix received in the Router Advertisement will be used and take
3468 precedence over any statically configured ones.
</para>
3470 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
3475 <term><varname>UseOnLinkPrefix=
</varname></term>
3477 <para>When true (the default), the onlink prefix received in the Router Advertisement will be
3478 used and takes precedence over any statically configured ones.
</para>
3480 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
3485 <term><varname>RouterDenyList=
</varname></term>
3487 <para>A whitespace-separated list of IPv6 router addresses. Each address can optionally
3488 take a prefix length after
<literal>/
</literal>. Any information advertised by the listed
3489 router is ignored.
</para>
3491 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
3496 <term><varname>RouterAllowList=
</varname></term>
3498 <para>A whitespace-separated list of IPv6 router addresses. Each address can optionally
3499 take a prefix length after
<literal>/
</literal>. Only information advertised by the listed
3500 router is accepted. Note that if
<varname>RouterAllowList=
</varname> is configured then
3501 <varname>RouterDenyList=
</varname> is ignored.
</para>
3503 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
3508 <term><varname>PrefixDenyList=
</varname></term>
3510 <para>A whitespace-separated list of IPv6 prefixes. Each prefix can optionally take its
3511 prefix length after
<literal>/
</literal>. IPv6 prefixes supplied via router advertisements
3512 in the list are ignored.
</para>
3514 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
3519 <term><varname>PrefixAllowList=
</varname></term>
3521 <para>A whitespace-separated list of IPv6 prefixes. Each prefix can optionally take its
3522 prefix length after
<literal>/
</literal>. IPv6 prefixes supplied via router advertisements
3523 in the list are allowed. Note that if
<varname>PrefixAllowList=
</varname> is configured
3524 then
<varname>PrefixDenyList=
</varname> is ignored.
</para>
3526 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
3531 <term><varname>RouteDenyList=
</varname></term>
3533 <para>A whitespace-separated list of IPv6 route prefixes. Each prefix can optionally take
3534 its prefix length after
<literal>/
</literal>. IPv6 route prefixes supplied via router
3535 advertisements in the list are ignored.
</para>
3537 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
3542 <term><varname>RouteAllowList=
</varname></term>
3544 <para>A whitespace-separated list of IPv6 route prefixes. Each prefix can optionally take
3545 its prefix length after
<literal>/
</literal>. IPv6 route prefixes supplied via router
3546 advertisements in the list are allowed. Note that if
<varname>RouteAllowList=
</varname> is
3547 configured then
<varname>RouteDenyList=
</varname> is ignored.
</para>
3549 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
3554 <term><varname>DHCPv6Client=
</varname></term>
3556 <para>Takes a boolean, or the special value
<literal>always
</literal>. When true, the
3557 DHCPv6 client will be started in
<literal>solicit
</literal> mode if the RA has the
3558 <literal>managed
</literal> flag or
<literal>information-request
</literal> mode if the RA
3559 lacks the
<literal>managed
</literal> flag but has the
3560 <literal>other configuration
</literal> flag. If set to
<literal>always
</literal>, the
3561 DHCPv6 client will be started in
<literal>solicit
</literal> mode when an RA is received,
3562 even if neither the
<literal>managed
</literal> nor the
3563 <literal>other configuration
</literal> flag is set in the RA. This will be ignored when
3564 <varname>WithoutRA=
</varname> in the [DHCPv6] section is enabled, or
3565 <varname>UplinkInterface=:self
</varname> in the [DHCPPrefixDelegation] section is
3566 specified. Defaults to true.
</para>
3568 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
3573 <term><varname>NetLabel=
</varname></term>
3575 <para>This applies the NetLabel for the addresses received with RA, like
3576 <varname>NetLabel=
</varname> in [Address] section applies it to statically configured
3577 addresses. See
<varname>NetLabel=
</varname> in [Address] section for more details.
</para>
3579 <xi:include href=
"version-info.xml" xpointer=
"v252"/>
3584 <term><varname>NFTSet=
</varname></term>
3586 <para>This applies the NFT set for the network configuration received with RA, like
3587 <varname>NFTSet=
</varname> in [Address] section applies it to static configuration. See
3588 <varname>NFTSet=
</varname> in [Address] section for more details. For
<literal>address
</literal> or
3589 <literal>prefix
</literal> source types, the type of the element used in the NFT filter must be
3590 <literal>ipv6_addr
</literal>.
</para>
3592 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
3599 <title>[DHCPServer] Section Options
</title>
3600 <para>The [DHCPServer] section contains settings for the DHCP server, if enabled via the
3601 <varname>DHCPServer=
</varname> option described above:
</para>
3603 <variablelist class='network-directives'
>
3606 <term><varname>ServerAddress=
</varname></term>
3608 <para>Specifies the server address for the DHCP server. Takes an IPv4 address with prefix length
3609 separated with a slash, e.g.
<literal>192.168.0.1/
24</literal>. Defaults to unset, and one of
3610 static IPv4 addresses configured in [Network] or [Address] section will be automatically selected.
3611 This setting may be useful when the interface on which the DHCP server is running has multiple
3612 static IPv4 addresses.
</para>
3613 <para>This implies
<varname>Address=
</varname> in [Network] or [Address] section with the same
3614 address and prefix length. That is,
3615 <programlisting>[Network]
3617 Address=
192.168.0.1/
24
3618 Address=
192.168.0.2/
24
3620 ServerAddress=
192.168.0.1/
24</programlisting>
3622 <programlisting>[Network]
3625 Address=
192.168.0.1/
24
3627 Address=
192.168.0.2/
24
3629 ServerAddress=
192.168.0.1/
24</programlisting>
3630 are equivalent to the following:
3631 <programlisting>[Network]
3633 Address=
192.168.0.2/
24
3635 ServerAddress=
192.168.0.1/
24</programlisting>
3637 <para>Since version
255, like the
<varname>Address=
</varname> setting in [Network] or [Address]
3638 section, this also supports a null address, e.g.
<literal>0.0.0.0/
24</literal>, and an unused
3639 address will be automatically selected. For more details about the automatic address selection,
3640 see
<varname>Address=
</varname> setting in [Network] section in the above.
</para>
3642 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
3647 <term><varname>PoolOffset=
</varname></term>
3648 <term><varname>PoolSize=
</varname></term>
3650 <listitem><para>Configures the pool of addresses to hand out. The pool
3651 is a contiguous sequence of IP addresses in the subnet configured for
3652 the server address, which does not include the subnet nor the broadcast
3653 address.
<varname>PoolOffset=
</varname> takes the offset of the pool
3654 from the start of subnet, or zero to use the default value.
3655 <varname>PoolSize=
</varname> takes the number of IP addresses in the
3656 pool or zero to use the default value. By default, the pool starts at
3657 the first address after the subnet address and takes up the rest of
3658 the subnet, excluding the broadcast address. If the pool includes
3659 the server address (the default), this is reserved and not handed
3660 out to clients.
</para>
3662 <xi:include href=
"version-info.xml" xpointer=
"v226"/></listitem>
3666 <term><varname>DefaultLeaseTimeSec=
</varname></term>
3667 <term><varname>MaxLeaseTimeSec=
</varname></term>
3669 <listitem><para>Control the default and maximum DHCP lease
3670 time to pass to clients. These settings take time values in seconds or
3671 another common time unit, depending on the suffix. The default
3672 lease time is used for clients that did not ask for a specific
3673 lease time. If a client asks for a lease time longer than the
3674 maximum lease time, it is automatically shortened to the
3675 specified time. The default lease time defaults to
1h, the
3676 maximum lease time to
12h. Shorter lease times are beneficial
3677 if the configuration data in DHCP leases changes frequently
3678 and clients shall learn the new settings with shorter
3679 latencies. Longer lease times reduce the generated DHCP
3680 network traffic.
</para>
3682 <xi:include href=
"version-info.xml" xpointer=
"v226"/></listitem>
3686 <term><varname>UplinkInterface=
</varname></term>
3687 <listitem><para>Specifies the name or the index of the uplink interface, or one of the special
3688 values
<literal>:none
</literal> and
<literal>:auto
</literal>. When emitting DNS, NTP, or SIP
3689 servers is enabled but no servers are specified, the servers configured in the uplink interface
3690 will be emitted. When
<literal>:auto
</literal>, the link which has a default gateway with the
3691 highest priority will be automatically selected. When
<literal>:none
</literal>, no uplink
3692 interface will be selected. Defaults to
<literal>:auto
</literal>.
</para>
3694 <xi:include href=
"version-info.xml" xpointer=
"v249"/></listitem>
3698 <term><varname>EmitDNS=
</varname></term>
3699 <term><varname>DNS=
</varname></term>
3701 <listitem><para><varname>EmitDNS=
</varname> takes a boolean. Configures whether the DHCP leases
3702 handed out to clients shall contain DNS server information. Defaults to
<literal>yes
</literal>.
3703 The DNS servers to pass to clients may be configured with the
<varname>DNS=
</varname> option,
3704 which takes a list of IPv4 addresses, or special value
<literal>_server_address
</literal> which
3705 will be converted to the address used by the DHCP server.
</para>
3707 <para>If the
<varname>EmitDNS=
</varname> option is enabled but no servers configured, the
3708 servers are automatically propagated from an
"uplink" interface that has appropriate servers
3709 set. The
"uplink" interface is determined by the default route of the system with the highest
3710 priority. Note that this information is acquired at the time the lease is handed out, and does
3711 not take uplink interfaces into account that acquire DNS server information at a later point.
3712 If no suitable uplink interface is found the DNS server data from
3713 <filename>/etc/resolv.conf
</filename> is used. Also, note that the leases are not refreshed if
3714 the uplink network configuration changes. To ensure clients regularly acquire the most current
3715 uplink DNS server information, it is thus advisable to shorten the DHCP lease time via
3716 <varname>MaxLeaseTimeSec=
</varname> described above.
</para>
3718 <para>This setting can be specified multiple times. If an empty string is specified, then all
3719 DNS servers specified earlier are cleared.
</para>
3721 <xi:include href=
"version-info.xml" xpointer=
"v226"/></listitem>
3725 <term><varname>EmitNTP=
</varname></term>
3726 <term><varname>NTP=
</varname></term>
3727 <term><varname>EmitSIP=
</varname></term>
3728 <term><varname>SIP=
</varname></term>
3729 <term><varname>EmitPOP3=
</varname></term>
3730 <term><varname>POP3=
</varname></term>
3731 <term><varname>EmitSMTP=
</varname></term>
3732 <term><varname>SMTP=
</varname></term>
3733 <term><varname>EmitLPR=
</varname></term>
3734 <term><varname>LPR=
</varname></term>
3736 <listitem><para>Similar to the
<varname>EmitDNS=
</varname> and
<varname>DNS=
</varname> settings
3737 described above, these settings configure whether and what server information for the indicate
3738 protocol shall be emitted as part of the DHCP lease. The same syntax, propagation semantics and
3739 defaults apply as for
<varname>EmitDNS=
</varname> and
<varname>DNS=
</varname>.
</para>
3741 <xi:include href=
"version-info.xml" xpointer=
"v226"/></listitem>
3745 <term><varname>EmitRouter=
</varname></term>
3746 <term><varname>Router=
</varname></term>
3748 <listitem><para>The
<varname>EmitRouter=
</varname> setting takes a boolean value, and configures
3749 whether the DHCP lease should contain the router option. The
<varname>Router=
</varname> setting
3750 takes an IPv4 address, and configures the router address to be emitted. When the
3751 <varname>Router=
</varname> setting is not specified, then the server address will be used for
3752 the router option. When the
<varname>EmitRouter=
</varname> setting is disabled, the
3753 <varname>Router=
</varname> setting will be ignored. The
<varname>EmitRouter=
</varname> setting
3754 defaults to true, and the
<varname>Router=
</varname> setting defaults to unset.
3757 <xi:include href=
"version-info.xml" xpointer=
"v230"/></listitem>
3761 <term><varname>EmitTimezone=
</varname></term>
3762 <term><varname>Timezone=
</varname></term>
3764 <listitem><para>Takes a boolean. Configures whether the DHCP leases handed out
3765 to clients shall contain timezone information. Defaults to
<literal>yes
</literal>. The
3766 <varname>Timezone=
</varname> setting takes a timezone string
3767 (such as
<literal>Europe/Berlin
</literal> or
3768 <literal>UTC
</literal>) to pass to clients. If no explicit
3769 timezone is set, the system timezone of the local host is
3770 propagated, as determined by the
3771 <filename>/etc/localtime
</filename> symlink.
</para>
3773 <xi:include href=
"version-info.xml" xpointer=
"v226"/></listitem>
3777 <term><varname>BootServerAddress=
</varname></term>
3780 <para>Takes an IPv4 address of the boot server used by e.g. PXE boot systems. When specified, this
3781 address is sent in the
<option>siaddr
</option> field of the DHCP message header. See
<ulink
3782 url=
"https://www.rfc-editor.org/rfc/rfc2131.html">RFC
2131</ulink> for more details. Defaults to
3785 <xi:include href=
"version-info.xml" xpointer=
"v251"/>
3790 <term><varname>BootServerName=
</varname></term>
3793 <para>Takes a name of the boot server used by e.g. PXE boot systems. When specified, this name is
3794 sent in the DHCP option
66 (
"TFTP server name"). See
<ulink
3795 url=
"https://www.rfc-editor.org/rfc/rfc2132.html">RFC
2132</ulink> for more details. Defaults to
3798 <para>Note that typically setting one of
<varname>BootServerName=
</varname> or
3799 <varname>BootServerAddress=
</varname> is sufficient, but both can be set too, if desired.
</para>
3801 <xi:include href=
"version-info.xml" xpointer=
"v251"/>
3806 <term><varname>BootFilename=
</varname></term>
3809 <para>Takes a path or URL to a file loaded by e.g. a PXE boot loader. When specified, this path is
3810 sent in the DHCP option
67 (
"Bootfile name"). See
<ulink
3811 url=
"https://www.rfc-editor.org/rfc/rfc2132.html">RFC
2132</ulink> for more details. Defaults to
3814 <xi:include href=
"version-info.xml" xpointer=
"v251"/>
3819 <term><varname>IPv6OnlyPreferredSec=
</varname></term>
3822 <para>Takes a timespan. Controls the
3823 <ulink url=
"https://tools.ietf.org/html/rfc8925">RFC
8925</ulink> IPv6-Only Preferred option.
3824 Specifies the DHCPv4 option to indicate that a host supports an IPv6-only mode and is willing to
3825 forgo obtaining an IPv4 address if the network provides IPv6 connectivity. Defaults to unset, and
3826 not send the option. The minimum allowed value is
300 seconds.
</para>
3828 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
3833 <term><varname>SendOption=
</varname></term>
3835 <para>Send a raw option with value via DHCPv4 server. Takes a DHCP option number, data type
3836 and data (
<literal><replaceable>option
</replaceable>:
<replaceable>type
</replaceable>:
<replaceable>value
</replaceable></literal>).
3837 The option number is an integer in the range
1…
254. The type takes one of
<literal>uint8
</literal>,
3838 <literal>uint16
</literal>,
<literal>uint32
</literal>,
<literal>ipv4address
</literal>,
<literal>ipv6address
</literal>, or
3839 <literal>string
</literal>. Special characters in the data string may be escaped using
3840 <ulink url=
"https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
3841 escapes
</ulink>. This setting can be specified multiple times. If an empty string is specified,
3842 then all options specified earlier are cleared. Defaults to unset.
</para>
3844 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
3849 <term><varname>SendVendorOption=
</varname></term>
3851 <para>Send a vendor option with value via DHCPv4 server. Takes a DHCP option number, data type
3852 and data (
<literal><replaceable>option
</replaceable>:
<replaceable>type
</replaceable>:
<replaceable>value
</replaceable></literal>).
3853 The option number is an integer in the range
1…
254. The type takes one of
<literal>uint8
</literal>,
3854 <literal>uint16
</literal>,
<literal>uint32
</literal>,
<literal>ipv4address
</literal>, or
3855 <literal>string
</literal>. Special characters in the data string may be escaped using
3856 <ulink url=
"https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
3857 escapes
</ulink>. This setting can be specified multiple times. If an empty string is specified,
3858 then all options specified earlier are cleared. Defaults to unset.
</para>
3860 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
3864 <term><varname>BindToInterface=
</varname></term>
3866 <para>Takes a boolean value. When
<literal>yes
</literal>, DHCP server socket will be bound
3867 to its network interface and all socket communication will be restricted to this interface.
3868 Defaults to
<literal>yes
</literal>, except if
<varname>RelayTarget=
</varname> is used (see below),
3869 in which case it defaults to
<literal>no
</literal>.
</para>
3871 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
3875 <term><varname>RelayTarget=
</varname></term>
3877 <para>Takes an IPv4 address, which must be in the format described in
3878 <citerefentry project='man-pages'
><refentrytitle>inet_pton
</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
3879 Turns this DHCP server into a DHCP relay agent. See
<ulink url=
"https://tools.ietf.org/html/rfc1542">RFC
1542</ulink>.
3880 The address is the address of DHCP server or another relay agent to forward DHCP messages to and from.
</para>
3882 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
3886 <term><varname>RelayAgentCircuitId=
</varname></term>
3888 <para>Specifies value for Agent Circuit ID suboption of Relay Agent Information option.
3889 Takes a string, which must be in the format
<literal>string:
<replaceable>value
</replaceable></literal>,
3890 where
<literal><replaceable>value
</replaceable></literal> should be replaced with the value of the suboption.
3891 Defaults to unset (means no Agent Circuit ID suboption is generated).
3892 Ignored if
<varname>RelayTarget=
</varname> is not specified.
</para>
3894 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
3898 <term><varname>RelayAgentRemoteId=
</varname></term>
3900 <para>Specifies value for Agent Remote ID suboption of Relay Agent Information option.
3901 Takes a string, which must be in the format
<literal>string:
<replaceable>value
</replaceable></literal>,
3902 where
<literal><replaceable>value
</replaceable></literal> should be replaced with the value of the suboption.
3903 Defaults to unset (means no Agent Remote ID suboption is generated).
3904 Ignored if
<varname>RelayTarget=
</varname> is not specified.
</para>
3906 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
3911 <term><varname>RapidCommit=
</varname></term>
3913 <para>Takes a boolean. When true, the server supports
3914 <ulink url=
"https://datatracker.ietf.org/doc/html/rfc4039">RFC
4039</ulink>. When a client sends
3915 a DHCPDISCOVER message with the Rapid Commit option to the server, then the server will reply with
3916 a DHCPACK message to the client, instead of DHCPOFFER. Defaults to true.
</para>
3918 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
3923 <term><varname>PersistLeases=
</varname></term>
3925 <para>Takes a boolean. When true, the DHCP server will load and save leases in the persistent
3926 storage. When false, the DHCP server will neither load nor save leases in the persistent storage.
3927 Hence, bound leases will be lost when the interface is reconfigured e.g. by
3928 <command>networkctl reconfigure
</command>, or
<filename>systemd-networkd.service
</filename>
3929 is restarted. That may cause address conflict on the network. So, please take an extra care when
3930 disable this setting. When unspecified, the value specified in the same setting in
3931 <citerefentry><refentrytitle>networkd.conf
</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
3932 which defaults to
<literal>yes
</literal>, will be used.
</para>
3934 <xi:include href=
"version-info.xml" xpointer=
"v256"/>
3942 <title>[DHCPServerStaticLease] Section Options
</title>
3943 <para>The
<literal>[DHCPServerStaticLease]
</literal> section configures a static DHCP lease to assign a
3944 fixed IPv4 address to a specific device based on its MAC address. This section can be specified multiple
3947 <variablelist class='network-directives'
>
3949 <term><varname>MACAddress=
</varname></term>
3951 <listitem><para>The hardware address of a device to match. This key is mandatory.
</para>
3953 <xi:include href=
"version-info.xml" xpointer=
"v249"/></listitem>
3957 <term><varname>Address=
</varname></term>
3959 <listitem><para>The IPv4 address that should be assigned to the device that was matched with
3960 <varname>MACAddress=
</varname>. This key is mandatory.
</para>
3962 <xi:include href=
"version-info.xml" xpointer=
"v249"/></listitem>
3968 <title>[IPv6SendRA] Section Options
</title>
3969 <para>The [IPv6SendRA] section contains settings for sending IPv6 Router Advertisements and whether
3970 to act as a router, if enabled via the
<varname>IPv6SendRA=
</varname> option described above. IPv6
3971 network prefixes or routes are defined with one or more [IPv6Prefix] or [IPv6RoutePrefix] sections.
3974 <variablelist class='network-directives'
>
3977 <term><varname>Managed=
</varname></term>
3978 <term><varname>OtherInformation=
</varname></term>
3980 <listitem><para>Takes a boolean. Controls whether a DHCPv6 server is used to acquire IPv6
3981 addresses on the network link when
<varname>Managed=
</varname>
3982 is set to
<literal>true
</literal> or if only additional network
3983 information can be obtained via DHCPv6 for the network link when
3984 <varname>OtherInformation=
</varname> is set to
3985 <literal>true
</literal>. Both settings default to
3986 <literal>false
</literal>, which means that a DHCPv6 server is not being
3989 <xi:include href=
"version-info.xml" xpointer=
"v235"/></listitem>
3993 <term><varname>RouterLifetimeSec=
</varname></term>
3995 <listitem><para>Takes a timespan. Configures the IPv6 router lifetime in seconds. The value must be
0
3996 seconds, or between
4 seconds and
9000 seconds. When set to
0, the host is not acting as a router.
3997 Defaults to
1800 seconds (
30 minutes).
</para>
3999 <xi:include href=
"version-info.xml" xpointer=
"v235"/>
4004 <term><varname>RetransmitSec=
</varname></term>
4006 <listitem><para>Takes a timespan. Configures the retransmit time, used by clients to retransmit Neighbor
4007 Solicitation messages on address resolution and the Neighbor Unreachability Detection algorithm.
4008 An integer, the default unit is seconds, in the range
0…
4294967295 msec. Defaults to
0.
</para>
4010 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
4015 <term><varname>RouterPreference=
</varname></term>
4017 <listitem><para>Configures IPv6 router preference if
4018 <varname>RouterLifetimeSec=
</varname> is non-zero. Valid values are
4019 <literal>high
</literal>,
<literal>medium
</literal> and
4020 <literal>low
</literal>, with
<literal>normal
</literal> and
4021 <literal>default
</literal> added as synonyms for
4022 <literal>medium
</literal> just to make configuration easier. See
4023 <ulink url=
"https://tools.ietf.org/html/rfc4191">RFC
4191</ulink>
4024 for details. Defaults to
<literal>medium
</literal>.
</para>
4026 <xi:include href=
"version-info.xml" xpointer=
"v235"/></listitem>
4030 <term><varname>HopLimit=
</varname></term>
4032 <para>Configures hop limit. Takes an integer in the range
0…
255. See also
4033 <varname>IPv6HopLimit=
</varname>.
</para>
4035 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
4040 <term><varname>UplinkInterface=
</varname></term>
4041 <listitem><para>Specifies the name or the index of the uplink interface, or one of the special
4042 values
<literal>:none
</literal> and
<literal>:auto
</literal>. When emitting DNS servers or
4043 search domains is enabled but no servers are specified, the servers configured in the uplink
4044 interface will be emitted. When
<literal>:auto
</literal>, the value specified to the same
4045 setting in the [DHCPPrefixDelegation] section will be used if
4046 <varname>DHCPPrefixDelegation=
</varname> is enabled, otherwise the link which has a default
4047 gateway with the highest priority will be automatically selected. When
<literal>:none
</literal>,
4048 no uplink interface will be selected. Defaults to
<literal>:auto
</literal>.
</para>
4050 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
4054 <term><varname>EmitDNS=
</varname></term>
4055 <term><varname>DNS=
</varname></term>
4057 <listitem><para><varname>DNS=
</varname> specifies a list of recursive DNS server IPv6 addresses
4058 that are distributed via Router Advertisement messages when
<varname>EmitDNS=
</varname> is true.
4059 <varname>DNS=
</varname> also takes special value
<literal>_link_local
</literal>; in that case
4060 the IPv6 link-local address is distributed. If
<varname>DNS=
</varname> is empty, DNS servers are
4061 read from the [Network] section. If the [Network] section does not contain any DNS servers
4062 either, DNS servers from the uplink interface specified in
<varname>UplinkInterface=
</varname>
4063 will be used. When
<varname>EmitDNS=
</varname> is false, no DNS server information is sent in
4064 Router Advertisement messages.
<varname>EmitDNS=
</varname> defaults to true.
</para>
4066 <xi:include href=
"version-info.xml" xpointer=
"v235"/></listitem>
4070 <term><varname>EmitDomains=
</varname></term>
4071 <term><varname>Domains=
</varname></term>
4073 <listitem><para>A list of DNS search domains distributed via Router Advertisement messages when
4074 <varname>EmitDomains=
</varname> is true. If
<varname>Domains=
</varname> is empty, DNS search
4075 domains are read from the [Network] section. If the [Network] section does not contain any DNS
4076 search domains either, DNS search domains from the uplink interface specified in
4077 <varname>UplinkInterface=
</varname> will be used. When
<varname>EmitDomains=
</varname> is false,
4078 no DNS search domain information is sent in Router Advertisement messages.
4079 <varname>EmitDomains=
</varname> defaults to true.
</para>
4081 <xi:include href=
"version-info.xml" xpointer=
"v235"/></listitem>
4085 <term><varname>DNSLifetimeSec=
</varname></term>
4087 <listitem><para>Lifetime in seconds for the DNS server addresses listed in
4088 <varname>DNS=
</varname> and search domains listed in
<varname>Domains=
</varname>. Defaults to
4089 3600 seconds (one hour).
</para>
4091 <xi:include href=
"version-info.xml" xpointer=
"v235"/></listitem>
4095 <term><varname>HomeAgent=
</varname></term>
4097 <listitem><para>Takes a boolean. Specifies that IPv6 router advertisements which indicate to hosts that
4098 the router acts as a Home Agent and includes a Home Agent option. Defaults to false. See
4099 <ulink url=
"https://tools.ietf.org/html/rfc6275">RFC
6275</ulink> for further details.
</para>
4101 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
4106 <term><varname>HomeAgentLifetimeSec=
</varname></term>
4108 <listitem><para>Takes a timespan. Specifies the lifetime of the Home Agent. An integer, the default unit is seconds,
4109 in the range
1…
65535. Defaults to the value set to
<varname>RouterLifetimeSec=
</varname>.
</para>
4111 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
4116 <term><varname>HomeAgentPreference=
</varname></term>
4118 <listitem><para>Configures IPv6 Home Agent preference. Takes an integer in the range
0…
65535.
4119 Defaults to
0.
</para>
4121 <xi:include href=
"version-info.xml" xpointer=
"v255"/>
4129 <title>[IPv6Prefix] Section Options
</title>
4130 <para>One or more [IPv6Prefix] sections contain the IPv6 prefixes that are announced via Router
4131 Advertisements. See
<ulink url=
"https://tools.ietf.org/html/rfc4861">RFC
4861</ulink> for further
4134 <variablelist class='network-directives'
>
4137 <term><varname>AddressAutoconfiguration=
</varname></term>
4138 <term><varname>OnLink=
</varname></term>
4140 <listitem><para>Takes a boolean to specify whether IPv6 addresses can be
4141 autoconfigured with this prefix and whether the prefix can be used for
4142 onlink determination. Both settings default to
<literal>true
</literal>
4143 in order to ease configuration.
4146 <xi:include href=
"version-info.xml" xpointer=
"v235"/></listitem>
4150 <term><varname>Prefix=
</varname></term>
4152 <listitem><para>The IPv6 prefix that is to be distributed to hosts. Similarly to configuring static
4153 IPv6 addresses, the setting is configured as an IPv6 prefix and its prefix length, separated by a
4154 <literal>/
</literal> character. Use multiple [IPv6Prefix] sections to configure multiple IPv6
4155 prefixes since prefix lifetimes, address autoconfiguration and onlink status may differ from one
4156 prefix to another.
</para>
4158 <xi:include href=
"version-info.xml" xpointer=
"v235"/></listitem>
4162 <term><varname>PreferredLifetimeSec=
</varname></term>
4163 <term><varname>ValidLifetimeSec=
</varname></term>
4165 <listitem><para>Preferred and valid lifetimes for the prefix measured in seconds.
4166 <varname>PreferredLifetimeSec=
</varname> defaults to
1800 seconds (
30 minutes) and
4167 <varname>ValidLifetimeSec=
</varname> defaults to
3600 seconds (one hour).
</para>
4169 <xi:include href=
"version-info.xml" xpointer=
"v235"/></listitem>
4173 <term><varname>Assign=
</varname></term>
4174 <listitem><para>Takes a boolean. When true, adds an address from the prefix. Default to false.
4177 <xi:include href=
"version-info.xml" xpointer=
"v246"/></listitem>
4181 <term><varname>Token=
</varname></term>
4183 <para>Specifies an optional address generation mode for assigning an address in each
4184 prefix. This accepts the same syntax as
<varname>Token=
</varname> in the [IPv6AcceptRA]
4185 section. If
<varname>Assign=
</varname> is set to false, then this setting will be ignored.
4186 Defaults to unset, which means the EUI-
64 algorithm will be used.
</para>
4188 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
4193 <term><varname>RouteMetric=
</varname></term>
4195 <para>The metric of the prefix route. Takes an unsigned integer in the range
0…
4294967295.
4196 When unset or set to
0, the kernel's default value is used. This setting is ignored when
4197 <varname>Assign=
</varname> is false.
</para>
4199 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
4206 <title>[IPv6RoutePrefix] Section Options
</title>
4207 <para>One or more [IPv6RoutePrefix] sections contain the IPv6
4208 prefix routes that are announced via Router Advertisements. See
4209 <ulink url=
"https://tools.ietf.org/html/rfc4191">RFC
4191</ulink>
4210 for further details.
</para>
4212 <variablelist class='network-directives'
>
4215 <term><varname>Route=
</varname></term>
4217 <listitem><para>The IPv6 route that is to be distributed to hosts. Similarly to configuring static
4218 IPv6 routes, the setting is configured as an IPv6 prefix routes and its prefix route length,
4219 separated by a
<literal>/
</literal> character. Use multiple [IPv6RoutePrefix] sections to configure
4220 multiple IPv6 prefix routes.
</para>
4222 <xi:include href=
"version-info.xml" xpointer=
"v244"/></listitem>
4226 <term><varname>LifetimeSec=
</varname></term>
4228 <listitem><para>Lifetime for the route prefix measured in seconds.
4229 <varname>LifetimeSec=
</varname> defaults to
3600 seconds (one hour).
</para>
4231 <xi:include href=
"version-info.xml" xpointer=
"v244"/></listitem>
4238 <title>[IPv6PREF64Prefix] Section Options
</title>
4239 <para>One or more [IPv6PREF64Prefix] sections contain the IPv6 PREF64 (or NAT64) prefixes that are announced via Router
4240 Advertisements. See
<ulink url=
"https://tools.ietf.org/html/rfc8781">RFC
8781</ulink> for further
4243 <variablelist class='network-directives'
>
4246 <term><varname>Prefix=
</varname></term>
4248 <listitem><para>The IPv6 PREF64 (or NAT64) prefix that is to be distributed to hosts. The setting holds
4249 an IPv6 prefix that should be set up for NAT64 translation (PLAT) to allow
464XLAT on the network segment.
4250 Use multiple [IPv6PREF64Prefix] sections to configure multiple IPv6 prefixes since prefix lifetime may differ
4251 from one prefix to another. The prefix is an address with a prefix length, separated by a slash
4252 <literal>/
</literal> character. Valid NAT64 prefix length are
96,
64,
56,
48,
40, and
32 bits.
</para>
4254 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem></varlistentry>
4257 <term><varname>LifetimeSec=
</varname></term>
4258 <listitem><para>Lifetime for the prefix measured in seconds. Should be greater than or equal to
<varname>RouterLifetimeSec=
</varname>.
4259 <varname>LifetimeSec=
</varname> defaults to
1800 seconds.
</para>
4261 <xi:include href=
"version-info.xml" xpointer=
"v255"/></listitem>
4267 <title>[Bridge] Section Options
</title>
4268 <para>The [Bridge] section accepts the following keys:
</para>
4270 <variablelist class='network-directives'
>
4272 <term><varname>UnicastFlood=
</varname></term>
4274 <para>Takes a boolean. Controls whether the bridge should flood
4275 traffic for which an FDB entry is missing and the destination
4276 is unknown through this port. When unset, the kernel's default will be used.
4279 <xi:include href=
"version-info.xml" xpointer=
"v223"/>
4283 <term><varname>MulticastFlood=
</varname></term>
4285 <para>Takes a boolean. Controls whether the bridge should flood
4286 traffic for which an MDB entry is missing and the destination
4287 is unknown through this port. When unset, the kernel's default will be used.
4290 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
4294 <term><varname>MulticastToUnicast=
</varname></term>
4296 <para>Takes a boolean. Multicast to unicast works on top of the multicast snooping feature of
4297 the bridge. Which means unicast copies are only delivered to hosts which are interested in it.
4298 When unset, the kernel's default will be used.
4301 <xi:include href=
"version-info.xml" xpointer=
"v240"/>
4305 <term><varname>NeighborSuppression=
</varname></term>
4307 <para>Takes a boolean. Configures whether ARP and ND neighbor suppression is enabled for
4308 this port. When unset, the kernel's default will be used.
4311 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
4315 <term><varname>Learning=
</varname></term>
4317 <para>Takes a boolean. Configures whether MAC address learning is enabled for
4318 this port. When unset, the kernel's default will be used.
4321 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
4325 <term><varname>HairPin=
</varname></term>
4327 <para>Takes a boolean. Configures whether traffic may be sent back out of the port on which it
4328 was received. When this flag is false, then the bridge will not forward traffic back out of the
4329 receiving port. When unset, the kernel's default will be used.
</para>
4331 <xi:include href=
"version-info.xml" xpointer=
"v223"/>
4335 <term><varname>Isolated=
</varname></term>
4337 <para>Takes a boolean. Configures whether this port is isolated or not. Within a bridge,
4338 isolated ports can only communicate with non-isolated ports. When set to true, this port can only
4339 communicate with other ports whose Isolated setting is false. When set to false, this port
4340 can communicate with any other ports. When unset, the kernel's default will be used.
</para>
4342 <xi:include href=
"version-info.xml" xpointer=
"v251"/>
4346 <term><varname>UseBPDU=
</varname></term>
4348 <para>Takes a boolean. Configures whether STP Bridge Protocol Data Units will be
4349 processed by the bridge port. When unset, the kernel's default will be used.
</para>
4351 <xi:include href=
"version-info.xml" xpointer=
"v223"/>
4355 <term><varname>FastLeave=
</varname></term>
4357 <para>Takes a boolean. This flag allows the bridge to immediately stop multicast
4358 traffic on a port that receives an IGMP Leave message. It is only used with
4359 IGMP snooping if enabled on the bridge. When unset, the kernel's default will be used.
</para>
4361 <xi:include href=
"version-info.xml" xpointer=
"v223"/>
4365 <term><varname>AllowPortToBeRoot=
</varname></term>
4367 <para>Takes a boolean. Configures whether a given port is allowed to
4368 become a root port. Only used when STP is enabled on the bridge.
4369 When unset, the kernel's default will be used.
</para>
4371 <xi:include href=
"version-info.xml" xpointer=
"v223"/>
4375 <term><varname>ProxyARP=
</varname></term>
4377 <para>Takes a boolean. Configures whether proxy ARP to be enabled on this port.
4378 When unset, the kernel's default will be used.
</para>
4380 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
4384 <term><varname>ProxyARPWiFi=
</varname></term>
4386 <para>Takes a boolean. Configures whether proxy ARP to be enabled on this port
4387 which meets extended requirements by IEEE
802.11 and Hotspot
2.0 specifications.
4388 When unset, the kernel's default will be used.
</para>
4390 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
4394 <term><varname>MulticastRouter=
</varname></term>
4396 <para>Configures this port for having multicast routers attached. A port with a multicast
4397 router will receive all multicast traffic. Takes one of
<literal>no
</literal>
4398 to disable multicast routers on this port,
<literal>query
</literal> to let the system detect
4399 the presence of routers,
<literal>permanent
</literal> to permanently enable multicast traffic
4400 forwarding on this port, or
<literal>temporary
</literal> to enable multicast routers temporarily
4401 on this port, not depending on incoming queries. When unset, the kernel's default will be used.
</para>
4403 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
4407 <term><varname>Cost=
</varname></term>
4409 <para>Sets the
"cost" of sending packets of this interface.
4410 Each port in a bridge may have a different speed and the cost
4411 is used to decide which link to use. Faster interfaces
4412 should have lower costs. It is an integer value between
1 and
4415 <xi:include href=
"version-info.xml" xpointer=
"v218"/>
4419 <term><varname>Priority=
</varname></term>
4421 <para>Sets the
"priority" of sending packets on this interface.
4422 Each port in a bridge may have a different priority which is used
4423 to decide which link to use. Lower value means higher priority.
4424 It is an integer value between
0 to
63. Networkd does not set any
4425 default, meaning the kernel default value of
32 is used.
</para>
4427 <xi:include href=
"version-info.xml" xpointer=
"v234"/>
4434 <title>[BridgeFDB] Section Options
</title>
4436 <para>The [BridgeFDB] section manages the forwarding database table of a port and accepts the following
4437 keys. Specify several [BridgeFDB] sections to configure several static MAC table entries.
</para>
4439 <variablelist class='network-directives'
>
4441 <term><varname>MACAddress=
</varname></term>
4443 <para>As in the [Network] section. This key is mandatory.
</para>
4445 <xi:include href=
"version-info.xml" xpointer=
"v219"/>
4449 <term><varname>Destination=
</varname></term>
4451 <para>Takes an IP address of the destination VXLAN tunnel endpoint.
</para>
4453 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
4457 <term><varname>VLANId=
</varname></term>
4459 <para>The VLAN ID for the new static MAC table entry. If
4460 omitted, no VLAN ID information is appended to the new static MAC
4463 <xi:include href=
"version-info.xml" xpointer=
"v219"/>
4467 <term><varname>VNI=
</varname></term>
4469 <para>The VXLAN Network Identifier (or VXLAN Segment ID) to use to connect to
4470 the remote VXLAN tunnel endpoint. Takes a number in the range
1…
16777215.
4471 Defaults to unset.
</para>
4473 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
4477 <term><varname>AssociatedWith=
</varname></term>
4479 <para>Specifies where the address is associated with. Takes one of
<literal>use
</literal>,
4480 <literal>self
</literal>,
<literal>master
</literal> or
<literal>router
</literal>.
4481 <literal>use
</literal> means the address is in use. User space can use this option to
4482 indicate to the kernel that the fdb entry is in use.
<literal>self
</literal> means
4483 the address is associated with the port drivers fdb. Usually hardware.
<literal>master
</literal>
4484 means the address is associated with master devices fdb.
<literal>router
</literal> means
4485 the destination address is associated with a router. Note that it's valid if the referenced
4486 device is a VXLAN type device and has route shortcircuit enabled. Defaults to
<literal>self
</literal>.
</para>
4488 <xi:include href=
"version-info.xml" xpointer=
"v243"/>
4492 <term><varname>OutgoingInterface=
</varname></term>
4494 <para>Specifies the name or index of the outgoing interface for the VXLAN device driver to
4495 reach the remote VXLAN tunnel endpoint. Defaults to unset.
</para>
4497 <xi:include href=
"version-info.xml" xpointer=
"v249"/>
4504 <title>[BridgeMDB] Section Options
</title>
4505 <para>The [BridgeMDB] section manages the multicast membership entries forwarding database table of a port and accepts the following
4506 keys. Specify several [BridgeMDB] sections to configure several permanent multicast membership entries.
</para>
4508 <variablelist class='network-directives'
>
4510 <term><varname>MulticastGroupAddress=
</varname></term>
4512 <para>Specifies the IPv4 or IPv6 multicast group address to add. This setting is mandatory.
</para>
4514 <xi:include href=
"version-info.xml" xpointer=
"v247"/>
4518 <term><varname>VLANId=
</varname></term>
4520 <para>The VLAN ID for the new entry. Valid ranges are
0 (no VLAN) to
4094. Optional, defaults to
0.
</para>
4522 <xi:include href=
"version-info.xml" xpointer=
"v247"/>
4529 <title>[LLDP] Section Options
</title>
4530 <para>The [LLDP] section manages the Link Layer Discovery Protocol (LLDP) and accepts the following
4533 <variablelist class='network-directives'
>
4535 <term><varname>MUDURL=
</varname></term>
4537 <para>When configured, the specified Manufacturer Usage Descriptions (MUD) URL will be sent in
4538 LLDP packets. The syntax and semantics are the same as for
<varname>MUDURL=
</varname> in the
4539 [DHCPv4] section described above.
</para>
4541 <para>The MUD URLs received via LLDP packets are saved and can be read using the
4542 <function>sd_lldp_neighbor_get_mud_url()
</function> function.
</para>
4544 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4551 <title>[CAN] Section Options
</title>
4552 <para>The [CAN] section manages the Controller Area Network (CAN bus) and accepts the
4553 following keys:
</para>
4554 <variablelist class='network-directives'
>
4556 <term><varname>BitRate=
</varname></term>
4558 <para>The bitrate of CAN device in bits per second. The usual SI prefixes (K, M) with the base of
1000 can
4559 be used here. Takes a number in the range
1…
4294967295.
</para>
4561 <xi:include href=
"version-info.xml" xpointer=
"v239"/>
4565 <term><varname>SamplePoint=
</varname></term>
4567 <para>Optional sample point in percent with one decimal (e.g.
<literal>75%
</literal>,
4568 <literal>87.5%
</literal>) or permille (e.g.
<literal>875‰
</literal>). This will be ignored when
4569 <varname>BitRate=
</varname> is unspecified.
</para>
4571 <xi:include href=
"version-info.xml" xpointer=
"v239"/>
4575 <term><varname>TimeQuantaNSec=
</varname></term>
4576 <term><varname>PropagationSegment=
</varname></term>
4577 <term><varname>PhaseBufferSegment1=
</varname></term>
4578 <term><varname>PhaseBufferSegment2=
</varname></term>
4579 <term><varname>SyncJumpWidth=
</varname></term>
4581 <para>Specifies the time quanta, propagation segment, phase buffer segment
1 and
2, and the
4582 synchronization jump width, which allow one to define the CAN bit-timing in a hardware
4583 independent format as proposed by the Bosch CAN
2.0 Specification.
4584 <varname>TimeQuantaNSec=
</varname> takes a timespan in nanoseconds.
4585 <varname>PropagationSegment=
</varname>,
<varname>PhaseBufferSegment1=
</varname>,
4586 <varname>PhaseBufferSegment2=
</varname>, and
<varname>SyncJumpWidth=
</varname> take number
4587 of time quantum specified in
<varname>TimeQuantaNSec=
</varname> and must be an unsigned
4588 integer in the range
0…
4294967295. These settings except for
4589 <varname>SyncJumpWidth=
</varname> will be ignored when
<varname>BitRate=
</varname> is
4592 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
4596 <term><varname>DataBitRate=
</varname></term>
4597 <term><varname>DataSamplePoint=
</varname></term>
4599 <para>The bitrate and sample point for the data phase, if CAN-FD is used. These settings are
4600 analogous to the
<varname>BitRate=
</varname> and
<varname>SamplePoint=
</varname> keys.
</para>
4602 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4606 <term><varname>DataTimeQuantaNSec=
</varname></term>
4607 <term><varname>DataPropagationSegment=
</varname></term>
4608 <term><varname>DataPhaseBufferSegment1=
</varname></term>
4609 <term><varname>DataPhaseBufferSegment2=
</varname></term>
4610 <term><varname>DataSyncJumpWidth=
</varname></term>
4612 <para>Specifies the time quanta, propagation segment, phase buffer segment
1 and
2, and the
4613 synchronization jump width for the data phase, if CAN-FD is used. These settings are
4614 analogous to the
<varname>TimeQuantaNSec=
</varname> or related settings.
</para>
4616 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
4620 <term><varname>FDMode=
</varname></term>
4622 <para>Takes a boolean. When
<literal>yes
</literal>, CAN-FD mode is enabled for the interface.
4623 Note, that a bitrate and optional sample point should also be set for the CAN-FD data phase using
4624 the
<varname>DataBitRate=
</varname> and
<varname>DataSamplePoint=
</varname> keys, or
4625 <varname>DataTimeQuanta=
</varname> and related settings.
</para>
4627 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4631 <term><varname>FDNonISO=
</varname></term>
4633 <para>Takes a boolean. When
<literal>yes
</literal>, non-ISO CAN-FD mode is enabled for the
4634 interface. When unset, the kernel's default will be used.
</para>
4636 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4640 <term><varname>RestartSec=
</varname></term>
4642 <para>Automatic restart delay time. If set to a non-zero value, a restart of the CAN controller will be
4643 triggered automatically in case of a bus-off condition after the specified delay time. Subsecond delays can
4644 be specified using decimals (e.g.
<literal>0.1s
</literal>) or a
<literal>ms
</literal> or
4645 <literal>us
</literal> postfix. Using
<literal>infinity
</literal> or
<literal>0</literal> will turn the
4646 automatic restart off. By default automatic restart is disabled.
</para>
4648 <xi:include href=
"version-info.xml" xpointer=
"v239"/>
4652 <term><varname>Termination=
</varname></term>
4654 <para>Takes a boolean or a termination resistor value in ohm in the range
0…
65535. When
4655 <literal>yes
</literal>, the termination resistor is set to
120 ohm. When
4656 <literal>no
</literal> or
<literal>0</literal> is set, the termination resistor is disabled.
4657 When unset, the kernel's default will be used.
</para>
4659 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4663 <term><varname>TripleSampling=
</varname></term>
4665 <para>Takes a boolean. When
<literal>yes
</literal>, three samples (instead of one) are used to determine
4666 the value of a received bit by majority rule. When unset, the kernel's default will be used.
</para>
4668 <xi:include href=
"version-info.xml" xpointer=
"v242"/>
4672 <term><varname>BusErrorReporting=
</varname></term>
4674 <para>Takes a boolean. When
<literal>yes
</literal>, reporting of CAN bus errors is activated
4675 (those include single bit, frame format, and bit stuffing errors, unable to send dominant bit,
4676 unable to send recessive bit, bus overload, active error announcement, error occurred on
4677 transmission). When unset, the kernel's default will be used. Note: in case of a CAN bus with a
4678 single CAN device, sending a CAN frame may result in a huge number of CAN bus errors.
</para>
4680 <xi:include href=
"version-info.xml" xpointer=
"v248"/>
4684 <term><varname>ListenOnly=
</varname></term>
4686 <para>Takes a boolean. When
<literal>yes
</literal>, listen-only mode is enabled. When the
4687 interface is in listen-only mode, the interface neither transmit CAN frames nor send ACK
4688 bit. Listen-only mode is important to debug CAN networks without interfering with the
4689 communication or acknowledge the CAN frame. When unset, the kernel's default will be used.
4692 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4696 <term><varname>Loopback=
</varname></term>
4698 <para>Takes a boolean. When
<literal>yes
</literal>, loopback mode is enabled. When the
4699 loopback mode is enabled, the interface treats messages transmitted by itself as received
4700 messages. The loopback mode is important to debug CAN networks. When unset, the kernel's
4701 default will be used.
</para>
4703 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
4707 <term><varname>OneShot=
</varname></term>
4709 <para>Takes a boolean. When
<literal>yes
</literal>, one-shot mode is enabled. When unset,
4710 the kernel's default will be used.
</para>
4712 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
4716 <term><varname>PresumeAck=
</varname></term>
4718 <para>Takes a boolean. When
<literal>yes
</literal>, the interface will ignore missing CAN
4719 ACKs. When unset, the kernel's default will be used.
</para>
4721 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
4725 <term><varname>ClassicDataLengthCode=
</varname></term>
4727 <para>Takes a boolean. When
<literal>yes
</literal>, the interface will handle the
4bit data
4728 length code (DLC). When unset, the kernel's default will be used.
</para>
4730 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
4737 <title>[IPoIB] Section Options
</title>
4738 <para>The [IPoIB] section manages the IP over Infiniband and accepts the following keys:
</para>
4740 <variablelist class='network-directives'
>
4741 <xi:include href=
"systemd.netdev.xml" xpointer=
"ipoib_mode" />
4742 <xi:include href=
"systemd.netdev.xml" xpointer=
"ipoib_umcast" />
4747 <title>[QDisc] Section Options
</title>
4748 <para>The [QDisc] section manages the traffic control queueing discipline (qdisc).
</para>
4750 <variablelist class='network-directives'
>
4752 <term><varname>Parent=
</varname></term>
4754 <para>Specifies the parent Queueing Discipline (qdisc). Takes one of
<literal>clsact
</literal>
4755 or
<literal>ingress
</literal>. This is mandatory.
</para>
4757 <xi:include href=
"version-info.xml" xpointer=
"v244"/>
4761 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
4766 <title>[NetworkEmulator] Section Options
</title>
4767 <para>The [NetworkEmulator] section manages the queueing discipline (qdisc) of the network emulator. It
4768 can be used to configure the kernel packet scheduler and simulate packet delay and loss for UDP or TCP
4769 applications, or limit the bandwidth usage of a particular service to simulate internet connections.
4772 <variablelist class='network-directives'
>
4773 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
4774 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
4777 <term><varname>DelaySec=
</varname></term>
4779 <para>Specifies the fixed amount of delay to be added to all packets going out of the
4780 interface. Defaults to unset.
</para>
4782 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4787 <term><varname>DelayJitterSec=
</varname></term>
4789 <para>Specifies the chosen delay to be added to the packets outgoing to the network
4790 interface. Defaults to unset.
</para>
4792 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4797 <term><varname>PacketLimit=
</varname></term>
4799 <para>Specifies the maximum number of packets the qdisc may hold queued at a time.
4800 An unsigned integer in the range
0…
4294967294. Defaults to
1000.
</para>
4802 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4807 <term><varname>LossRate=
</varname></term>
4809 <para>Specifies an independent loss probability to be added to the packets outgoing from the
4810 network interface. Takes a percentage value, suffixed with
"%". Defaults to unset.
</para>
4812 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4817 <term><varname>DuplicateRate=
</varname></term>
4819 <para>Specifies that the chosen percent of packets is duplicated before queuing them.
4820 Takes a percentage value, suffixed with
"%". Defaults to unset.
</para>
4822 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4829 <title>[TokenBucketFilter] Section Options
</title>
4830 <para>The [TokenBucketFilter] section manages the queueing discipline (qdisc) of token bucket filter
4833 <variablelist class='network-directives'
>
4834 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
4835 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
4838 <term><varname>LatencySec=
</varname></term>
4840 <para>Specifies the latency parameter, which specifies the maximum amount of time a
4841 packet can sit in the Token Bucket Filter (TBF). Defaults to unset.
</para>
4843 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4848 <term><varname>LimitBytes=
</varname></term>
4850 <para>Takes the number of bytes that can be queued waiting for tokens to become available.
4851 When the size is suffixed with K, M, or G, it is parsed as Kilobytes, Megabytes, or Gigabytes,
4852 respectively, to the base of
1024. Defaults to unset.
</para>
4854 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4859 <term><varname>BurstBytes=
</varname></term>
4861 <para>Specifies the size of the bucket. This is the maximum amount of bytes that tokens
4862 can be available for instantaneous transfer. When the size is suffixed with K, M, or G, it is
4863 parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of
1024. Defaults to
4866 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4871 <term><varname>Rate=
</varname></term>
4873 <para>Specifies the device specific bandwidth. When suffixed with K, M, or G, the specified
4874 bandwidth is parsed as Kilobits, Megabits, or Gigabits, respectively, to the base of
1000.
4875 Defaults to unset.
</para>
4877 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4882 <term><varname>MPUBytes=
</varname></term>
4884 <para>The Minimum Packet Unit (MPU) determines the minimal token usage (specified in bytes)
4885 for a packet. When suffixed with K, M, or G, the specified size is parsed as Kilobytes,
4886 Megabytes, or Gigabytes, respectively, to the base of
1024. Defaults to zero.
</para>
4888 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4893 <term><varname>PeakRate=
</varname></term>
4895 <para>Takes the maximum depletion rate of the bucket. When suffixed with K, M, or G, the
4896 specified size is parsed as Kilobits, Megabits, or Gigabits, respectively, to the base of
4897 1000. Defaults to unset.
</para>
4899 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4904 <term><varname>MTUBytes=
</varname></term>
4906 <para>Specifies the size of the peakrate bucket. When suffixed with K, M, or G, the specified
4907 size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of
1024.
4908 Defaults to unset.
</para>
4910 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
4917 <title>[PIE] Section Options
</title>
4918 <para>The [PIE] section manages the queueing discipline (qdisc) of Proportional Integral
4919 controller-Enhanced (PIE).
</para>
4921 <variablelist class='network-directives'
>
4922 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
4923 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
4926 <term><varname>PacketLimit=
</varname></term>
4928 <para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
4929 incoming packets are dropped. An unsigned integer in the range
1…
4294967294. Defaults to unset and
4930 kernel's default is used.
</para>
4932 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4939 <title>[FlowQueuePIE] Section Options
</title>
4940 <para>The
<literal>[FlowQueuePIE]
</literal> section manages the queueing discipline
4941 (qdisc) of Flow Queue Proportional Integral controller-Enhanced (fq_pie).
</para>
4943 <variablelist class='network-directives'
>
4944 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
4945 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
4948 <term><varname>PacketLimit=
</varname></term>
4950 <para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
4951 incoming packets are dropped. An unsigned integer ranges
1 to
4294967294. Defaults to unset and
4952 kernel's default is used.
</para>
4954 <xi:include href=
"version-info.xml" xpointer=
"v247"/>
4961 <title>[StochasticFairBlue] Section Options
</title>
4962 <para>The [StochasticFairBlue] section manages the queueing discipline (qdisc) of stochastic fair blue
4965 <variablelist class='network-directives'
>
4966 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
4967 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
4970 <term><varname>PacketLimit=
</varname></term>
4972 <para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
4973 incoming packets are dropped. An unsigned integer in the range
0…
4294967294. Defaults to unset and
4974 kernel's default is used.
</para>
4976 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
4983 <title>[StochasticFairnessQueueing] Section Options
</title>
4984 <para>The [StochasticFairnessQueueing] section manages the queueing discipline (qdisc) of stochastic
4985 fairness queueing (sfq).
</para>
4987 <variablelist class='network-directives'
>
4988 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
4989 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
4992 <term><varname>PerturbPeriodSec=
</varname></term>
4994 <para>Specifies the interval in seconds for queue algorithm perturbation. Defaults to unset.
</para>
4996 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5003 <title>[BFIFO] Section Options
</title>
5004 <para>The [BFIFO] section manages the queueing discipline (qdisc) of Byte limited Packet First In First
5007 <variablelist class='network-directives'
>
5008 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5009 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5012 <term><varname>LimitBytes=
</varname></term>
5014 <para>Specifies the hard limit in bytes on the FIFO buffer size. The size limit prevents overflow
5015 in case the kernel is unable to dequeue packets as quickly as it receives them. When this limit is
5016 reached, incoming packets are dropped. When suffixed with K, M, or G, the specified size is parsed
5017 as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of
1024. Defaults to unset and
5018 kernel default is used.
</para>
5020 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5027 <title>[PFIFO] Section Options
</title>
5028 <para>The [PFIFO] section manages the queueing discipline (qdisc) of Packet First In First Out
5031 <variablelist class='network-directives'
>
5032 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5033 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5036 <term><varname>PacketLimit=
</varname></term>
5038 <para>Specifies the hard limit on the number of packets in the FIFO queue. The size limit prevents
5039 overflow in case the kernel is unable to dequeue packets as quickly as it receives them. When this
5040 limit is reached, incoming packets are dropped. An unsigned integer in the range
5041 0…
4294967294. Defaults to unset and kernel's default is used.
</para>
5043 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5050 <title>[PFIFOHeadDrop] Section Options
</title>
5051 <para>The [PFIFOHeadDrop] section manages the queueing discipline (qdisc) of Packet First In First Out
5052 Head Drop (pfifo_head_drop).
</para>
5054 <variablelist class='network-directives'
>
5055 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5056 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5059 <term><varname>PacketLimit=
</varname></term>
5061 <para>As in [PFIFO] section.
</para>
5063 <xi:include href=
"version-info.xml" xpointer=
"v246"/></listitem>
5069 <title>[PFIFOFast] Section Options
</title>
5070 <para>The [PFIFOFast] section manages the queueing discipline (qdisc) of Packet First In First Out Fast
5071 (pfifo_fast).
</para>
5073 <variablelist class='network-directives'
>
5074 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5075 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5080 <title>[CAKE] Section Options
</title>
5081 <para>The [CAKE] section manages the queueing discipline (qdisc) of Common Applications Kept Enhanced
5084 <variablelist class='network-directives'
>
5085 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5086 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5089 <term><varname>Bandwidth=
</varname></term>
5091 <para>Specifies the shaper bandwidth. When suffixed with K, M, or G, the specified size is
5092 parsed as Kilobits, Megabits, or Gigabits, respectively, to the base of
1000. Defaults to
5093 unset and kernel's default is used.
</para>
5095 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5100 <term><varname>AutoRateIngress=
</varname></term>
5102 <para>Takes a boolean value. Enables automatic capacity estimation based on traffic arriving
5103 at this qdisc. This is most likely to be useful with cellular links, which tend to change
5104 quality randomly. If this setting is enabled, the
<varname>Bandwidth=
</varname> setting is
5105 used as an initial estimate. Defaults to unset, and the kernel's default is used.
</para>
5107 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5112 <term><varname>OverheadBytes=
</varname></term>
5114 <para>Specifies that bytes to be addeded to the size of each packet. Bytes may be negative.
5115 Takes an integer in the range -
64…
256. Defaults to unset and kernel's default is used.
5118 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5123 <term><varname>MPUBytes=
</varname></term>
5125 <para>Rounds each packet (including overhead) up to the specified bytes. Takes an integer in
5126 the range
1…
256. Defaults to unset and kernel's default is used.
</para>
5128 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5133 <term><varname>CompensationMode=
</varname></term>
5135 <para>Takes one of
<literal>none
</literal>,
<literal>atm
</literal>, or
<literal>ptm
</literal>.
5136 Specifies the compensation mode for overhead calculation. When
<literal>none
</literal>, no
5137 compensation is taken into account. When
<literal>atm
</literal>, enables the compensation for
5138 ATM cell framing, which is normally found on ADSL links. When
<literal>ptm
</literal>, enables
5139 the compensation for PTM encoding, which is normally found on VDSL2 links and uses a
64b/
65b
5140 encoding scheme. Defaults to unset and the kernel's default is used.
</para>
5142 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5147 <term><varname>UseRawPacketSize=
</varname></term>
5149 <para>Takes a boolean value. When true, the packet size reported by the Linux kernel will be
5150 used, instead of the underlying IP packet size. Defaults to unset, and the kernel's default
5153 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5158 <term><varname>FlowIsolationMode=
</varname></term>
5160 <para>CAKE places packets from different flows into different queues, then packets from each
5161 queue are delivered fairly. This specifies whether the fairness is based on source address,
5162 destination address, individual flows, or any combination of those. The available values are:
5167 <term><option>none
</option></term>
5169 The flow isolation is disabled, and all traffic passes through a single queue.
5172 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5175 <term><option>src-host
</option></term>
5177 Flows are defined only by source address. Equivalent to the
<literal>srchost
</literal>
5178 option for
<command>tc qdisc
</command> command. See also
5179 <citerefentry project='man-pages'
><refentrytitle>tc-cake
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
5182 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5185 <term><option>dst-host
</option></term>
5187 Flows are defined only by destination address. Equivalent to the
5188 <literal>dsthost
</literal> option for
<command>tc qdisc
</command> command. See also
5189 <citerefentry project='man-pages'
><refentrytitle>tc-cake
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
5192 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5195 <term><option>hosts
</option></term>
5197 Flows are defined by source-destination host pairs. Equivalent to the same option for
5198 <command>tc qdisc
</command> command. See also
5199 <citerefentry project='man-pages'
><refentrytitle>tc-cake
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
5202 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5205 <term><option>flows
</option></term>
5207 Flows are defined by the entire
5-tuple of source address, destination address,
5208 transport protocol, source port and destination port. Equivalent to the same option for
5209 <command>tc qdisc
</command> command. See also
5210 <citerefentry project='man-pages'
><refentrytitle>tc-cake
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
5213 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5216 <term><option>dual-src-host
</option></term>
5218 Flows are defined by the
5-tuple (see
<literal>flows
</literal> in the above), and
5219 fairness is applied first over source addresses, then over individual flows. Equivalent
5220 to the
<literal>dual-srchost
</literal> option for
<command>tc qdisc
</command> command.
5222 <citerefentry project='man-pages'
><refentrytitle>tc-cake
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
5225 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5228 <term><option>dual-dst-host
</option></term>
5230 Flows are defined by the
5-tuple (see
<literal>flows
</literal> in the above), and
5231 fairness is applied first over destination addresses, then over individual flows.
5232 Equivalent to the
<literal>dual-dsthost
</literal> option for
5233 <command>tc qdisc
</command> command. See also
5234 <citerefentry project='man-pages'
><refentrytitle>tc-cake
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
5237 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5240 <term><option>triple
</option></term>
5242 Flows are defined by the
5-tuple (see
<literal>flows
</literal>), and fairness is
5243 applied over source and destination addresses, and also over individual flows.
5244 Equivalent to the
<literal>triple-isolate
</literal> option for
5245 <command>tc qdisc
</command> command. See also
5246 <citerefentry project='man-pages'
><refentrytitle>tc-cake
</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
5249 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5253 <para>Defaults to unset and the kernel's default is used.
</para>
5255 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5260 <term><varname>NAT=
</varname></term>
5262 <para>Takes a boolean value. When true, CAKE performs a NAT lookup before applying
5263 flow-isolation rules, to determine the true addresses and port numbers of the packet, to
5264 improve fairness between hosts inside the NAT. This has no practical effect when
5265 <varname>FlowIsolationMode=
</varname> is
<literal>none
</literal> or
<literal>flows
</literal>,
5266 or if NAT is performed on a different host. Defaults to unset, and the kernel's default is
5269 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5274 <term><varname>PriorityQueueingPreset=
</varname></term>
5276 <para>CAKE divides traffic into
<literal>tins
</literal>, and each tin has its own independent
5277 set of flow-isolation queues, bandwidth threshold, and priority. This specifies the preset of
5278 tin profiles. The available values are:
</para>
5282 <term><option>besteffort
</option></term>
5284 Disables priority queueing by placing all traffic in one tin.
5287 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5290 <term><option>precedence
</option></term>
5292 Enables priority queueing based on the legacy interpretation of TOS
5293 <literal>Precedence
</literal> field. Use of this preset on the modern Internet is
5297 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5300 <term><option>diffserv8
</option></term>
5302 Enables priority queueing based on the Differentiated Service
5303 (
<literal>DiffServ
</literal>) field with eight tins: Background Traffic, High
5304 Throughput, Best Effort, Video Streaming, Low Latency Transactions, Interactive Shell,
5305 Minimum Latency, and Network Control.
5308 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5311 <term><option>diffserv4
</option></term>
5313 Enables priority queueing based on the Differentiated Service
5314 (
<literal>DiffServ
</literal>) field with four tins: Background Traffic, Best Effort,
5315 Streaming Media, and Latency Sensitive.
5318 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5321 <term><option>diffserv3
</option></term>
5323 Enables priority queueing based on the Differentiated Service
5324 (
<literal>DiffServ
</literal>) field with three tins: Background Traffic, Best Effort,
5325 and Latency Sensitive.
5328 <xi:include href=
"version-info.xml" xpointer=
"v250"/></listitem>
5332 <para>Defaults to unset, and the kernel's default is used.
</para>
5334 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5339 <term><varname>FirewallMark=
</varname></term>
5341 <para>Takes an integer in the range
1…
4294967295. When specified, firewall-mark-based
5342 overriding of CAKE's tin selection is enabled. Defaults to unset, and the kernel's default is
5345 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5350 <term><varname>Wash=
</varname></term>
5352 <para>Takes a boolean value. When true, CAKE clears the DSCP fields, except for ECN bits, of
5353 any packet passing through CAKE. Defaults to unset, and the kernel's default is used.
</para>
5355 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5360 <term><varname>SplitGSO=
</varname></term>
5362 <para>Takes a boolean value. When true, CAKE will split General Segmentation Offload (GSO)
5363 super-packets into their on-the-wire components and dequeue them individually. Defaults to
5364 unset, and the kernel's default is used.
</para>
5366 <xi:include href=
"version-info.xml" xpointer=
"v250"/>
5371 <term><varname>RTTSec=
</varname></term>
5373 <para>Specifies the RTT for the filter. Takes a timespan. Typical values are e.g.
100us for
5374 extremely high-performance
10GigE+ networks like datacentre,
1ms for non-WiFi LAN connections,
5375 100ms for typical internet connections. Defaults to unset, and the kernel's default will be used.
5378 <xi:include href=
"version-info.xml" xpointer=
"v253"/>
5383 <term><varname>AckFilter=
</varname></term>
5385 <para>Takes a boolean value, or special value
<literal>aggressive
</literal>. If enabled, ACKs in
5386 each flow are queued and redundant ACKs to the upstream are dropped. If yes, the filter will always
5387 keep at least two redundant ACKs in the queue, while in
<literal>aggressive
</literal> mode, it will
5388 filter down to a single ACK. This may improve download throughput on links with very asymmetrical
5389 rate limits. Defaults to unset, and the kernel's default will be used.
</para>
5391 <xi:include href=
"version-info.xml" xpointer=
"v253"/>
5399 <title>[ControlledDelay] Section Options
</title>
5400 <para>The [ControlledDelay] section manages the queueing discipline (qdisc) of
5401 controlled delay (CoDel).
</para>
5403 <variablelist class='network-directives'
>
5404 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5405 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5408 <term><varname>PacketLimit=
</varname></term>
5410 <para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
5411 incoming packets are dropped. An unsigned integer in the range
0…
4294967294. Defaults to unset and
5412 kernel's default is used.
</para>
5414 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5419 <term><varname>TargetSec=
</varname></term>
5421 <para>Takes a timespan. Specifies the acceptable minimum standing/persistent queue delay.
5422 Defaults to unset and kernel's default is used.
</para>
5424 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5429 <term><varname>IntervalSec=
</varname></term>
5431 <para>Takes a timespan. This is used to ensure that the measured minimum delay does not
5432 become too stale. Defaults to unset and kernel's default is used.
</para>
5434 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5439 <term><varname>ECN=
</varname></term>
5441 <para>Takes a boolean. This can be used to mark packets instead of dropping them. Defaults to
5442 unset and kernel's default is used.
</para>
5444 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5449 <term><varname>CEThresholdSec=
</varname></term>
5451 <para>Takes a timespan. This sets a threshold above which all packets are marked with ECN
5452 Congestion Experienced (CE). Defaults to unset and kernel's default is used.
</para>
5454 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5461 <title>[DeficitRoundRobinScheduler] Section Options
</title>
5462 <para>The [DeficitRoundRobinScheduler] section manages the queueing discipline (qdisc) of Deficit Round
5463 Robin Scheduler (DRR).
</para>
5465 <variablelist class='network-directives'
>
5466 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5467 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5472 <title>[DeficitRoundRobinSchedulerClass] Section Options
</title>
5473 <para>The [DeficitRoundRobinSchedulerClass] section manages the traffic control class of Deficit Round
5474 Robin Scheduler (DRR).
</para>
5476 <variablelist class='network-directives'
>
5477 <xi:include href=
"tc.xml" xpointer=
"tclass-parent" />
5478 <xi:include href=
"tc.xml" xpointer=
"tclass-classid" />
5481 <term><varname>QuantumBytes=
</varname></term>
5483 <para>Specifies the amount of bytes a flow is allowed to dequeue before the scheduler moves
5484 to the next class. When suffixed with K, M, or G, the specified size is parsed as Kilobytes,
5485 Megabytes, or Gigabytes, respectively, to the base of
1024. Defaults to the MTU of the
5488 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5496 <title>[EnhancedTransmissionSelection] Section Options
</title>
5497 <para>The [EnhancedTransmissionSelection] section manages the queueing discipline (qdisc) of Enhanced
5498 Transmission Selection (ETS).
</para>
5500 <variablelist class='network-directives'
>
5501 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5502 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5505 <term><varname>Bands=
</varname></term>
5507 <para>Specifies the number of bands. An unsigned integer in the range
1…
16. This value has to be at
5508 least large enough to cover the strict bands specified through the
<varname>StrictBands=
</varname>
5509 and bandwidth-sharing bands specified in
<varname>QuantumBytes=
</varname>.
</para>
5511 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5516 <term><varname>StrictBands=
</varname></term>
5518 <para>Specifies the number of bands that should be created in strict mode. An unsigned integer in
5519 the range
1…
16.
</para>
5521 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5526 <term><varname>QuantumBytes=
</varname></term>
5528 <para>Specifies the white-space separated list of quantum used in band-sharing bands. When
5529 suffixed with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes,
5530 respectively, to the base of
1024. This setting can be specified multiple times. If an empty
5531 string is assigned, then the all previous assignments are cleared.
</para>
5533 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5538 <term><varname>PriorityMap=
</varname></term>
5540 <para>The priority map maps the priority of a packet to a band. The argument is a whitespace
5541 separated list of numbers. The first number indicates which band the packets with priority
0 should
5542 be put to, the second is for priority
1, and so on. There can be up to
16 numbers in the list. If
5543 there are fewer, the default band that traffic with one of the unmentioned priorities goes to is
5544 the last one. Each band number must be in the range
0…
255. This setting can be specified multiple
5545 times. If an empty string is assigned, then the all previous assignments are cleared.
</para>
5547 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5554 <title>[GenericRandomEarlyDetection] Section Options
</title>
5555 <para>The [GenericRandomEarlyDetection] section manages the queueing discipline (qdisc) of Generic Random
5556 Early Detection (GRED).
</para>
5558 <variablelist class='network-directives'
>
5559 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5560 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5563 <term><varname>VirtualQueues=
</varname></term>
5565 <para>Specifies the number of virtual queues. Takes an integer in the range
1…
16. Defaults to unset
5566 and kernel's default is used.
</para>
5568 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5573 <term><varname>DefaultVirtualQueue=
</varname></term>
5575 <para>Specifies the number of default virtual queue. This must be less than
<varname>VirtualQueue=
</varname>.
5576 Defaults to unset and kernel's default is used.
</para>
5578 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5583 <term><varname>GenericRIO=
</varname></term>
5585 <para>Takes a boolean. It turns on the RIO-like buffering scheme. Defaults to
5586 unset and kernel's default is used.
</para>
5588 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5595 <title>[FairQueueingControlledDelay] Section Options
</title>
5596 <para>The [FairQueueingControlledDelay] section manages the queueing discipline (qdisc) of fair queuing
5597 controlled delay (FQ-CoDel).
</para>
5599 <variablelist class='network-directives'
>
5600 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5601 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5604 <term><varname>PacketLimit=
</varname></term>
5606 <para>Specifies the hard limit on the real queue size. When this limit is reached, incoming packets are
5607 dropped. Defaults to unset and kernel's default is used.
</para>
5609 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5614 <term><varname>MemoryLimitBytes=
</varname></term>
5616 <para>Specifies the limit on the total number of bytes that can be queued in this FQ-CoDel instance.
5617 When suffixed with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes,
5618 respectively, to the base of
1024. Defaults to unset and kernel's default is used.
</para>
5620 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5625 <term><varname>Flows=
</varname></term>
5627 <para>Specifies the number of flows into which the incoming packets are classified.
5628 Defaults to unset and kernel's default is used.
</para>
5630 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5635 <term><varname>TargetSec=
</varname></term>
5637 <para>Takes a timespan. Specifies the acceptable minimum standing/persistent queue delay.
5638 Defaults to unset and kernel's default is used.
</para>
5640 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5645 <term><varname>IntervalSec=
</varname></term>
5647 <para>Takes a timespan. This is used to ensure that the measured minimum delay does not
5648 become too stale. Defaults to unset and kernel's default is used.
</para>
5650 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5655 <term><varname>QuantumBytes=
</varname></term>
5657 <para>Specifies the number of bytes used as the
"deficit" in the fair queuing algorithm timespan.
5658 When suffixed with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes,
5659 respectively, to the base of
1024. Defaults to unset and kernel's default is used.
</para>
5661 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5666 <term><varname>ECN=
</varname></term>
5668 <para>Takes a boolean. This can be used to mark packets instead of dropping them. Defaults to
5669 unset and kernel's default is used.
</para>
5671 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5676 <term><varname>CEThresholdSec=
</varname></term>
5678 <para>Takes a timespan. This sets a threshold above which all packets are marked with ECN
5679 Congestion Experienced (CE). Defaults to unset and kernel's default is used.
</para>
5681 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5688 <title>[FairQueueing] Section Options
</title>
5689 <para>The [FairQueueing] section manages the queueing discipline (qdisc) of fair queue traffic policing
5692 <variablelist class='network-directives'
>
5693 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5694 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5697 <term><varname>PacketLimit=
</varname></term>
5699 <para>Specifies the hard limit on the real queue size. When this limit is reached, incoming packets are
5700 dropped. Defaults to unset and kernel's default is used.
</para>
5702 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5707 <term><varname>FlowLimit=
</varname></term>
5709 <para>Specifies the hard limit on the maximum number of packets queued per flow. Defaults to
5710 unset and kernel's default is used.
</para>
5712 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5717 <term><varname>QuantumBytes=
</varname></term>
5719 <para>Specifies the credit per dequeue RR round, i.e. the amount of bytes a flow is allowed
5720 to dequeue at once. When suffixed with K, M, or G, the specified size is parsed as Kilobytes,
5721 Megabytes, or Gigabytes, respectively, to the base of
1024. Defaults to unset and kernel's
5722 default is used.
</para>
5724 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5729 <term><varname>InitialQuantumBytes=
</varname></term>
5731 <para>Specifies the initial sending rate credit, i.e. the amount of bytes a new flow is
5732 allowed to dequeue initially. When suffixed with K, M, or G, the specified size is parsed as
5733 Kilobytes, Megabytes, or Gigabytes, respectively, to the base of
1024. Defaults to unset and
5734 kernel's default is used.
</para>
5736 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5741 <term><varname>MaximumRate=
</varname></term>
5743 <para>Specifies the maximum sending rate of a flow. When suffixed with K, M, or G, the
5744 specified size is parsed as Kilobits, Megabits, or Gigabits, respectively, to the base of
5745 1000. Defaults to unset and kernel's default is used.
</para>
5747 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5752 <term><varname>Buckets=
</varname></term>
5754 <para>Specifies the size of the hash table used for flow lookups. Defaults to unset and
5755 kernel's default is used.
</para>
5757 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5762 <term><varname>OrphanMask=
</varname></term>
5764 <para>Takes an unsigned integer. For packets not owned by a socket, fq is able to mask a part
5765 of hash and reduce number of buckets associated with the traffic. Defaults to unset and
5766 kernel's default is used.
</para>
5768 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5773 <term><varname>Pacing=
</varname></term>
5775 <para>Takes a boolean, and enables or disables flow pacing. Defaults to unset and kernel's
5776 default is used.
</para>
5778 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5783 <term><varname>CEThresholdSec=
</varname></term>
5785 <para>Takes a timespan. This sets a threshold above which all packets are marked with ECN
5786 Congestion Experienced (CE). Defaults to unset and kernel's default is used.
</para>
5788 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5795 <title>[TrivialLinkEqualizer] Section Options
</title>
5796 <para>The [TrivialLinkEqualizer] section manages the queueing discipline (qdisc) of trivial link
5797 equalizer (teql).
</para>
5799 <variablelist class='network-directives'
>
5800 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5801 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5804 <term><varname>Id=
</varname></term>
5806 <para>Specifies the interface ID
<literal>N
</literal> of teql. Defaults to
<literal>0</literal>.
5807 Note that when teql is used, currently, the module
<constant>sch_teql
</constant> with
5808 <constant>max_equalizers=N+
1</constant> option must be loaded before
5809 <command>systemd-networkd
</command> is started.
</para>
5811 <xi:include href=
"version-info.xml" xpointer=
"v245"/>
5818 <title>[HierarchyTokenBucket] Section Options
</title>
5819 <para>The [HierarchyTokenBucket] section manages the queueing discipline (qdisc) of hierarchy token
5820 bucket (htb).
</para>
5822 <variablelist class='network-directives'
>
5823 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5824 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5827 <term><varname>DefaultClass=
</varname></term>
5829 <para>Takes the minor id in hexadecimal of the default class. Unclassified traffic gets sent
5830 to the class. Defaults to unset.
</para>
5832 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5837 <term><varname>RateToQuantum=
</varname></term>
5839 <para>Takes an unsigned integer. The DRR quantums are calculated by dividing the value
5840 configured in
<varname>Rate=
</varname> by
<varname>RateToQuantum=
</varname>.
</para>
5842 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5849 <title>[HierarchyTokenBucketClass] Section Options
</title>
5850 <para>The [HierarchyTokenBucketClass] section manages the traffic control class of hierarchy token bucket
5853 <variablelist class='network-directives'
>
5854 <xi:include href=
"tc.xml" xpointer=
"tclass-parent" />
5855 <xi:include href=
"tc.xml" xpointer=
"tclass-classid" />
5858 <term><varname>Priority=
</varname></term>
5860 <para>Specifies the priority of the class. In the round-robin process, classes with the lowest
5861 priority field are tried for packets first.
</para>
5863 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5868 <term><varname>QuantumBytes=
</varname></term>
5870 <para>Specifies how many bytes to serve from leaf at once. When suffixed with K, M, or G, the
5871 specified size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of
5874 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5879 <term><varname>MTUBytes=
</varname></term>
5881 <para>Specifies the maximum packet size we create. When suffixed with K, M, or G, the specified
5882 size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of
1024.
</para>
5884 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5889 <term><varname>OverheadBytes=
</varname></term>
5891 <para>Takes an unsigned integer which specifies per-packet size overhead used in rate
5892 computations. When suffixed with K, M, or G, the specified size is parsed as Kilobytes,
5893 Megabytes, or Gigabytes, respectively, to the base of
1024.
</para>
5895 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5900 <term><varname>Rate=
</varname></term>
5902 <para>Specifies the maximum rate this class and all its children are guaranteed. When suffixed
5903 with K, M, or G, the specified size is parsed as Kilobits, Megabits, or Gigabits, respectively,
5904 to the base of
1000. This setting is mandatory.
</para>
5906 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5911 <term><varname>CeilRate=
</varname></term>
5913 <para>Specifies the maximum rate at which a class can send, if its parent has bandwidth to spare.
5914 When suffixed with K, M, or G, the specified size is parsed as Kilobits, Megabits, or Gigabits,
5915 respectively, to the base of
1000. When unset, the value specified with
<varname>Rate=
</varname>
5918 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5923 <term><varname>BufferBytes=
</varname></term>
5925 <para>Specifies the maximum bytes burst which can be accumulated during idle period. When suffixed
5926 with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively,
5927 to the base of
1024.
</para>
5929 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5934 <term><varname>CeilBufferBytes=
</varname></term>
5936 <para>Specifies the maximum bytes burst for ceil which can be accumulated during idle period.
5937 When suffixed with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes,
5938 respectively, to the base of
1024.
</para>
5940 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5947 <title>[HeavyHitterFilter] Section Options
</title>
5948 <para>The [HeavyHitterFilter] section manages the queueing discipline (qdisc) of Heavy Hitter Filter
5951 <variablelist class='network-directives'
>
5952 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5953 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5956 <term><varname>PacketLimit=
</varname></term>
5958 <para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
5959 incoming packets are dropped. An unsigned integer in the range
0…
4294967294. Defaults to unset and
5960 kernel's default is used.
</para>
5962 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5969 <title>[QuickFairQueueing] Section Options
</title>
5970 <para>The [QuickFairQueueing] section manages the queueing discipline (qdisc) of Quick Fair Queueing
5973 <variablelist class='network-directives'
>
5974 <xi:include href=
"tc.xml" xpointer=
"qdisc-parent" />
5975 <xi:include href=
"tc.xml" xpointer=
"qdisc-handle" />
5980 <title>[QuickFairQueueingClass] Section Options
</title>
5981 <para>The [QuickFairQueueingClass] section manages the traffic control class of Quick Fair Queueing
5984 <variablelist class='network-directives'
>
5985 <xi:include href=
"tc.xml" xpointer=
"tclass-parent" />
5986 <xi:include href=
"tc.xml" xpointer=
"tclass-classid" />
5989 <term><varname>Weight=
</varname></term>
5991 <para>Specifies the weight of the class. Takes an integer in the range
1…
1023. Defaults to
5992 unset in which case the kernel default is used.
</para>
5994 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
5999 <term><varname>MaxPacketBytes=
</varname></term>
6001 <para>Specifies the maximum packet size in bytes for the class. When suffixed with K, M, or G, the
6002 specified size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of
6003 1024. When unset, the kernel default is used.
</para>
6005 <xi:include href=
"version-info.xml" xpointer=
"v246"/>
6012 <title>[BridgeVLAN] Section Options
</title>
6014 The [BridgeVLAN] section manages the VLAN ID configurations of a bridge master or port, and accepts the
6015 following keys. To make the settings in this section take an effect,
6016 <varname>VLANFiltering=
</varname> option has to be enabled on the bridge master, see the [Bridge]
6018 <citerefentry><refentrytitle>systemd.netdev
</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
6019 If at least one valid settings specified in this section in a .network file for an interface, all
6020 assigned VLAN IDs on the interface that are not configured in the .network file will be removed. If
6021 VLAN IDs on an interface need to be managed by other tools, then the settings in this section cannot
6022 be used in the matching .network file.
6025 <variablelist class='network-directives'
>
6027 <term><varname>VLAN=
</varname></term>
6029 <para>The VLAN ID allowed on the port. This can be either a single ID or a range M-N. Takes an
6030 integer in the range
1…
4094. This setting can be specified multiple times. If an empty string is
6031 assigned, then the all previous assignments are cleared.
</para>
6033 <xi:include href=
"version-info.xml" xpointer=
"v231"/>
6037 <term><varname>EgressUntagged=
</varname></term>
6039 <para>The VLAN ID specified here will be used to untag frames on egress. Configuring
6040 <varname>EgressUntagged=
</varname> implicates the use of
<varname>VLAN=
</varname> above and will
6041 enable the VLAN ID for ingress as well. This can be either a single ID or a range M-N. This
6042 setting can be specified multiple times. If an empty string is assigned, then the all previous
6043 assignments are cleared.
</para>
6045 <xi:include href=
"version-info.xml" xpointer=
"v231"/>
6049 <term><varname>PVID=
</varname></term>
6051 <para>The port VLAN ID specified here is assigned to all untagged frames at ingress. Takes an
6052 VLAN ID or negative boolean value (e.g.
<literal>no
</literal>). When false, the currently
6053 assigned port VLAN ID will be dropped. Configuring
<varname>PVID=
</varname> implicates the use of
6054 <varname>VLAN=
</varname> setting in the above and will enable the VLAN ID for ingress as well.
6055 Defaults to unset, and will keep the assigned port VLAN ID if exists.
</para>
6057 <xi:include href=
"version-info.xml" xpointer=
"v231"/>
6064 <title>Examples
</title>
6066 <title>Static network configuration
</title>
6068 <programlisting># /etc/systemd/network/
50-static.network
6073 Address=
192.168.0.15/
24
6074 Gateway=
192.168.0.1</programlisting>
6076 <para>This brings interface
<literal>enp2s0
</literal> up with a static address. The
6077 specified gateway will be used for a default route.
</para>
6081 <title>DHCP on ethernet links
</title>
6083 <programlisting># /etc/systemd/network/
80-dhcp.network
6088 DHCP=yes
</programlisting>
6090 <para>This will enable DHCPv4 and DHCPv6 on all interfaces with names starting with
6091 <literal>en
</literal> (i.e. ethernet interfaces).
</para>
6095 <title>IPv6 Prefix Delegation (DHCPv6 PD)
</title>
6097 <programlisting># /etc/systemd/network/
55-dhcpv6-pd-upstream.network
6104 # The below setting is optional, to also assign an address in the delegated prefix
6105 # to the upstream interface. If not necessary, then comment out the line below and
6106 # the [DHCPPrefixDelegation] section.
6107 DHCPPrefixDelegation=yes
6109 # If the upstream network provides Router Advertisement with Managed bit set,
6110 # then comment out the line below and WithoutRA= setting in the [DHCPv6] section.
6116 [DHCPPrefixDelegation]
6117 UplinkInterface=:self
6119 Announce=no
</programlisting>
6121 <programlisting># /etc/systemd/network/
55-dhcpv6-pd-downstream.network
6126 DHCPPrefixDelegation=yes
6129 # It is expected that the host is acting as a router. So, usually it is not
6130 # necessary to receive Router Advertisement from other hosts in the downstream network.
6133 [DHCPPrefixDelegation]
6134 UplinkInterface=enp1s0
6136 Announce=yes
</programlisting>
6138 <para>This will enable DHCPv6-PD on the interface enp1s0 as an upstream interface where the
6139 DHCPv6 client is running and enp2s0 as a downstream interface where the prefix is delegated to.
6140 The delegated prefixes are distributed by IPv6 Router Advertisement on the downstream network.
6145 <title>IPv6 Prefix Delegation (DHCPv4
6RD)
</title>
6147 <programlisting># /etc/systemd/network/
55-dhcpv4-
6rd-upstream.network
6154 # When DHCPv4-
6RD is used, the upstream network does not support IPv6.
6155 # Hence, it is not necessary to wait for Router Advertisement, which is enabled by default.
6159 Use6RD=yes
</programlisting>
6161 <programlisting># /etc/systemd/network/
55-dhcpv4-
6rd-downstream.network
6166 DHCPPrefixDelegation=yes
6169 # It is expected that the host is acting as a router. So, usually it is not
6170 # necessary to receive Router Advertisement from other hosts in the downstream network.
6173 [DHCPPrefixDelegation]
6174 UplinkInterface=enp1s0
6176 Announce=yes
</programlisting>
6178 <para>This will enable DHCPv4-
6RD on the interface enp1s0 as an upstream interface where the
6179 DHCPv4 client is running and enp2s0 as a downstream interface where the prefix is delegated to.
6180 The delegated prefixes are distributed by IPv6 Router Advertisement on the downstream network.
6185 <title>A bridge with two enslaved links
</title>
6187 <programlisting># /etc/systemd/network/
25-bridge-static.netdev
6190 Kind=bridge
</programlisting>
6192 <programlisting># /etc/systemd/network/
25-bridge-static.network
6197 Address=
192.168.0.15/
24
6199 DNS=
192.168.0.1</programlisting>
6201 <programlisting># /etc/systemd/network/
25-bridge-slave-interface-
1.network
6206 Bridge=bridge0
</programlisting>
6208 <programlisting># /etc/systemd/network/
25-bridge-slave-interface-
2.network
6213 Bridge=bridge0
</programlisting>
6215 <para>This creates a bridge and attaches devices
<literal>enp2s0
</literal> and
6216 <literal>wlp3s0
</literal> to it. The bridge will have the specified static address
6217 and network assigned, and a default route via the specified gateway will be
6218 added. The specified DNS server will be added to the global list of DNS resolvers.
6223 <title>Bridge port with VLAN forwarding
</title>
6226 # /etc/systemd/network/
25-bridge-slave-interface-
1.network
6242 EgressUntagged=
300-
400</programlisting>
6244 <para>This overrides the configuration specified in the previous example for the
6245 interface
<literal>enp2s0
</literal>, and enables VLAN on that bridge port. VLAN IDs
6246 1-
32,
42,
100-
400 will be allowed. Packets tagged with VLAN IDs
42,
300-
400 will be
6247 untagged when they leave on this interface. Untagged packets which arrive on this
6248 interface will be assigned VLAN ID
42.
</para>
6252 <title>Various tunnels
</title>
6254 <programlisting>/etc/systemd/network/
25-tunnels.network
6265 <programlisting>/etc/systemd/network/
25-tunnel-ipip.netdev
6271 <programlisting>/etc/systemd/network/
25-tunnel-sit.netdev
6277 <programlisting>/etc/systemd/network/
25-tunnel-gre.netdev
6283 <programlisting>/etc/systemd/network/
25-tunnel-vti.netdev
6289 <para>This will bring interface
<literal>ens1
</literal> up and create an IPIP tunnel,
6290 a SIT tunnel, a GRE tunnel, and a VTI tunnel using it.
</para>
6294 <title>A bond device
</title>
6296 <programlisting># /etc/systemd/network/
30-bond1.network
6304 <programlisting># /etc/systemd/network/
30-bond1.netdev
6310 <programlisting># /etc/systemd/network/
30-bond1-dev1.network
6312 MACAddress=
52:
54:
00:e9:
64:
41
6318 <programlisting># /etc/systemd/network/
30-bond1-dev2.network
6320 MACAddress=
52:
54:
00:e9:
64:
42
6326 <para>This will create a bond device
<literal>bond1
</literal> and enslave the two
6327 devices with MAC addresses
52:
54:
00:e9:
64:
41 and
52:
54:
00:e9:
64:
42 to it. IPv6 DHCP
6328 will be used to acquire an address.
</para>
6332 <title>Virtual Routing and Forwarding (VRF)
</title>
6333 <para>Add the
<literal>bond1
</literal> interface to the VRF master interface
6334 <literal>vrf1
</literal>. This will redirect routes generated on this interface to be
6335 within the routing table defined during VRF creation. For kernels before
4.8 traffic
6336 won't be redirected towards the VRFs routing table unless specific ip-rules are added.
6338 <programlisting># /etc/systemd/network/
25-vrf.network
6348 <title>MacVTap
</title>
6349 <para>This brings up a network interface
<literal>macvtap-test
</literal>
6350 and attaches it to
<literal>enp0s25
</literal>.
</para>
6351 <programlisting># /usr/lib/systemd/network/
25-macvtap.network
6356 MACVTAP=macvtap-test
6361 <title>A Xfrm interface with physical underlying device.
</title>
6363 <programlisting># /etc/systemd/network/
27-xfrm.netdev
6369 InterfaceId=
7</programlisting>
6371 <programlisting># /etc/systemd/network/
27-eth0.network
6376 Xfrm=xfrm0
</programlisting>
6378 <para>This creates a
<literal>xfrm0
</literal> interface and binds it to the
<literal>eth0
</literal> device.
6379 This allows hardware based ipsec offloading to the
<literal>eth0
</literal> nic.
6380 If offloading is not needed, xfrm interfaces can be assigned to the
<literal>lo
</literal> device.
6386 <title>See Also
</title>
6387 <para><simplelist type=
"inline">
6388 <member><citerefentry><refentrytitle>systemd
</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
6389 <member><citerefentry><refentrytitle>systemd-networkd.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
6390 <member><citerefentry><refentrytitle>systemd.link
</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
6391 <member><citerefentry><refentrytitle>systemd.netdev
</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
6392 <member><citerefentry><refentrytitle>systemd-network-generator.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
6393 <member><citerefentry><refentrytitle>systemd-resolved.service
</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
6394 </simplelist></para>