<filename>/etc/systemd/network</filename>. All configuration files are collectively sorted and
processed in alphanumeric order, regardless of the directories in which they live. However, files
with identical filenames replace each other. It is recommended that each filename is prefixed with
- a number (e.g. <filename>10-eth0.network</filename>). Otherwise, the default
- <filename>.network</filename> files or those generated by
+ a number smaller than <literal>70</literal> (e.g. <filename>10-eth0.network</filename>). Otherwise, the
+ default <filename>.network</filename> files or those generated by
<citerefentry><refentrytitle>systemd-network-generator.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
may take precedence over user configured files. Files in <filename>/etc/</filename> have the highest
priority, files in <filename>/run/</filename> take precedence over files with the same name under
configured. The first (in alphanumeric order) of the network files that matches a given interface
is applied, all later files are ignored, even if they match as well.</para>
+ <para>Note that any network interfaces that have the <varname>ID_NET_MANAGED_BY=</varname> udev property
+ set will never be matched by any .network files – unless the property's value is the string
+ <literal>io.systemd.Network</literal> – even if the [Match] section would otherwise match. This may be
+ used to exclude specific network interfaces from <command>systemd-networkd</command>'s management, while
+ keeping the [Match] section generic. The <varname>ID_NET_MANAGED_BY=</varname> property thus declares
+ intended <emphasis>ownership</emphasis> of the device, and permits ensuring that concurrent network
+ management implementations do not compete for management of specific devices.</para>
+
<para>A network file is said to match a network interface if all matches specified by the [Match]
section are satisfied. When a network file does not contain valid settings in [Match] section, then
the file will match all interfaces and <command>systemd-networkd</command> warns about that. Hint:
<para>A whitespace-separated list of shell-style globs matching the device name, as exposed
by the udev property <literal>INTERFACE</literal>, or device's alternative names. If the
list is prefixed with a "!", the test is inverted.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<literal>mesh-point</literal>, <literal>p2p-client</literal>, <literal>p2p-go</literal>,
<literal>p2p-device</literal>, <literal>ocb</literal>, and <literal>nan</literal>. If the
list is prefixed with a "!", the test is inverted. </para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<listitem>
<para>A whitespace-separated list of shell-style globs matching the SSID of the currently
connected wireless LAN. If the list is prefixed with a "!", the test is inverted.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
LAN. Use full colon-, hyphen- or dot-delimited hexadecimal. See the example in
<varname>MACAddress=</varname>. This option may appear more than once, in which case the
lists are merged. If the empty string is assigned to this option, the list is reset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<term><varname>MACAddress=</varname></term>
<listitem>
<para>The hardware address to set for the device.</para>
+
+ <xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
G, are supported and are understood to the base of 1024.</para>
<para>Note that if IPv6 is enabled on the interface, and the MTU is chosen below 1280 (the
minimum MTU for IPv6) it will automatically be increased to this value.</para>
+
+ <xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
interfaces atop a single lower-level physical interface, which will then only serve as a
link/"bridge" device aggregating traffic to the same physical link and not participate in
the network otherwise. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. If set to true, the multicast flag on the device is enabled. Defaults
to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. If set to true, the driver retrieves all multicast packets from the
network. This happens when multicast routing is enabled. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
<para>If this is set to false for the underlying link of a <literal>passthru</literal> mode
MACVLAN/MACVTAP, the virtual interface will be created with the <literal>nopromisc</literal>
flag set.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<literal>no</literal>.</para>
<para>This is useful for preventing later matching network files from interfering with
certain interfaces that are fully controlled by other applications.</para>
+
+ <xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
interfaces are added to a numbered group, operations on all the interfaces from that group
can be performed at once. Takes an unsigned integer in the range 0…2147483647. Defaults to
unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
assigned by DHCP or the cable is not plugged in, the link will simply remain offline and be
skipped automatically by <command>systemd-networkd-wait-online</command> if
<literal>RequiredForOnline=no</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v236"/>
</listitem>
</varlistentry>
<literal>any</literal>. Note that this option has no effect if
<literal>RequiredForOnline=no</literal>, or if <literal>RequiredForOnline=</literal>
specifies a minimum operational state below <literal>degraded</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
depends on both the administrative state as well as the network device's physical connection.
However, to avoid reconfiguration failures, when using <literal>always-up</literal>,
<varname>IgnoreCarrierLoss=</varname> is forced to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
</variablelist>
<term><varname>Description=</varname></term>
<listitem>
<para>A description of the device. This is only used for presentation purposes.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<para>See the [DHCPv4] or [DHCPv6] sections below for further configuration options for the
DHCP client support.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<para>Takes a boolean. If set to <literal>yes</literal>, DHCPv4 server will be started.
Defaults to <literal>no</literal>. Further settings for the DHCP server may be set in the
[DHCPServer] section described below.</para>
+
+ <xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
<varname>Bridge=</varname> is set or when the specified
<varname>MACVLAN=</varname>/<varname>MACVTAP=</varname> has <varname>Mode=passthru</varname>,
or <option>ipv6</option> otherwise.</para>
+
+ <xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
<varname>LinkLocalAddressing=</varname> is <literal>yes</literal> or <literal>ipv6</literal>,
setting <varname>IPv6LinkLocalAddressGenerationMode=none</varname>
disables to configure an IPv6 link-local address.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varname>IPv6LinkLocalAddressGenerationMode=</varname>,
then a stable secret address will be generated from the local machine ID and the interface
name.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
169.254.255.0/24. This setting may be useful if the device should always have the same address
as long as there is no address conflict. When unset, a random address will be automatically
selected. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v252"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. If set to true, sets up the route needed for non-IPv4LL hosts to
communicate with IPv4LL-only hosts. Defaults to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
<programlisting>[Route]
Gateway=::
Table=1234</programlisting></para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
registration and announcement. Defaults to true. This setting is read by
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
registration and announcement. Defaults to false. This setting is read by
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v229"/>
</listitem>
</varlistentry>
be used. This setting is read by
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
used. This setting is read by
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v229"/>
</listitem>
</varlistentry>
read by
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v229"/>
</listitem>
</varlistentry>
to query the collected neighbor data. LLDP is only available on Ethernet links. See
<varname>EmitLLDP=</varname> below for enabling LLDP packet emission from the local system.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
Note that configuring this setting to true is equivalent to
<literal>nearest-bridge</literal>, the recommended and most restricted level of propagation.
See <varname>LLDP=</varname> above for an option to enable LLDP reception.</para>
+
+ <xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
<para>This forces <varname>ActivationPolicy=</varname> to be set to <literal>bound</literal>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
10.0.0.0/8 for IPv4, and fd00::/8 for IPv6. This functionality is useful to manage a large
number of dynamically created network interfaces with the same network configuration and
automatic address range assignment.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<citerefentry project='man-pages'><refentrytitle>inet_pton</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
This is a short-hand for a [Route] section only containing a <varname>Gateway=</varname> key.
This option may be specified more than once.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
assigned, then the all previous assignments are cleared. This setting is read by
<citerefentry><refentrytitle>systemd-resolved.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<citerefentry project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Domain name routing has no equivalent in the traditional glibc API, which has no concept of
domain name servers limited to a specific link.</para>
+
+ <xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
this link. If not specified defaults to an automatic mode: queries not matching any link's
configured domains will be routed to this link if it has no routing-only domains configured.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
specified more than once. This setting is read by
<citerefentry><refentrytitle>systemd-timesyncd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
<para>To allow IP packet forwarding only between specific network interfaces use a firewall.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
<literal>yes</literal>.</para>
<para>Note. Any positive boolean values such as <literal>yes</literal> or
<literal>true</literal> are now deprecated. Please use one of the values in the above.</para>
+
+ <xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
the value specified in the same setting in
<citerefentry><refentrytitle>networkd.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
which defaults to <literal>no</literal>, will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v222"/>
</listitem>
</varlistentry>
<command>systemd-networkd</command> needs to know all details supplied in the advertisements,
and these are not available from the kernel if the kernel's own implementation is used.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
<listitem>
<para>Configures the amount of IPv6 Duplicate Address Detection (DAD) probes to send. When
unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v228"/>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>IPv6HopLimit=</varname></term>
<listitem>
- <para>Configures IPv6 Hop Limit. For each router that forwards the packet, the hop limit is
- decremented by 1. When the hop limit field reaches zero, the packet is discarded. When unset,
- the kernel's default will be used.</para>
+ <para>Configures IPv6 Hop Limit. Takes an integer in the range 1…255. For each router that
+ forwards the packet, the hop limit is decremented by 1. When the hop limit field reaches zero, the
+ packet is discarded. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v228"/>
</listitem>
</varlistentry>
only if the source address is not reachable via any interface on that router.
See <ulink url="https://tools.ietf.org/html/rfc1027">RFC 3704</ulink>.
When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<para>Takes a boolean. Accept packets with local source addresses. In combination with
suitable routing, this can be used to direct packets between two local interfaces over the
wire and have them accepted properly. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Takes a boolean. When true, the kernel does not consider loopback addresses as martian
source or destination while routing. This enables the use of 127.0.0.0/8 for local routing
purposes. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
identity, the router accepts responsibility for routing packets to the "real" destination.
See <ulink url="https://tools.ietf.org/html/rfc1027">RFC 1027</ulink>. When unset, the
kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
also be shown by <command>ip -6 neighbour show proxy</command>. systemd-networkd will control
the per-interface `proxy_ndp` switch for each configured interface depending on this option.
When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
This setting implies <varname>IPv6ProxyNDP=yes</varname> but has no effect if
<varname>IPv6ProxyNDP=</varname> has been set to false. When unset, the kernel's default will
be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
distributed. See <varname>DCHPPrefixDelegation=</varname> setting and the [IPv6SendRA],
[IPv6Prefix], [IPv6RoutePrefix], and [DHCPPrefixDelegation] sections for more configuration
options.</para>
+
+ <xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
be assigned, and the prefixes will be announced through IPv6 Router Advertisement if
<varname>IPv6SendRA=</varname> is enabled. This behaviour can be configured in the
[DHCPPrefixDelegation] section. Defaults to disabled.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<listitem>
<para>Configures IPv6 maximum transmission unit (MTU). An integer greater than or equal to
1280 bytes. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
useful when a netdev with a master interface is created by another program, e.g.
<citerefentry><refentrytitle>systemd-nspawn</refentrytitle><manvolnum>1</manvolnum></citerefentry>.
Defaults to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
to. See
<citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
VXLAN, or Xfrm to be created on the link. See
<citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
This option may be specified more than once.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<para>Takes a boolean. Specifies the new active slave. The <literal>ActiveSlave=</literal>
option is only valid for following modes: <literal>active-backup</literal>,
<literal>balance-alb</literal>, and <literal>balance-tlb</literal>. Defaults to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
when one slave has higher throughput than another. The <literal>PrimarySlave=</literal>
option is only valid for following modes: <literal>active-backup</literal>,
<literal>balance-alb</literal>, and <literal>balance-tlb</literal>. Defaults to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<para>Takes a boolean. Allows networkd to configure a specific link even if it has no
carrier. Defaults to false. If enabled, and the <varname>IgnoreCarrierLoss=</varname> setting
is not explicitly set, then it is enabled as well.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<varname>ConfigureWithoutCarrier=</varname>. When <varname>ActivationPolicy=</varname> is set
to <literal>always-up</literal>, this is forced to <literal>yes</literal>, and ignored any
user specified values.</para>
+
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<literal>dhcp-on-stop</literal> when <command>systemd-networkd</command> is running in
initrd, <literal>yes</literal> when the root filesystem is a network filesystem, and
<literal>no</literal> otherwise.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>As in the [Network] section. This setting is mandatory. Each [Address] section can
contain one <varname>Address=</varname> setting.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<listitem>
<para>The peer address in a point-to-point connection. Accepts the same format as the
<varname>Address=</varname> setting.</para>
+
+ <xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
If set to true, then the IPv4 broadcast address will be derived from the
<varname>Address=</varname> setting. If set to false, then the broadcast address will not be
set. Defaults to true, except for wireguard interfaces, where it default to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the label for the IPv4 address. The label must be a 7-bit ASCII string with
a length of 1…15 characters. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
requested. A setting of <option>PreferredLifetime=0</option> is useful for addresses which
are added to be used only by a specific application, which is then configured to use them
explicitly.</para>
+
+ <xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
the network, even through a gateway), <literal>link</literal> (only valid on this device,
will not traverse a gateway) or <literal>host</literal> (only valid within the device itself,
e.g. 127.0.0.1) or an integer in the range 0…255. Defaults to <literal>global</literal>.
+ IPv4 only - IPv6 scope is automatically assigned by the kernel and cannot be set manually.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
address, taking the configured prefix length into account. Takes an unsigned integer in the
range 0…4294967295. When unset or set to 0, the kernel's default value is used. This
setting will be ignored when <varname>AddPrefixRoute=</varname> is false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Takes a boolean. Designates this address the "home address" as defined in
<ulink url="https://tools.ietf.org/html/rfc6275">RFC 6275</ulink>. Supported only on IPv6.
Defaults to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
<ulink url="https://tools.ietf.org/html/rfc4862">RFC 4862</ulink>. Defaults to
<literal>ipv4</literal> for IPv4 link-local addresses, <literal>ipv6</literal> for IPv6
addresses, and <literal>none</literal> otherwise.</para>
+
+ <xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
needs to have a prefix length of 64. This flag allows using privacy extensions in a manually
configured network, just like if stateless auto-configuration was active. Defaults to false.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. When true, the prefix route for the address is automatically added.
Defaults to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
with option <literal>autojoin</literal> we can get similar functionality for openvswitch (OVS)
vxlan interfaces as well as other tunneling mechanisms that need to receive multicast traffic.
Defaults to <literal>no</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
to only allow <literal>my_server_t</literal> (and nothing else) to receive data from local subnet
10.0.0.0/8 of interface <literal>eth0</literal>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v252"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>NFTSet=</varname><replaceable>source</replaceable>:<replaceable>family</replaceable>:<replaceable>table</replaceable>:<replaceable>set</replaceable></term>
+ <listitem>
+ <para>This setting provides a method for integrating network configuration into firewall rules with
+ <ulink url="https://netfilter.org/projects/nftables/index.html">NFT</ulink> sets. The benefit of
+ using the setting is that static network configuration (or dynamically obtained network addresses,
+ see similar directives in other sections) can be used in firewall rules with the indirection of NFT
+ set types. For example, access could be granted for hosts in the local subnetwork only. Firewall
+ rules using IP address of an interface are also instantly updated when the network configuration
+ changes, for example via DHCP.</para>
+
+ <para>This option expects a whitespace separated list of NFT set definitions. Each definition
+ consists of a colon-separated tuple of source type (one of <literal>address</literal>,
+ <literal>prefix</literal> or <literal>ifindex</literal>), NFT address family (one of
+ <literal>arp</literal>, <literal>bridge</literal>, <literal>inet</literal>, <literal>ip</literal>,
+ <literal>ip6</literal>, or <literal>netdev</literal>), table name and set name. The names of tables
+ and sets must conform to lexical restrictions of NFT table names. The type of the element used in
+ the NFT filter must match the type implied by the directive (<literal>address</literal>,
+ <literal>prefix</literal> or <literal>ifindex</literal>) and address type (IPv4 or IPv6) as shown
+ in the table below.</para>
+
+ <table>
+ <title>Defined <varname>source type</varname> values</title>
+ <tgroup cols='3'>
+ <colspec colname='source type'/>
+ <colspec colname='description'/>
+ <colspec colname='NFT type name'/>
+ <thead>
+ <row>
+ <entry>Source type</entry>
+ <entry>Description</entry>
+ <entry>Corresponding NFT type name</entry>
+ </row>
+ </thead>
+
+ <tbody>
+ <row>
+ <entry><literal>address</literal></entry>
+ <entry>host IP address</entry>
+ <entry><literal>ipv4_addr</literal> or <literal>ipv6_addr</literal></entry>
+ </row>
+ <row>
+ <entry><literal>prefix</literal></entry>
+ <entry>network prefix</entry>
+ <entry><literal>ipv4_addr</literal> or <literal>ipv6_addr</literal>, with <literal>flags interval</literal></entry>
+ </row>
+ <row>
+ <entry><literal>ifindex</literal></entry>
+ <entry>interface index</entry>
+ <entry><literal>iface_index</literal></entry>
+ </row>
+ </tbody>
+ </tgroup>
+ </table>
+
+ <para>When an interface is configured with IP addresses, the addresses, subnetwork masks or
+ interface index will be appended to the NFT sets. The information will be removed when the
+ interface is deconfigured. <command>systemd-networkd</command> only inserts elements to (or removes
+ from) the sets, so the related NFT rules, tables and sets must be prepared elsewhere in
+ advance. Failures to manage the sets will be ignored.</para>
+
+ <para>Example:
+ <programlisting>[Address]
+NFTSet=prefix:netdev:filter:eth_ipv4_prefix</programlisting>
+ Corresponding NFT rules:
+ <programlisting>table netdev filter {
+ set eth_ipv4_prefix {
+ type ipv4_addr
+ flags interval
+ }
+ chain eth_ingress {
+ type filter hook ingress device "eth0" priority filter; policy drop;
+ ip daddr != @eth_ipv4_prefix drop
+ accept
+ }
+}</programlisting>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
</variablelist>
<term><varname>Address=</varname></term>
<listitem>
<para>The IP address of the neighbor.</para>
+
+ <xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
<term><varname>LinkLayerAddress=</varname></term>
<listitem>
<para>The link layer address (MAC address or IP address) of the neighbor.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>The label for the prefix, an unsigned integer in the range 0…4294967294. 0xffffffff is
reserved. This setting is mandatory.</para>
+
+ <xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
<listitem>
<para>IPv6 prefix is an address with a prefix length, separated by a slash
<literal>/</literal> character. This setting is mandatory. </para>
+
+ <xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
</variablelist>
and <ulink url="https://en.wikipedia.org/wiki/Differentiated_services">Differentiated services</ulink>
for more details.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the source address prefix to match. Possibly followed by a slash and the
prefix length.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the destination address prefix to match. Possibly followed by a slash and the
prefix length.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<para>Specifies the iptables firewall mark value to match (a number in the range
1…4294967295). Optionally, the firewall mask (also a number between 1…4294967295) can be
suffixed with a slash (<literal>/</literal>), e.g., <literal>7/255</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<literal>local</literal>, and names defined in <varname>RouteTable=</varname> in
<citerefentry><refentrytitle>networkd.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
or a number between 1 and 4294967295. Defaults to <literal>main</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<para>Specifies the priority of this rule. <varname>Priority=</varname> is an integer in the
range 0…4294967295. Higher number means lower priority, and rules get processed in order of
increasing number. Defaults to unset, and the kernel will pick a value dynamically.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies incoming device to match. If the interface is loopback, the rule only matches
packets originating from this host.</para>
+
+ <xi:include href="version-info.xml" xpointer="v236"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the outgoing device to match. The outgoing interface is only available for
packets originating from local sockets that are bound to a device.</para>
+
+ <xi:include href="version-info.xml" xpointer="v236"/>
</listitem>
</varlistentry>
<para>Specifies the source IP port or IP port range match in forwarding information base
(FIB) rules. A port range is specified by the lower and upper port separated by a dash.
Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
<para>Specifies the destination IP port or IP port range match in forwarding information base
(FIB) rules. A port range is specified by the lower and upper port separated by a dash.
Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
<literal>sctp</literal>, or IP protocol number such as <literal>6</literal> for
<literal>tcp</literal> or <literal>17</literal> for <literal>udp</literal>. Defaults to unset.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
<term><varname>InvertRule=</varname></term>
<listitem>
<para>A boolean. Specifies whether the rule is to be inverted. Defaults to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
specified in <varname>To=</varname> or <varname>From=</varname>. If neither
<varname>To=</varname> nor <varname>From=</varname> are specified, then defaults to
<literal>ipv4</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a username, a user ID, or a range of user IDs separated by a dash. Defaults to
unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>Takes a number <replaceable>N</replaceable> in the range 0…128 and rejects routing
decisions that have a prefix length of <replaceable>N</replaceable> or less. Defaults to
unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>Takes an integer in the range 0…2147483647 and rejects routing decisions that have
an interface with the same group id. It has the same meaning as
<option>suppress_ifgroup</option> in <command>ip rule</command>. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<para>Specifies Routing Policy Database (RPDB) rule type. Takes one of
<literal>blackhole</literal>, <literal>unreachable</literal> or <literal>prohibit</literal>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>The id of the next hop. Takes an integer in the range 1…4294967295. If unspecified,
then automatically chosen by kernel.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<term><varname>Gateway=</varname></term>
<listitem>
<para>As in the [Network] section.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
By default, the family is determined by the address specified in
<varname>Gateway=</varname>. If <varname>Gateway=</varname> is not specified, then defaults
to <literal>ipv4</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
reachable directly by the current machine (i.e., attached to the local network), so that we
can insert the nexthop in the kernel table without it being complained about. Defaults to
<literal>no</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<para>Takes a boolean. If enabled, packets to the corresponding routes are discarded
silently, and <varname>Gateway=</varname> cannot be specified. Defaults to
<literal>no</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<varname>Family=</varname>, <varname>Blackhole=</varname>. This setting can be specified
multiple times. If an empty string is assigned, then the all previous assignments are
cleared. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
</variablelist>
<para>Takes the gateway address or the special values <literal>_dhcp4</literal> and
<literal>_ipv6ra</literal>. If <literal>_dhcp4</literal> or <literal>_ipv6ra</literal> is
set, then the gateway address provided by DHCPv4 or IPv6 RA is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
reachable directly by the current machine (i.e., attached to the local network), so that we
can insert the route in the kernel table without it being complained about. Defaults to
<literal>no</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
<listitem>
<para>The destination prefix of the route. Possibly followed by a slash and the prefix
length. If omitted, a full-length host route is assumed.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<listitem>
<para>The source prefix of the route. Possibly followed by a slash and the prefix length. If
omitted, a full-length host route is assumed.</para>
+
+ <xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
<listitem>
<para>The metric of the route. Takes an unsigned integer in the range 0…4294967295. Defaults
to unset, and the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
messages. Which can be one of <literal>low</literal> the route has a lowest priority,
<literal>medium</literal> the route has a default priority or <literal>high</literal> the
route has a highest priority.</para>
+
+ <xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
<varname>Type=</varname> is <literal>broadcast</literal>, <literal>multicast</literal>,
<literal>anycast</literal>, or <literal>unicast</literal>. In other cases,
defaults to <literal>global</literal>. The value is not used for IPv6.</para>
+
+ <xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
in
<citerefentry project='man-pages'><refentrytitle>inet_pton</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v227"/>
</listitem>
</varlistentry>
<varname>Type=</varname> is <literal>local</literal>, <literal>broadcast</literal>,
<literal>anycast</literal>, or <literal>nat</literal>, then <literal>local</literal> is used.
In other cases, defaults to <literal>main</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
<listitem>
<para>Configures per route hop limit. Takes an integer in the range 1…255. See also
<varname>IPv6HopLimit=</varname>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
values <literal>kernel</literal>, <literal>boot</literal>, <literal>static</literal>,
<literal>ra</literal> and <literal>dhcp</literal>. Defaults to <literal>static</literal>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
is generated. If <literal>throw</literal>, route lookup in the current routing table will
fail and the route selection process will return to Routing Policy Database (RPDB). Defaults
to <literal>unicast</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
without waiting for acknowledgement. Takes a number between 1 and 1023. Note that 100 is
considered an extremely large value for this option. When unset, the kernel's default
(typically 10) will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v237"/>
</listitem>
</varlistentry>
that amount of data before waiting for an acknowledgment and window update from the
receiving host. Takes a number between 1 and 1023. Note that 100 is considered an extremely
large value for this option. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v237"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. When true, the TCP quick ACK mode for the route is enabled. When unset,
the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v237"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. When true enables TCP fastopen without a cookie on a per-route basis.
When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. When true enables TTL propagation at Label Switched Path (LSP) egress.
When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<listitem>
<para>The maximum transmission unit in bytes to set for the route. The usual suffixes K, M,
G, are supported and are understood to the base of 1024.</para>
+
+ <xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
<para>Specifies the Path MSS (in bytes) hints given on TCP layer. The usual suffixes K, M, G,
are supported and are understood to the base of 1024. An unsigned integer in the range
1…4294967294. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<para>Specifies the TCP congestion control algorithm for the route. Takes a name of the algorithm,
e.g. <literal>bbr</literal>, <literal>dctcp</literal>, or <literal>vegas</literal>. When unset,
the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v252"/>
</listitem>
</varlistentry>
<para>Specifies the TCP Retransmission Timeout (RTO) for the route. Takes time values in seconds.
This value specifies the timeout of an alive TCP connection, when retransmissions remain
unacknowledged. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
interface name or index separated with <literal>@</literal>, and a weight in 1..256 for this
multipath route separated with whitespace. This setting can be specified multiple times. If
an empty string is assigned, then the all previous assignments are cleared.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the nexthop id. Takes an unsigned integer in the range 1…4294967295. If set,
the corresponding [NextHop] section must be configured. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
</variablelist>
<!-- DHCP packet contents -->
+ <varlistentry>
+ <term><varname>RequestAddress=</varname></term>
+ <listitem>
+ <para>Takes an IPv4 address. When specified, the Requested IP Address option (option code 50) is
+ added with it to the initial DHCPDISCOVER message sent by the DHCP client. Defaults to unset, and
+ an already assigned dynamic address to the interface is automatically picked.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
+ </listitem>
+ </varlistentry>
+
<varlistentry>
<term><varname>SendHostname=</varname></term>
<listitem>
hostname must consist only of 7-bit ASCII lower-case characters and no spaces or dots, and be
formatted as a valid DNS domain name. Otherwise, the hostname is not sent even if this option
is true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
<para>Use this value for the hostname which is sent to the DHCP server, instead of machine's
hostname. Note that the specified hostname must consist only of 7-bit ASCII lower-case
characters and no spaces or dots, and be formatted as a valid DNS domain name.</para>
+
+ <xi:include href="version-info.xml" xpointer="v223"/>
</listitem>
</varlistentry>
to advertise device specifications, including the intended communication patterns for their
device when it connects to the network. The network can then use this to author a
context-specific access policy, so the device functions only within those parameters.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
DUID, is used. IAID can be configured by <varname>IAID=</varname>. DUID can be configured by
<varname>DUIDType=</varname> and <varname>DUIDRawData=</varname>. Defaults to
<option>duid</option>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
<term><varname>VendorClassIdentifier=</varname></term>
<listitem>
<para>The vendor class identifier used to identify vendor type and configuration.</para>
+
+ <xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
represents the user class of which the client is a member. Each class sets an identifying
string of information to be used by the DHCP service to classify clients. Takes a
whitespace-separated list of strings.</para>
+
+ <xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
<para>Override the global <varname>DUIDType=</varname> setting for this network. See
<citerefentry><refentrytitle>networkd.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for a description of possible values.</para>
+
+ <xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
<para>Override the global <varname>DUIDRawData=</varname> setting for this network. See
<citerefentry><refentrytitle>networkd.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>
for a description of possible values.</para>
+
+ <xi:include href="version-info.xml" xpointer="v230"/>
</listitem>
</varlistentry>
<listitem>
<para>The DHCP Identity Association Identifier (IAID) for the interface, a 32-bit unsigned
integer.</para>
+
+ <xi:include href="version-info.xml" xpointer="v230"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>RapidCommit=</varname></term>
+ <listitem>
+ <para>Takes a boolean. The DHCPv4 client can obtain configuration parameters from a DHCPv4 server
+ through a rapid two-message exchange (discover and ack). When the rapid commit option is set by
+ both the DHCPv4 client and the DHCPv4 server, the two-message exchange is used. Otherwise, the
+ four-message exchange (discover, offer, request, and ack) is used. The two-message exchange
+ provides faster client configuration. See
+ <ulink url="https://tools.ietf.org/html/rfc4039">RFC 4039</ulink> for details.
+ Defaults to true when <varname>Anonymize=no</varname> and neither <varname>AllowList=</varname>
+ nor <varname>DenyList=</varname> is specified, and false otherwise.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<citerefentry><refentrytitle>systemd.link</refentrytitle><manvolnum>5</manvolnum></citerefentry>).
</para>
- <para>When true, <varname>SendHostname=</varname>, <varname>ClientIdentifier=</varname>,
- <varname>VendorClassIdentifier=</varname>, <varname>UserClass=</varname>,
- <varname>RequestOptions=</varname>, <varname>SendOption=</varname>,
- <varname>SendVendorOption=</varname>, and <varname>MUDURL=</varname> are ignored.</para>
+ <para>When true,
+ <varname>ClientIdentifier=mac</varname>,
+ <varname>RapidCommit=no</varname>,
+ <varname>SendHostname=no</varname>,
+ <varname>Use6RD=no</varname>,
+ <varname>UseCaptivePortal=no</varname>,
+ <varname>UseMTU=no</varname>,
+ <varname>UseNTP=no</varname>,
+ <varname>UseSIP=no</varname>, and
+ <varname>UseTimezone=no</varname>
+ are implied and these settings in the .network file are silently ignored. Also,
+ <varname>Hostname=</varname>,
+ <varname>MUDURL=</varname>,
+ <varname>RequestAddress</varname>,
+ <varname>RequestOptions=</varname>,
+ <varname>SendOption=</varname>,
+ <varname>SendVendorOption=</varname>,
+ <varname>UserClass=</varname>, and
+ <varname>VendorClassIdentifier=</varname>
+ are silently ignored.</para>
<para>With this option enabled DHCP requests will mimic those generated by Microsoft
Windows, in order to reduce the ability to fingerprint and recognize installations. This
means DHCP request sizes will grow and lease data will be more comprehensive than normally,
though most of the requested data is not actually used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<listitem>
<para>Sets request options to be sent to the server in the DHCPv4 request options list. A
whitespace-separated list of integers in the range 1…254. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<ulink url="https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
escapes</ulink>. This setting can be specified multiple times. If an empty string is
specified, then all options specified earlier are cleared. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<ulink url="https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
escapes</ulink>. This setting can be specified multiple times. If an empty string is specified,
then all options specified earlier are cleared. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
sent from the DHCPv4 client. When <literal>CS6</literal> (network control) or
<literal>CS4</literal> (realtime), the corresponding service type will be set. Defaults to
<literal>CS6</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
file to set the 802.1Q VLAN ethernet tagged header priority, see
<citerefentry><refentrytitle>systemd.netdev</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v253"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the label for the IPv4 address received from the DHCP server. The label must
be a 7-bit ASCII string with a length of 1…15 characters. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<para>This corresponds to the <option>nameserver</option> option in
<citerefentry project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<para>When true, the routes to the DNS servers received from the DHCP server will be
configured. When <varname>UseDNS=</varname> is disabled, this setting is ignored. Defaults to
true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<listitem>
<para>When true (the default), the NTP servers received from the DHCP server will be used by
<filename>systemd-timesyncd.service</filename>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v220"/>
</listitem>
</varlistentry>
<para>When true, the routes to the NTP servers received from the DHCP server will be
configured. When <varname>UseNTP=</varname> is disabled, this setting is ignored. Defaults to
true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
<listitem>
<para>When true (the default), the SIP servers received from the DHCP server will be collected
and made available to client programs.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<term><varname>UseCaptivePortal=</varname></term>
<listitem>
<para>When true (the default), the captive portal advertised by the DHCP server will be recorded
- and made available to client programs and displayed in the networkctl status output per-link.</para>
+ and made available to client programs and displayed in the
+ <citerefentry><refentrytitle>networkctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+ status output per-link.</para>
+
+ <xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
</varlistentry>
<para>Note, some drivers will reset the interfaces if the MTU is changed. For such
interfaces, please try to use <varname>IgnoreCarrierLoss=</varname> with a short timespan,
e.g. <literal>3 seconds</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<listitem>
<para>When true (the default), the hostname received from the DHCP server will be set as the
transient hostname of the system.</para>
+
+ <xi:include href="version-info.xml" xpointer="v211"/>
</listitem>
</varlistentry>
<para>When set to true, this setting corresponds to the <option>domain</option> option in
<citerefentry project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
own address, the scope will be set to <option>host</option>. Otherwise if the gateway is null
(a direct route), a <option>link</option> scope will be used. For anything else, scope
defaults to <option>global</option>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v215"/>
</listitem>
</varlistentry>
<para>Set the routing metric for routes specified by the DHCP server (including the prefix
route added for the specified prefix). Takes an unsigned integer in the range 0…4294967295.
Defaults to 1024.</para>
+
+ <xi:include href="version-info.xml" xpointer="v217"/>
</listitem>
</varlistentry>
<para>When used in combination with <varname>VRF=</varname>, the VRF's routing table is
used when this parameter is not specified.</para>
+
+ <xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the MTU for the DHCP routes. Please see the [Route] section for further
details.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. When true, the TCP quick ACK mode is enabled for the routes configured by
the acquired DHCPv4 lease. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v253"/>
</listitem>
</varlistentry>
<term><varname>InitialCongestionWindow=</varname></term>
<listitem>
<para>As in the [Route] section.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<term><varname>InitialAdvertisedReceiveWindow=</varname></term>
<listitem>
<para>As in the [Route] section.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>UseGateway=</varname></term>
<listitem>
- <para>When true, the gateway will be requested from the DHCP server and added to the routing
- table with a metric of 1024, and a scope of <option>link</option>. When unset, the value
- specified with <varname>UseRoutes=</varname> is used.</para>
+ <para>When true, and the DHCP server provides a Router option, the default gateway based on the
+ router address will be configured. Defaults to unset, and the value specified with
+ <varname>UseRoutes=</varname> will be used.</para>
+
+ <para>Note, when the server provides both the Router and Classless Static Routes option, and
+ <varname>UseRoutes=</varname> is enabled, the Router option is always ignored regardless of this
+ setting. See <ulink url="https://datatracker.ietf.org/doc/html/rfc3442">RFC 3442</ulink>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>UseTimezone=</varname></term>
<listitem><para>When true, the timezone received from the DHCP server will be set as timezone
- of the local system. Defaults to false.</para></listitem>
+ of the local system. Defaults to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v226"/></listitem>
</varlistentry>
<varlistentry>
<varname>DHCPPrefixDelegation=</varname> in the [Network] section, the [DHCPPrefixDelegation]
section, and <ulink url="https://tools.ietf.org/html/rfc5969">RFC 5969</ulink>. Defaults to
false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>IPv6OnlyMode=</varname></term>
+ <listitem>
+ <para>When true, the DHCPv4 configuration will be delayed by the timespan provided by the DHCP
+ server and skip to configure dynamic IPv4 network connectivity if IPv6 connectivity is provided
+ within the timespan. See <ulink url="https://tools.ietf.org/html/rfc8925">RFC 8925</ulink>.
+ Defaults to true when <varname>IPv6AcceptRA=</varname> is enabled or DHCPv6 client is enabled
+ (i.e., <varname>DHCP=yes</varname>), and false otherwise.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<para>Allows one to set DHCPv4 lease lifetime when DHCPv4 server does not send the lease
lifetime. Takes one of <literal>forever</literal> or <literal>infinity</literal>. If
specified, the acquired address never expires. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
This is necessary for devices that cannot receive RAW packets, or that cannot receive packets
at all before an IP address has been configured. On the other hand, this must not be enabled
on networks where broadcasts are filtered out.</para>
+
+ <xi:include href="version-info.xml" xpointer="v216"/>
</listitem>
</varlistentry>
time between retries is increased exponentially, up to approximately one per minute, so the
network will not be overloaded even if this number is high. The default is suitable in most
circumstances.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<term><varname>ListenPort=</varname></term>
<listitem>
<para>Set the port from which the DHCP client packets originate.</para>
+
+ <xi:include href="version-info.xml" xpointer="v233"/>
</listitem>
</varlistentry>
prefix length after <literal>/</literal>. DHCP offers from servers in the list are rejected.
Note that if <varname>AllowList=</varname> is configured then <varname>DenyList=</varname> is
ignored.</para>
+ <para>Note that this filters only DHCP offers, so the filtering may not work when
+ <varname>RapidCommit=</varname> is enabled. See also <varname>RapidCommit=</varname> in the above.
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>A whitespace-separated list of IPv4 addresses. Each address can optionally take a
prefix length after <literal>/</literal>. DHCP offers from servers in the list are accepted.
</para>
+ <para>Note that this filters only DHCP offers, so the filtering may not work when
+ <varname>RapidCommit=</varname> is enabled. See also <varname>RapidCommit=</varname> in the above.
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>When true, the DHCPv4 client sends a DHCP release packet when it stops. Defaults to
true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
the DHCPv4 client rejects the address by sending a <constant>DHCPDECLINE</constant> packet to
the DHCP server, and tries to obtain an IP address again. See
<ulink url="https://tools.ietf.org/html/rfc5227">RFC 5227</ulink>. Defaults to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>This applies the NetLabel for the addresses received with DHCP, like
<varname>NetLabel=</varname> in [Address] section applies it to statically configured
addresses. See <varname>NetLabel=</varname> in [Address] section for more details.</para>
+
+ <xi:include href="version-info.xml" xpointer="v252"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>NFTSet=</varname></term>
+ <listitem>
+ <para>This applies the NFT set for the network configuration received with DHCP, like
+ <varname>NFTSet=</varname> in [Address] section applies it to static configuration. See
+ <varname>NFTSet=</varname> in [Address] section for more details. For <literal>address</literal> or
+ <literal>prefix</literal> source types, the type of the element used in the NFT filter must be
+ <literal>ipv4_addr</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
</variablelist>
<term><varname>RequestOptions=</varname></term>
<listitem>
<para>As in the [DHCPv4] section.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>As in the [DHCPv4] section, however because DHCPv6 uses 16-bit fields to store option
numbers, the option number is an integer in the range 1…65536.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<ulink url="https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
escapes</ulink>. This setting can be specified multiple times. If an empty string is
specified, then all options specified earlier are cleared. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
escapes</ulink>. This setting can be specified multiple times. If an empty string is
specified, then all options specified earlier are cleared. Takes a whitespace-separated list
of strings. Note that currently <constant>NUL</constant> bytes are not allowed.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
hardware on which the client is running. The information contained in the data area of this
option is contained in one or more opaque fields that identify details of the hardware
configuration. Takes a whitespace-separated list of strings.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varname>Address=</varname> in the [Network] section. The DHCPv6 client will include a prefix
hint in the DHCPv6 solicitation sent to the server. The prefix length must be in the range
1…128. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
provides faster client configuration. See
<ulink url="https://tools.ietf.org/html/rfc3315#section-17.2.1">RFC 3315</ulink> for details.
Defaults to true, and the two-message exchange will be used if the server support it.</para>
+
+ <xi:include href="version-info.xml" xpointer="v252"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>SendHostname=</varname></term>
+ <listitem>
+ <para>When true (the default), the machine's hostname (or the value specified with
+ <varname>Hostname=</varname>, described below) will be sent to the DHCPv6 server. Note that the
+ hostname must consist only of 7-bit ASCII lower-case characters and no spaces or dots, and be
+ formatted as a valid DNS domain name. Otherwise, the hostname is not sent even if this option
+ is true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>Hostname=</varname></term>
+ <listitem>
+ <para>Use this value for the hostname which is sent to the DHCPv6 server, instead of machine's
+ hostname. Note that the specified hostname must consist only of 7-bit ASCII lower-case
+ characters and no spaces or dots, and be formatted as a valid DNS domain name.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<listitem>
<para>When true (the default), the IP addresses provided by the DHCPv6 server will be
assigned.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<term><varname>UseCaptivePortal=</varname></term>
<listitem>
<para>When true (the default), the captive portal advertised by the DHCPv6 server will be recorded
- and made available to client programs and displayed in the networkctl status output per-link.</para>
+ and made available to client programs and displayed in the
+ <citerefentry><refentrytitle>networkctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+ status output per-link.</para>
+
+ <xi:include href="version-info.xml" xpointer="v254"/>
</listitem>
</varlistentry>
settings in the [DHCPPrefixDelegation] section, and
<ulink url="https://www.rfc-editor.org/rfc/rfc8415.html#section-6.3">RFC 8415</ulink>.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<term><varname>SendRelease=</varname></term>
<listitem>
<para>As in the [DHCPv4] section.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>NFTSet=</varname></term>
+ <listitem>
+ <para>This applies the NFT set for the network configuration received with DHCP, like
+ <varname>NFTSet=</varname> in [Address] section applies it to static configuration. See
+ <varname>NFTSet=</varname> in [Address] section for more details. For <literal>address</literal>
+ or <literal>prefix</literal> source types, the type of the element used in the NFT filter must be
+ <literal>ipv6_addr</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
section. Otherwise, defaults to <literal>no</literal>, and the DHCPv6 client will be started
when an RA is received. See also the <varname>DHCPv6Client=</varname> setting in the
[IPv6AcceptRA] section.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<varname>WithoutRA=solicit</varname> is implied if the setting is not explicitly specified.
When <literal>:auto</literal>, the first link which acquired prefixes to be delegated from
the DHCPv6 or DHCPv4 server is selected. Defaults to <literal>:auto</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<ulink url="https://tools.ietf.org/html/rfc4291#section-2.5.4">RFC 4291</ulink>, section
2.5.4), in which case the allowed value is hexadecimal, from 0 to 0x7fffffffffffffff
inclusive.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
is enabled, the delegated prefixes are distributed through the IPv6 Router Advertisement.
This setting will be ignored when the <varname>DHCPPrefixDelegation=</varname> setting is
enabled on the upstream interface. Defaults to yes.</para>
+
+ <xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
interface), the EUI-64 algorithm will be used by default to form an interface identifier from
the delegated prefixes. See also <varname>Token=</varname> setting below. Defaults to yes.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
delegated prefix. This accepts the same syntax as <varname>Token=</varname> in the
[IPv6AcceptRA] section. If <varname>Assign=</varname> is set to false, then this setting will
be ignored. Defaults to unset, which means the EUI-64 algorithm will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<term><varname>ManageTemporaryAddress=</varname></term>
<listitem>
<para>As in the [Address] section, but defaults to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<para>The metric of the route to the delegated prefix subnet. Takes an unsigned integer in
the range 0…4294967295. When set to 0, the kernel's default value is used. Defaults to 256.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
<para>This applies the NetLabel for the addresses received with DHCP, like
<varname>NetLabel=</varname> in [Address] section applies it to statically configured
addresses. See <varname>NetLabel=</varname> in [Address] section for more details.</para>
+
+ <xi:include href="version-info.xml" xpointer="v252"/>
</listitem>
</varlistentry>
- </variablelist>
- </refsect1>
- <refsect1>
- <title>[IPv6AcceptRA] Section Options</title>
+ <varlistentry>
+ <term><varname>NFTSet=</varname></term>
+ <listitem>
+ <para>This applies the NFT set for the network configuration received with DHCP, like
+ <varname>NFTSet=</varname> in [Address] section applies it to static configuration. See
+ <varname>NFTSet=</varname> in [Address] section for more details. For <literal>address</literal> or
+ <literal>prefix</literal> source types, the type of the element used in the NFT filter must be
+ <literal>ipv6_addr</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
+ </listitem>
+ </varlistentry>
+ </variablelist>
+ </refsect1>
+
+ <refsect1>
+ <title>[IPv6AcceptRA] Section Options</title>
<para>The [IPv6AcceptRA] section configures the IPv6 Router Advertisement (RA) client, if it is enabled
with the <varname>IPv6AcceptRA=</varname> setting described above:</para>
The EUI-64 algorithm will be used to generate an address for that prefix. Only
supported by Ethernet or InfiniBand interfaces.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
for that prefix. If an IPv6 address without mode is specified, then
<literal>static</literal> mode is assumed.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
will be changed, even if the prefix received in the RA message has not been
changed.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
</variablelist>
Token=static:::1a:2b:3c:4d
Token=prefixstable
Token=prefixstable:2002:da8:1::</programlisting></para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<para>This corresponds to the <option>nameserver</option> option in <citerefentry
project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
<para>When set to true, this setting corresponds to the <option>domain</option> option in <citerefentry
project='man-pages'><refentrytitle>resolv.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
<para>When used in combination with <varname>VRF=</varname>, the VRF's routing table is
used when this parameter is not specified.</para>
+
+ <xi:include href="version-info.xml" xpointer="v232"/>
</listitem>
</varlistentry>
preference, and the last is for low preference
(<literal><replaceable>high</replaceable>:<replaceable>medium</replaceable>:<replaceable>low</replaceable></literal>).
Defaults to <literal>512:1024:2048</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. When true, the TCP quick ACK mode is enabled for the routes configured by
the received RAs. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v253"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. When true, the MTU received in the Router Advertisement will be
used. Defaults to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. When true, the hop limit received in the Router Advertisement will be set to routes
configured based on the advertisement. See also <varname>IPv6HopLimit=</varname>. Defaults to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. When true, the ICMP6 rate limit received in the Router Advertisement will be set to ICMP6
rate limit based on the advertisement. Defaults to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<listitem>
<para>When true (the default), the router address will be configured as the default gateway.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<listitem>
<para>When true (the default), the routes corresponding to the route prefixes received in
the Router Advertisement will be configured.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<term><varname>UseCaptivePortal=</varname></term>
<listitem>
<para>When true (the default), the captive portal received in the Router Advertisement will be recorded
- and made available to client programs and displayed in the networkctl status output per-link.</para>
+ and made available to client programs and displayed in the
+ <citerefentry><refentrytitle>networkctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+ status output per-link.</para>
+
+ <xi:include href="version-info.xml" xpointer="v254"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>UsePREF64=</varname></term>
+ <listitem>
+ <para>When true, the IPv6 PREF64 (or NAT64) prefixes received in the Router Advertisement will be
+ recorded and made available to client programs and displayed in the
+ <citerefentry><refentrytitle>networkctl</refentrytitle><manvolnum>1</manvolnum></citerefentry>
+ status output per-link. See <ulink url="https://tools.ietf.org/html/rfc8781">RFC 8781</ulink>.
+ Defaults to false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<listitem>
<para>When true (the default), the autonomous prefix received in the Router Advertisement will be used and take
precedence over any statically configured ones.</para>
+
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<listitem>
<para>When true (the default), the onlink prefix received in the Router Advertisement will be
used and takes precedence over any statically configured ones.</para>
+
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<para>A whitespace-separated list of IPv6 router addresses. Each address can optionally
take a prefix length after <literal>/</literal>. Any information advertised by the listed
router is ignored.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
take a prefix length after <literal>/</literal>. Only information advertised by the listed
router is accepted. Note that if <varname>RouterAllowList=</varname> is configured then
<varname>RouterDenyList=</varname> is ignored.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<para>A whitespace-separated list of IPv6 prefixes. Each prefix can optionally take its
prefix length after <literal>/</literal>. IPv6 prefixes supplied via router advertisements
in the list are ignored.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
prefix length after <literal>/</literal>. IPv6 prefixes supplied via router advertisements
in the list are allowed. Note that if <varname>PrefixAllowList=</varname> is configured
then <varname>PrefixDenyList=</varname> is ignored.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<para>A whitespace-separated list of IPv6 route prefixes. Each prefix can optionally take
its prefix length after <literal>/</literal>. IPv6 route prefixes supplied via router
advertisements in the list are ignored.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
its prefix length after <literal>/</literal>. IPv6 route prefixes supplied via router
advertisements in the list are allowed. Note that if <varname>RouteAllowList=</varname> is
configured then <varname>RouteDenyList=</varname> is ignored.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<varname>WithoutRA=</varname> in the [DHCPv6] section is enabled, or
<varname>UplinkInterface=:self</varname> in the [DHCPPrefixDelegation] section is
specified. Defaults to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>This applies the NetLabel for the addresses received with RA, like
<varname>NetLabel=</varname> in [Address] section applies it to statically configured
addresses. See <varname>NetLabel=</varname> in [Address] section for more details.</para>
+
+ <xi:include href="version-info.xml" xpointer="v252"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>NFTSet=</varname></term>
+ <listitem>
+ <para>This applies the NFT set for the network configuration received with RA, like
+ <varname>NFTSet=</varname> in [Address] section applies it to static configuration. See
+ <varname>NFTSet=</varname> in [Address] section for more details. For <literal>address</literal> or
+ <literal>prefix</literal> source types, the type of the element used in the NFT filter must be
+ <literal>ipv6_addr</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
</variablelist>
<varlistentry>
<term><varname>ServerAddress=</varname></term>
- <listitem><para>Specifies server address for the DHCP server. Takes an IPv4 address with prefix
- length, for example 192.168.0.1/24. This setting may be useful when the link on
- which the DHCP server is running has multiple static addresses. When unset, one of static addresses
- in the link will be automatically selected. Defaults to unset.</para></listitem>
+ <listitem>
+ <para>Specifies the server address for the DHCP server. Takes an IPv4 address with prefix length
+ separated with a slash, e.g. <literal>192.168.0.1/24</literal>. Defaults to unset, and one of
+ static IPv4 addresses configured in [Network] or [Address] section will be automatically selected.
+ This setting may be useful when the interface on which the DHCP server is running has multiple
+ static IPv4 addresses.</para>
+ <para>This implies <varname>Address=</varname> in [Network] or [Address] section with the same
+ address and prefix length. That is,
+ <programlisting>[Network]
+DHCPServer=yes
+Address=192.168.0.1/24
+Address=192.168.0.2/24
+[DHCPServer]
+ServerAddress=192.168.0.1/24</programlisting>
+ or
+ <programlisting>[Network]
+DHCPServer=yes
+[Address]
+Address=192.168.0.1/24
+[Address]
+Address=192.168.0.2/24
+[DHCPServer]
+ServerAddress=192.168.0.1/24</programlisting>
+ are equivalent to the following.
+ <programlisting>[Network]
+DHCPServer=yes
+Address=192.168.0.2/24
+[DHCPServer]
+ServerAddress=192.168.0.1/24</programlisting>
+ </para>
+ <para>Since version 255, like the <varname>Address=</varname> setting in [Network] or [Address]
+ section, this also supports a null address, e.g. <literal>0.0.0.0/24</literal>, and an unused
+ address will be automatically selected. For more details about the automatic address selection,
+ see <varname>Address=</varname> setting in [Network] section in the above.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
+ </listitem>
</varlistentry>
<varlistentry>
the first address after the subnet address and takes up the rest of
the subnet, excluding the broadcast address. If the pool includes
the server address (the default), this is reserved and not handed
- out to clients.</para></listitem>
+ out to clients.</para>
+
+ <xi:include href="version-info.xml" xpointer="v226"/></listitem>
</varlistentry>
<varlistentry>
if the configuration data in DHCP leases changes frequently
and clients shall learn the new settings with shorter
latencies. Longer lease times reduce the generated DHCP
- network traffic.</para></listitem>
+ network traffic.</para>
+
+ <xi:include href="version-info.xml" xpointer="v226"/></listitem>
</varlistentry>
<varlistentry>
servers is enabled but no servers are specified, the servers configured in the uplink interface
will be emitted. When <literal>:auto</literal>, the link which has a default gateway with the
highest priority will be automatically selected. When <literal>:none</literal>, no uplink
- interface will be selected. Defaults to <literal>:auto</literal>.</para></listitem>
+ interface will be selected. Defaults to <literal>:auto</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
<varlistentry>
<varname>MaxLeaseTimeSec=</varname> described above.</para>
<para>This setting can be specified multiple times. If an empty string is specified, then all
- DNS servers specified earlier are cleared.</para></listitem>
+ DNS servers specified earlier are cleared.</para>
+
+ <xi:include href="version-info.xml" xpointer="v226"/></listitem>
</varlistentry>
<varlistentry>
<listitem><para>Similar to the <varname>EmitDNS=</varname> and <varname>DNS=</varname> settings
described above, these settings configure whether and what server information for the indicate
protocol shall be emitted as part of the DHCP lease. The same syntax, propagation semantics and
- defaults apply as for <varname>EmitDNS=</varname> and <varname>DNS=</varname>.</para></listitem>
+ defaults apply as for <varname>EmitDNS=</varname> and <varname>DNS=</varname>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v226"/></listitem>
</varlistentry>
<varlistentry>
the router option. When the <varname>EmitRouter=</varname> setting is disabled, the
<varname>Router=</varname> setting will be ignored. The <varname>EmitRouter=</varname> setting
defaults to true, and the <varname>Router=</varname> setting defaults to unset.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v230"/></listitem>
</varlistentry>
<varlistentry>
<literal>UTC</literal>) to pass to clients. If no explicit
timezone is set, the system timezone of the local host is
propagated, as determined by the
- <filename>/etc/localtime</filename> symlink.</para></listitem>
+ <filename>/etc/localtime</filename> symlink.</para>
+
+ <xi:include href="version-info.xml" xpointer="v226"/></listitem>
</varlistentry>
<varlistentry>
address is sent in the <option>siaddr</option> field of the DHCP message header. See <ulink
url="https://www.rfc-editor.org/rfc/rfc2131.html">RFC 2131</ulink> for more details. Defaults to
unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
</varlistentry>
<para>Note that typically setting one of <varname>BootServerName=</varname> or
<varname>BootServerAddress=</varname> is sufficient, but both can be set too, if desired.</para>
+
+ <xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
</varlistentry>
sent in the DHCP option 67 ("Bootfile name"). See <ulink
url="https://www.rfc-editor.org/rfc/rfc2132.html">RFC 2132</ulink> for more details. Defaults to
unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v251"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>IPv6OnlyPreferredSec=</varname></term>
+
+ <listitem>
+ <para>Takes a timespan. Controls the
+ <ulink url="https://tools.ietf.org/html/rfc8925">RFC 8925</ulink> IPv6-Only Preferred option.
+ Specifies the DHCPv4 option to indicate that a host supports an IPv6-only mode and is willing to
+ forgo obtaining an IPv4 address if the network provides IPv6 connectivity. Defaults to unset, and
+ not send the option. The minimum allowed value is 300 seconds.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<ulink url="https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
escapes</ulink>. This setting can be specified multiple times. If an empty string is specified,
then all options specified earlier are cleared. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<ulink url="https://en.wikipedia.org/wiki/Escape_sequences_in_C#Table_of_escape_sequences">C-style
escapes</ulink>. This setting can be specified multiple times. If an empty string is specified,
then all options specified earlier are cleared. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varlistentry>
to its network interface and all socket communication will be restricted to this interface.
Defaults to <literal>yes</literal>, except if <varname>RelayTarget=</varname> is used (see below),
in which case it defaults to <literal>no</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
<varlistentry>
<citerefentry project='man-pages'><refentrytitle>inet_pton</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
Turns this DHCP server into a DHCP relay agent. See <ulink url="https://tools.ietf.org/html/rfc1542">RFC 1542</ulink>.
The address is the address of DHCP server or another relay agent to forward DHCP messages to and from.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
<varlistentry>
where <literal><replaceable>value</replaceable></literal> should be replaced with the value of the suboption.
Defaults to unset (means no Agent Circuit ID suboption is generated).
Ignored if <varname>RelayTarget=</varname> is not specified.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
<varlistentry>
where <literal><replaceable>value</replaceable></literal> should be replaced with the value of the suboption.
Defaults to unset (means no Agent Remote ID suboption is generated).
Ignored if <varname>RelayTarget=</varname> is not specified.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>RapidCommit=</varname></term>
+ <listitem>
+ <para>Takes a boolean. When true, the server supports
+ <ulink url="https://datatracker.ietf.org/doc/html/rfc4039">RFC 4039</ulink>. When a client sends
+ a DHCPDISCOVER message with the Rapid Commit option to the server, then the server will reply with
+ a DHCPACK message to the client, instead of DHCPOFFER. Defaults to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>MACAddress=</varname></term>
- <listitem><para>The hardware address of a device to match. This key is mandatory.</para></listitem>
+ <listitem><para>The hardware address of a device to match. This key is mandatory.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>Address=</varname></term>
<listitem><para>The IPv4 address that should be assigned to the device that was matched with
- <varname>MACAddress=</varname>. This key is mandatory.</para></listitem>
+ <varname>MACAddress=</varname>. This key is mandatory.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
<varname>OtherInformation=</varname> is set to
<literal>true</literal>. Both settings default to
<literal>false</literal>, which means that a DHCPv6 server is not being
- used.</para></listitem>
+ used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
<listitem><para>Takes a timespan. Configures the IPv6 router lifetime in seconds. The value must be 0
seconds, or between 4 seconds and 9000 seconds. When set to 0, the host is not acting as a router.
Defaults to 1800 seconds (30 minutes).</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/>
</listitem>
</varlistentry>
<listitem><para>Takes a timespan. Configures the retransmit time, used by clients to retransmit Neighbor
Solicitation messages on address resolution and the Neighbor Unreachability Detection algorithm.
An integer the default unit of seconds, in the range 0…4294967295 msec. Defaults to 0.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
<literal>default</literal> added as synonyms for
<literal>medium</literal> just to make configuration easier. See
<ulink url="https://tools.ietf.org/html/rfc4191">RFC 4191</ulink>
- for details. Defaults to <literal>medium</literal>.</para></listitem>
+ for details. Defaults to <literal>medium</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Configures hop limit. Takes an integer in the range 0…255. See also
<varname>IPv6HopLimit=</varname>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
</listitem>
</varlistentry>
setting in the [DHCPPrefixDelegation] section will be used if
<varname>DHCPPrefixDelegation=</varname> is enabled, otherwise the link which has a default
gateway with the highest priority will be automatically selected. When <literal>:none</literal>,
- no uplink interface will be selected. Defaults to <literal>:auto</literal>.</para></listitem>
+ no uplink interface will be selected. Defaults to <literal>:auto</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
read from the [Network] section. If the [Network] section does not contain any DNS servers
either, DNS servers from the uplink interface specified in <varname>UplinkInterface=</varname>
will be used. When <varname>EmitDNS=</varname> is false, no DNS server information is sent in
- Router Advertisement messages. <varname>EmitDNS=</varname> defaults to true.</para></listitem>
+ Router Advertisement messages. <varname>EmitDNS=</varname> defaults to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
search domains either, DNS search domains from the uplink interface specified in
<varname>UplinkInterface=</varname> will be used. When <varname>EmitDomains=</varname> is false,
no DNS search domain information is sent in Router Advertisement messages.
- <varname>EmitDomains=</varname> defaults to true.</para></listitem>
+ <varname>EmitDomains=</varname> defaults to true.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
<listitem><para>Lifetime in seconds for the DNS server addresses listed in
<varname>DNS=</varname> and search domains listed in <varname>Domains=</varname>. Defaults to
- 3600 seconds (one hour).</para></listitem>
+ 3600 seconds (one hour).</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/></listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>HomeAgent=</varname></term>
+
+ <listitem><para>Takes a boolean. Specifies that IPv6 router advertisements which indicates to hosts that
+ the router acts as a Home Agent and includes a Home Agent Option. Defaults to false. See
+ <ulink url="https://tools.ietf.org/html/rfc6275">RFC 6275</ulink> for further details.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>HomeAgentLifetimeSec=</varname></term>
+
+ <listitem><para>Takes a timespan. Specifies the lifetime of the Home Agent. An integer the default unit of seconds,
+ in the range 1…65535. Defaults to the value set to <varname>RouterLifetimeSec=</varname>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><varname>HomeAgentPreference=</varname></term>
+
+ <listitem><para>Configures IPv6 Home Agent preference. Takes an integer in the range 0…65535.
+ Defaults to 0.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/>
+ </listitem>
</varlistentry>
</variablelist>
autoconfigured with this prefix and whether the prefix can be used for
onlink determination. Both settings default to <literal>true</literal>
in order to ease configuration.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
IPv6 addresses, the setting is configured as an IPv6 prefix and its prefix length, separated by a
<literal>/</literal> character. Use multiple [IPv6Prefix] sections to configure multiple IPv6
prefixes since prefix lifetimes, address autoconfiguration and onlink status may differ from one
- prefix to another.</para></listitem>
+ prefix to another.</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
<listitem><para>Preferred and valid lifetimes for the prefix measured in seconds.
<varname>PreferredLifetimeSec=</varname> defaults to 1800 seconds (30 minutes) and
- <varname>ValidLifetimeSec=</varname> defaults to 3600 seconds (one hour).</para></listitem>
+ <varname>ValidLifetimeSec=</varname> defaults to 3600 seconds (one hour).</para>
+
+ <xi:include href="version-info.xml" xpointer="v235"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>Assign=</varname></term>
<listitem><para>Takes a boolean. When true, adds an address from the prefix. Default to false.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
<varlistentry>
prefix. This accepts the same syntax as <varname>Token=</varname> in the [IPv6AcceptRA]
section. If <varname>Assign=</varname> is set to false, then this setting will be ignored.
Defaults to unset, which means the EUI-64 algorithm will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<para>The metric of the prefix route. Takes an unsigned integer in the range 0…4294967295.
When unset or set to 0, the kernel's default value is used. This setting is ignored when
<varname>Assign=</varname> is false.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
</variablelist>
<listitem><para>The IPv6 route that is to be distributed to hosts. Similarly to configuring static
IPv6 routes, the setting is configured as an IPv6 prefix routes and its prefix route length,
separated by a <literal>/</literal> character. Use multiple [IPv6RoutePrefix] sections to configure
- multiple IPv6 prefix routes.</para></listitem>
+ multiple IPv6 prefix routes.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/></listitem>
</varlistentry>
<varlistentry>
<term><varname>LifetimeSec=</varname></term>
<listitem><para>Lifetime for the route prefix measured in seconds.
- <varname>LifetimeSec=</varname> defaults to 3600 seconds (one hour).</para></listitem>
+ <varname>LifetimeSec=</varname> defaults to 3600 seconds (one hour).</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/></listitem>
</varlistentry>
</variablelist>
an IPv6 prefix that should be set up for NAT64 translation (PLAT) to allow 464XLAT on the network segment.
Use multiple [IPv6PREF64Prefix] sections to configure multiple IPv6 prefixes since prefix lifetime may differ
from one prefix to another. The prefix is an address with a prefix length, separated by a slash
- <literal>/</literal> character. Valid NAT64 prefix length are 96, 64, 56, 48, 40, and 32 bits.</para></listitem></varlistentry>
+ <literal>/</literal> character. Valid NAT64 prefix length are 96, 64, 56, 48, 40, and 32 bits.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/></listitem></varlistentry>
<varlistentry>
<term><varname>LifetimeSec=</varname></term>
<listitem><para>Lifetime for the prefix measured in seconds. Should be greater than or equal to <varname>RouterLifetimeSec=</varname>.
- <varname>LifetimeSec=</varname> defaults to 1800 seconds.</para></listitem>
+ <varname>LifetimeSec=</varname> defaults to 1800 seconds.</para>
+
+ <xi:include href="version-info.xml" xpointer="v255"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
traffic for which an FDB entry is missing and the destination
is unknown through this port. When unset, the kernel's default will be used.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v223"/>
</listitem>
</varlistentry>
<varlistentry>
traffic for which an MDB entry is missing and the destination
is unknown through this port. When unset, the kernel's default will be used.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<varlistentry>
the bridge. Which means unicast copies are only delivered to hosts which are interested in it.
When unset, the kernel's default will be used.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v240"/>
</listitem>
</varlistentry>
<varlistentry>
<para>Takes a boolean. Configures whether ARP and ND neighbor suppression is enabled for
this port. When unset, the kernel's default will be used.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<varlistentry>
<para>Takes a boolean. Configures whether MAC address learning is enabled for
this port. When unset, the kernel's default will be used.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<varlistentry>
<para>Takes a boolean. Configures whether traffic may be sent back out of the port on which it
was received. When this flag is false, then the bridge will not forward traffic back out of the
receiving port. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v223"/>
</listitem>
</varlistentry>
<varlistentry>
isolated ports can only communicate with non-isolated ports. When set to true, this port can only
communicate with other ports whose Isolated setting is false. When set to false, this port
can communicate with any other ports. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v251"/>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Takes a boolean. Configures whether STP Bridge Protocol Data Units will be
processed by the bridge port. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v223"/>
</listitem>
</varlistentry>
<varlistentry>
<para>Takes a boolean. This flag allows the bridge to immediately stop multicast
traffic on a port that receives an IGMP Leave message. It is only used with
IGMP snooping if enabled on the bridge. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v223"/>
</listitem>
</varlistentry>
<varlistentry>
<para>Takes a boolean. Configures whether a given port is allowed to
become a root port. Only used when STP is enabled on the bridge.
When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v223"/>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Takes a boolean. Configures whether proxy ARP to be enabled on this port.
When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<varlistentry>
<para>Takes a boolean. Configures whether proxy ARP to be enabled on this port
which meets extended requirements by IEEE 802.11 and Hotspot 2.0 specifications.
When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<varlistentry>
the presence of routers, <literal>permanent</literal> to permanently enable multicast traffic
forwarding on this port, or <literal>temporary</literal> to enable multicast routers temporarily
on this port, not depending on incoming queries. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<varlistentry>
is used to decide which link to use. Faster interfaces
should have lower costs. It is an integer value between 1 and
65535.</para>
+
+ <xi:include href="version-info.xml" xpointer="v218"/>
</listitem>
</varlistentry>
<varlistentry>
to decide which link to use. Lower value means higher priority.
It is an integer value between 0 to 63. Networkd does not set any
default, meaning the kernel default value of 32 is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v234"/>
</listitem>
</varlistentry>
</variablelist>
<term><varname>MACAddress=</varname></term>
<listitem>
<para>As in the [Network] section. This key is mandatory.</para>
+
+ <xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>Destination=</varname></term>
<listitem>
<para>Takes an IP address of the destination VXLAN tunnel endpoint.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<varlistentry>
<para>The VLAN ID for the new static MAC table entry. If
omitted, no VLAN ID information is appended to the new static MAC
table entry.</para>
+
+ <xi:include href="version-info.xml" xpointer="v219"/>
</listitem>
</varlistentry>
<varlistentry>
<para>The VXLAN Network Identifier (or VXLAN Segment ID) to use to connect to
the remote VXLAN tunnel endpoint. Takes a number in the range 1…16777215.
Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<varlistentry>
means the address is associated with master devices fdb. <literal>router</literal> means
the destination address is associated with a router. Note that it's valid if the referenced
device is a VXLAN type device and has route shortcircuit enabled. Defaults to <literal>self</literal>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v243"/>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Specifies the name or index of the outgoing interface for the VXLAN device driver to
reach the remote VXLAN tunnel endpoint. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v249"/>
</listitem>
</varlistentry>
</variablelist>
<term><varname>MulticastGroupAddress=</varname></term>
<listitem>
<para>Specifies the IPv4 or IPv6 multicast group address to add. This setting is mandatory.</para>
+
+ <xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>VLANId=</varname></term>
<listitem>
<para>The VLAN ID for the new entry. Valid ranges are 0 (no VLAN) to 4094. Optional, defaults to 0.</para>
+
+ <xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
</variablelist>
<para>The MUD URLs received via LLDP packets are saved and can be read using the
<function>sd_lldp_neighbor_get_mud_url()</function> function.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>The bitrate of CAN device in bits per second. The usual SI prefixes (K, M) with the base of 1000 can
be used here. Takes a number in the range 1…4294967295.</para>
+
+ <xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
<varlistentry>
<para>Optional sample point in percent with one decimal (e.g. <literal>75%</literal>,
<literal>87.5%</literal>) or permille (e.g. <literal>875‰</literal>). This will be ignored when
<varname>BitRate=</varname> is unspecified.</para>
+
+ <xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
<varlistentry>
integer in the range 0…4294967295. These settings except for
<varname>SyncJumpWidth=</varname> will be ignored when <varname>BitRate=</varname> is
specified.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>The bitrate and sample point for the data phase, if CAN-FD is used. These settings are
analogous to the <varname>BitRate=</varname> and <varname>SamplePoint=</varname> keys.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varlistentry>
<para>Specifies the time quanta, propagation segment, phase buffer segment 1 and 2, and the
synchronization jump width for the data phase, if CAN-FD is used. These settings are
analogous to the <varname>TimeQuantaNSec=</varname> or related settings.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
Note, that a bitrate and optional sample point should also be set for the CAN-FD data phase using
the <varname>DataBitRate=</varname> and <varname>DataSamplePoint=</varname> keys, or
<varname>DataTimeQuanta=</varname> and related settings.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Takes a boolean. When <literal>yes</literal>, non-ISO CAN-FD mode is enabled for the
interface. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varlistentry>
be specified using decimals (e.g. <literal>0.1s</literal>) or a <literal>ms</literal> or
<literal>us</literal> postfix. Using <literal>infinity</literal> or <literal>0</literal> will turn the
automatic restart off. By default automatic restart is disabled.</para>
+
+ <xi:include href="version-info.xml" xpointer="v239"/>
</listitem>
</varlistentry>
<varlistentry>
<literal>yes</literal>, the termination resistor is set to 120 ohm. When
<literal>no</literal> or <literal>0</literal> is set, the termination resistor is disabled.
When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Takes a boolean. When <literal>yes</literal>, three samples (instead of one) are used to determine
the value of a received bit by majority rule. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v242"/>
</listitem>
</varlistentry>
<varlistentry>
unable to send recessive bit, bus overload, active error announcement, error occurred on
transmission). When unset, the kernel's default will be used. Note: in case of a CAN bus with a
single CAN device, sending a CAN frame may result in a huge number of CAN bus errors.</para>
+
+ <xi:include href="version-info.xml" xpointer="v248"/>
</listitem>
</varlistentry>
<varlistentry>
bit. Listen-only mode is important to debug CAN networks without interfering with the
communication or acknowledge the CAN frame. When unset, the kernel's default will be used.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<varlistentry>
loopback mode is enabled, the interface treats messages transmitted by itself as received
messages. The loopback mode is important to debug CAN networks. When unset, the kernel's
default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Takes a boolean. When <literal>yes</literal>, one-shot mode is enabled. When unset,
the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Takes a boolean. When <literal>yes</literal>, the interface will ignore missing CAN
ACKs. When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varlistentry>
<listitem>
<para>Takes a boolean. When <literal>yes</literal>, the interface will handle the 4bit data
length code (DLC). When unset, the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>Specifies the parent Queueing Discipline (qdisc). Takes one of <literal>clsact</literal>
or <literal>ingress</literal>. This is mandatory.</para>
+
+ <xi:include href="version-info.xml" xpointer="v244"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the fixed amount of delay to be added to all packets going out of the
interface. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the chosen delay to be added to the packets outgoing to the network
interface. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the maximum number of packets the qdisc may hold queued at a time.
An unsigned integer in the range 0…4294967294. Defaults to 1000.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies an independent loss probability to be added to the packets outgoing from the
network interface. Takes a percentage value, suffixed with "%". Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies that the chosen percent of packets is duplicated before queuing them.
Takes a percentage value, suffixed with "%". Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>Specifies the latency parameter, which specifies the maximum amount of time a
packet can sit in the Token Bucket Filter (TBF). Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>Takes the number of bytes that can be queued waiting for tokens to become available.
When the size is suffixed with K, M, or G, it is parsed as Kilobytes, Megabytes, or Gigabytes,
respectively, to the base of 1024. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
can be available for instantaneous transfer. When the size is suffixed with K, M, or G, it is
parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of 1024. Defaults to
unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Specifies the device specific bandwidth. When suffixed with K, M, or G, the specified
bandwidth is parsed as Kilobits, Megabits, or Gigabits, respectively, to the base of 1000.
Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>The Minimum Packet Unit (MPU) determines the minimal token usage (specified in bytes)
for a packet. When suffixed with K, M, or G, the specified size is parsed as Kilobytes,
Megabytes, or Gigabytes, respectively, to the base of 1024. Defaults to zero.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>Takes the maximum depletion rate of the bucket. When suffixed with K, M, or G, the
specified size is parsed as Kilobits, Megabits, or Gigabits, respectively, to the base of
1000. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>Specifies the size of the peakrate bucket. When suffixed with K, M, or G, the specified
size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of 1024.
Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
</variablelist>
<para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
incoming packets are dropped. An unsigned integer in the range 1…4294967294. Defaults to unset and
kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
incoming packets are dropped. An unsigned integer ranges 1 to 4294967294. Defaults to unset and
kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v247"/>
</listitem>
</varlistentry>
</variablelist>
<para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
incoming packets are dropped. An unsigned integer in the range 0…4294967294. Defaults to unset and
kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<term><varname>PerturbPeriodSec=</varname></term>
<listitem>
<para>Specifies the interval in seconds for queue algorithm perturbation. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
</variablelist>
reached, incoming packets are dropped. When suffixed with K, M, or G, the specified size is parsed
as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of 1024. Defaults to unset and
kernel default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
overflow in case the kernel is unable to dequeue packets as quickly as it receives them. When this
limit is reached, incoming packets are dropped. An unsigned integer in the range
0…4294967294. Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<varlistentry>
<term><varname>PacketLimit=</varname></term>
<listitem>
- <para>As in [PFIFO] section.</para></listitem>
+ <para>As in [PFIFO] section.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/></listitem>
</varlistentry>
</variablelist>
</refsect1>
<para>Specifies the shaper bandwidth. When suffixed with K, M, or G, the specified size is
parsed as Kilobits, Megabits, or Gigabits, respectively, to the base of 1000. Defaults to
unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
at this qdisc. This is most likely to be useful with cellular links, which tend to change
quality randomly. If this setting is enabled, the <varname>Bandwidth=</varname> setting is
used as an initial estimate. Defaults to unset, and the kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<para>Specifies that bytes to be addeded to the size of each packet. Bytes may be negative.
Takes an integer in the range -64…256. Defaults to unset and kernel's default is used.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>Rounds each packet (including overhead) up to the specified bytes. Takes an integer in
the range 1…256. Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
ATM cell framing, which is normally found on ADSL links. When <literal>ptm</literal>, enables
the compensation for PTM encoding, which is normally found on VDSL2 links and uses a 64b/65b
encoding scheme. Defaults to unset and the kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<para>Takes a boolean value. When true, the packet size reported by the Linux kernel will be
used, instead of the underlying IP packet size. Defaults to unset, and the kernel's default
is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<term><option>none</option></term>
<listitem><para>
The flow isolation is disabled, and all traffic passes through a single queue.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>src-host</option></term>
Flows are defined only by source address. Equivalent to the <literal>srchost</literal>
option for <command>tc qdisc</command> command. See also
<citerefentry project='man-pages'><refentrytitle>tc-cake</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>dst-host</option></term>
Flows are defined only by destination address. Equivalent to the
<literal>dsthost</literal> option for <command>tc qdisc</command> command. See also
<citerefentry project='man-pages'><refentrytitle>tc-cake</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>hosts</option></term>
Flows are defined by source-destination host pairs. Equivalent to the same option for
<command>tc qdisc</command> command. See also
<citerefentry project='man-pages'><refentrytitle>tc-cake</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>flows</option></term>
transport protocol, source port and destination port. Equivalent to the same option for
<command>tc qdisc</command> command. See also
<citerefentry project='man-pages'><refentrytitle>tc-cake</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>dual-src-host</option></term>
to the <literal>dual-srchost</literal> option for <command>tc qdisc</command> command.
See also
<citerefentry project='man-pages'><refentrytitle>tc-cake</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>dual-dst-host</option></term>
Equivalent to the <literal>dual-dsthost</literal> option for
<command>tc qdisc</command> command. See also
<citerefentry project='man-pages'><refentrytitle>tc-cake</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>triple</option></term>
Equivalent to the <literal>triple-isolate</literal> option for
<command>tc qdisc</command> command. See also
<citerefentry project='man-pages'><refentrytitle>tc-cake</refentrytitle><manvolnum>8</manvolnum></citerefentry>.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
</variablelist>
<para>Defaults to unset and the kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<varname>FlowIsolationMode=</varname> is <literal>none</literal> or <literal>flows</literal>,
or if NAT is performed on a different host. Defaults to unset, and the kernel's default is
used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<term><option>besteffort</option></term>
<listitem><para>
Disables priority queueing by placing all traffic in one tin.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>precedence</option></term>
Enables priority queueing based on the legacy interpretation of TOS
<literal>Precedence</literal> field. Use of this preset on the modern Internet is
firmly discouraged.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>diffserv8</option></term>
(<literal>DiffServ</literal>) field with eight tins: Background Traffic, High
Throughput, Best Effort, Video Streaming, Low Latency Transactions, Interactive Shell,
Minimum Latency, and Network Control.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>diffserv4</option></term>
Enables priority queueing based on the Differentiated Service
(<literal>DiffServ</literal>) field with four tins: Background Traffic, Best Effort,
Streaming Media, and Latency Sensitive.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
<varlistentry>
<term><option>diffserv3</option></term>
Enables priority queueing based on the Differentiated Service
(<literal>DiffServ</literal>) field with three tins: Background Traffic, Best Effort,
and Latency Sensitive.
- </para></listitem>
+ </para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/></listitem>
</varlistentry>
</variablelist>
<para>Defaults to unset, and the kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<para>Takes an integer in the range 1…4294967295. When specified, firewall-mark-based
overriding of CAKE's tin selection is enabled. Defaults to unset, and the kernel's default is
used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean value. When true, CAKE clears the DSCP fields, except for ECN bits, of
any packet passing through CAKE. Defaults to unset, and the kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
<para>Takes a boolean value. When true, CAKE will split General Segmentation Offload (GSO)
super-packets into their on-the-wire components and dequeue them individually. Defaults to
unset, and the kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v250"/>
</listitem>
</varlistentry>
extremely high-performance 10GigE+ networks like datacentre, 1ms for non-WiFi LAN connections,
100ms for typical internet connections. Defaults to unset, and the kernel's default will be used.
</para>
+
+ <xi:include href="version-info.xml" xpointer="v253"/>
</listitem>
</varlistentry>
keep at least two redundant ACKs in the queue, while in <literal>aggressive</literal> mode, it will
filter down to a single ACK. This may improve download throughput on links with very asymmetrical
rate limits. Defaults to unset, and the kernel's default will be used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v253"/>
</listitem>
</varlistentry>
<para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
incoming packets are dropped. An unsigned integer in the range 0…4294967294. Defaults to unset and
kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a timespan. Specifies the acceptable minimum standing/persistent queue delay.
Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a timespan. This is used to ensure that the measured minimum delay does not
become too stale. Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. This can be used to mark packets instead of dropping them. Defaults to
unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a timespan. This sets a threshold above which all packets are marked with ECN
Congestion Experienced (CE). Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
</variablelist>
to the next class. When suffixed with K, M, or G, the specified size is parsed as Kilobytes,
Megabytes, or Gigabytes, respectively, to the base of 1024. Defaults to the MTU of the
interface.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Specifies the number of bands. An unsigned integer in the range 1…16. This value has to be at
least large enough to cover the strict bands specified through the <varname>StrictBands=</varname>
and bandwidth-sharing bands specified in <varname>QuantumBytes=</varname>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the number of bands that should be created in strict mode. An unsigned integer in
the range 1…16.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
suffixed with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes,
respectively, to the base of 1024. This setting can be specified multiple times. If an empty
string is assigned, then the all previous assignments are cleared.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
there are fewer, the default band that traffic with one of the unmentioned priorities goes to is
the last one. Each band number must be in the range 0…255. This setting can be specified multiple
times. If an empty string is assigned, then the all previous assignments are cleared.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>Specifies the number of virtual queues. Takes an integer in the range 1…16. Defaults to unset
and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the number of default virtual queue. This must be less than <varname>VirtualQueue=</varname>.
Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. It turns on the RIO-like buffering scheme. Defaults to
unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>Specifies the hard limit on the real queue size. When this limit is reached, incoming packets are
dropped. Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>Specifies the limit on the total number of bytes that can be queued in this FQ-CoDel instance.
When suffixed with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes,
respectively, to the base of 1024. Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the number of flows into which the incoming packets are classified.
Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a timespan. Specifies the acceptable minimum standing/persistent queue delay.
Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a timespan. This is used to ensure that the measured minimum delay does not
become too stale. Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>Specifies the number of bytes used as the "deficit" in the fair queuing algorithm timespan.
When suffixed with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes,
respectively, to the base of 1024. Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean. This can be used to mark packets instead of dropping them. Defaults to
unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a timespan. This sets a threshold above which all packets are marked with ECN
Congestion Experienced (CE). Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>Specifies the hard limit on the real queue size. When this limit is reached, incoming packets are
dropped. Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the hard limit on the maximum number of packets queued per flow. Defaults to
unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
to dequeue at once. When suffixed with K, M, or G, the specified size is parsed as Kilobytes,
Megabytes, or Gigabytes, respectively, to the base of 1024. Defaults to unset and kernel's
default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
allowed to dequeue initially. When suffixed with K, M, or G, the specified size is parsed as
Kilobytes, Megabytes, or Gigabytes, respectively, to the base of 1024. Defaults to unset and
kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>Specifies the maximum sending rate of a flow. When suffixed with K, M, or G, the
specified size is parsed as Kilobits, Megabits, or Gigabits, respectively, to the base of
1000. Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the size of the hash table used for flow lookups. Defaults to unset and
kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<para>Takes an unsigned integer. For packets not owned by a socket, fq is able to mask a part
of hash and reduce number of buckets associated with the traffic. Defaults to unset and
kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a boolean, and enables or disables flow pacing. Defaults to unset and kernel's
default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes a timespan. This sets a threshold above which all packets are marked with ECN
Congestion Experienced (CE). Defaults to unset and kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
</variablelist>
Note that when teql is used, currently, the module <constant>sch_teql</constant> with
<constant>max_equalizers=N+1</constant> option must be loaded before
<command>systemd-networkd</command> is started.</para>
+
+ <xi:include href="version-info.xml" xpointer="v245"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>Takes the minor id in hexadecimal of the default class. Unclassified traffic gets sent
to the class. Defaults to unset.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>Takes an unsigned integer. The DRR quantums are calculated by dividing the value
configured in <varname>Rate=</varname> by <varname>RateToQuantum=</varname>.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>Specifies the priority of the class. In the round-robin process, classes with the lowest
priority field are tried for packets first.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Specifies how many bytes to serve from leaf at once. When suffixed with K, M, or G, the
specified size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of
1024.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<listitem>
<para>Specifies the maximum packet size we create. When suffixed with K, M, or G, the specified
size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of 1024.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Takes an unsigned integer which specifies per-packet size overhead used in rate
computations. When suffixed with K, M, or G, the specified size is parsed as Kilobytes,
Megabytes, or Gigabytes, respectively, to the base of 1024.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Specifies the maximum rate this class and all its children are guaranteed. When suffixed
with K, M, or G, the specified size is parsed as Kilobits, Megabits, or Gigabits, respectively,
to the base of 1000. This setting is mandatory.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
When suffixed with K, M, or G, the specified size is parsed as Kilobits, Megabits, or Gigabits,
respectively, to the base of 1000. When unset, the value specified with <varname>Rate=</varname>
is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Specifies the maximum bytes burst which can be accumulated during idle period. When suffixed
with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively,
to the base of 1024.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Specifies the maximum bytes burst for ceil which can be accumulated during idle period.
When suffixed with K, M, or G, the specified size is parsed as Kilobytes, Megabytes, or Gigabytes,
respectively, to the base of 1024.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<para>Specifies the hard limit on the queue size in number of packets. When this limit is reached,
incoming packets are dropped. An unsigned integer in the range 0…4294967294. Defaults to unset and
kernel's default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>Specifies the weight of the class. Takes an integer in the range 1…1023. Defaults to
unset in which case the kernel default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
<para>Specifies the maximum packet size in bytes for the class. When suffixed with K, M, or G, the
specified size is parsed as Kilobytes, Megabytes, or Gigabytes, respectively, to the base of
1024. When unset, the kernel default is used.</para>
+
+ <xi:include href="version-info.xml" xpointer="v246"/>
</listitem>
</varlistentry>
</variablelist>
<listitem>
<para>The VLAN ID allowed on the port. This can be either a single ID or a range M-N. Takes
an integer in the range 1…4094.</para>
+
+ <xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
<varlistentry>
<para>The VLAN ID specified here will be used to untag frames on egress. Configuring
<varname>EgressUntagged=</varname> implicates the use of <varname>VLAN=</varname> above and will enable the
VLAN ID for ingress as well. This can be either a single ID or a range M-N.</para>
+
+ <xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
<varlistentry>
<para>The Port VLAN ID specified here is assigned to all untagged frames at ingress.
<varname>PVID=</varname> can be used only once. Configuring <varname>PVID=</varname> implicates the use of
<varname>VLAN=</varname> above and will enable the VLAN ID for ingress as well.</para>
+
+ <xi:include href="version-info.xml" xpointer="v231"/>
</listitem>
</varlistentry>
</variablelist>
projects / thirdparty / systemd.git / blobdiff