shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-12-23 21:35:11 +03:00
Code
778abdbfa1
systemd/man/networkd.conf.xml

338 lines
16 KiB
XML
Raw Normal View History

man: drop mode line in file headers This is already included in .dir-locals, so we don't need it in the files themselves.
2018-07-03 00:15:39 +03:00
<?xml version='1.0'?>
man: use same header for all files The "include" files had type "book" for some raeason. I don't think this is meaningful. Let's just use the same everywhere. $ perl -i -0pe 's^..DOCTYPE (book|refentry) PUBLIC "-//OASIS//DTD DocBook XML V4.[25]//EN"\s+"http^<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"\n "http^gms' man/*.xml
2019-03-14 16:40:58 +03:00
<!DOCTYPE refentry PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
man: use same version in public and system ident.
2023-12-25 17:48:33 +03:00
"http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
<!--
license: LGPL-2.1+ -> LGPL-2.1-or-later
2020-11-09 07:23:58 +03:00
SPDX-License-Identifier: LGPL-2.1-or-later
Add SPDX license identifiers to man pages
2017-11-18 19:22:32 +03:00
tree-wide: beautify remaining copyright statements Let's unify an beautify our remaining copyright statements, with a unicode ©. This means our copyright statements are now always formatted the same way. Yay.
2018-06-12 20:00:24 +03:00
Copyright © 2014 Vinay Kulkarni
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
-->
<refentry id="networkd.conf" conditional='ENABLE_NETWORKD'
xmlns:xi="http://www.w3.org/2001/XInclude">
<refentryinfo>
<title>networkd.conf</title>
<productname>systemd</productname>
</refentryinfo>
<refmeta>
<refentrytitle>networkd.conf</refentrytitle>
<manvolnum>5</manvolnum>
</refmeta>
<refnamediv>
<refname>networkd.conf</refname>
<refname>networkd.conf.d</refname>
<refpurpose>Global Network configuration files</refpurpose>
</refnamediv>
<refsynopsisdiv>
man: use <simplelist> for file lists in synopsis With <para><filename>…</filename></para>, we get a separate "paragraph" for each line, i.e. entries separated by empty lines. This uses up a lot of space and was only done because docbook makes it hard to insert a newline. In some other places, <literallayout> was used, but then we cannot indent the source text (because the whitespace would end up in the final page). We can get the desired result with <simplelist>. With <simplelist> the items are indented in roff output, but not in html output. In some places this looks better then no indentation, and in others it would probably be better to have no indent. But this is a minor issue and we cannot control that. (I didn't convert all spots. There's a bunch of other man pages which have two lines, e.g. an executable and service file, and it doesn't matter there so much.)
2023-12-14 14:52:03 +03:00
<para><simplelist>
<member><filename>/etc/systemd/networkd.conf</filename></member>
man: document all the new paths
2024-02-22 12:58:48 +03:00
<member><filename>/run/systemd/networkd.conf</filename></member>
<member><filename>/usr/lib/systemd/networkd.conf</filename></member>
man: use <simplelist> for file lists in synopsis With <para><filename>…</filename></para>, we get a separate "paragraph" for each line, i.e. entries separated by empty lines. This uses up a lot of space and was only done because docbook makes it hard to insert a newline. In some other places, <literallayout> was used, but then we cannot indent the source text (because the whitespace would end up in the final page). We can get the desired result with <simplelist>. With <simplelist> the items are indented in roff output, but not in html output. In some places this looks better then no indentation, and in others it would probably be better to have no indent. But this is a minor issue and we cannot control that. (I didn't convert all spots. There's a bunch of other man pages which have two lines, e.g. an executable and service file, and it doesn't matter there so much.)
2023-12-14 14:52:03 +03:00
<member><filename>/etc/systemd/networkd.conf.d/*.conf</filename></member>
man: add missing drop-in directory
2024-04-16 05:50:38 +03:00
<member><filename>/run/systemd/networkd.conf.d/*.conf</filename></member>
man: use <simplelist> for file lists in synopsis With <para><filename>…</filename></para>, we get a separate "paragraph" for each line, i.e. entries separated by empty lines. This uses up a lot of space and was only done because docbook makes it hard to insert a newline. In some other places, <literallayout> was used, but then we cannot indent the source text (because the whitespace would end up in the final page). We can get the desired result with <simplelist>. With <simplelist> the items are indented in roff output, but not in html output. In some places this looks better then no indentation, and in others it would probably be better to have no indent. But this is a minor issue and we cannot control that. (I didn't convert all spots. There's a bunch of other man pages which have two lines, e.g. an executable and service file, and it doesn't matter there so much.)
2023-12-14 14:52:03 +03:00
<member><filename>/usr/lib/systemd/networkd.conf.d/*.conf</filename></member>
</simplelist></para>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
</refsynopsisdiv>
<refsect1>
<title>Description</title>
man/networkd.conf: remove strange comment Does anyone even read those pages‽
2024-01-25 23:31:30 +03:00
<para>These configuration files control global network parameters.</para>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
</refsect1>
<xi:include href="standard-conf.xml" xpointer="main-conf" />
man: add entry about SpeedMeter= Closes #14002.
2019-11-18 18:03:35 +03:00
<refsect1>
<title>[Network] Section Options</title>
tree-wide: drop quotes from around [section] For users, the square brackets already serve as markup and clearly delineate the section name from surrounding text. Putting additional markup around that only adds clutter. Also, we were very inconsistent in using the quotes. Let's just drop them altogether.
2020-07-06 12:00:06 +03:00
<para>The following options are available in the [Network] section:</para>
man: add entry about SpeedMeter= Closes #14002.
2019-11-18 18:03:35 +03:00
<variablelist class='network-directives'>
<varlistentry>
<term><varname>SpeedMeter=</varname></term>
<listitem><para>Takes a boolean. If set to yes, then <command>systemd-networkd</command>
measures the traffic of each interface, and
man: fix invalid tag place
2020-08-21 09:30:05 +03:00
<command>networkctl status <replaceable>INTERFACE</replaceable></command> shows the measured speed.
man: add version info This tries to add information about when each option was added. It goes back to version 183. The version info is included from a separate file to allow generating it, which would allow more control on the formatting of the final output.
2023-08-22 19:52:36 +03:00
Defaults to no.</para>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
man: add entry about SpeedMeter= Closes #14002.
2019-11-18 18:03:35 +03:00
</varlistentry>
<varlistentry>
<term><varname>SpeedMeterIntervalSec=</varname></term>
<listitem><para>Specifies the time interval to calculate the traffic speed of each interface.
man: add version info This tries to add information about when each option was added. It goes back to version 183. The version info is included from a separate file to allow generating it, which would allow more control on the formatting of the final output.
2023-08-22 19:52:36 +03:00
If <varname>SpeedMeter=no</varname>, the value is ignored. Defaults to 10sec.</para>
<xi:include href="version-info.xml" xpointer="v244"/></listitem>
man: add entry about SpeedMeter= Closes #14002.
2019-11-18 18:03:35 +03:00
</varlistentry>
network: Add support to ignore foreign routes
2020-02-11 15:35:11 +03:00
network: introduce ManageForeignRoutingPolicyRules= boolean setting in networkd.conf The commit 0b81225e5791f660506f7db0ab88078cf296b771 makes that networkd remove all foreign rules except those with "proto kernel". But, in some situation, people may want to manage routing policy rules with other tools, e.g. 'ip' command. To support such the situation, this introduce ManageForeignRoutingPolicyRules= boolean setting. Closes #19106.
2021-04-11 15:33:51 +03:00
<varlistentry>
<term><varname>ManageForeignRoutingPolicyRules=</varname></term>
<listitem><para>A boolean. When true, <command>systemd-networkd</command> will remove rules
that are not configured in .network files (except for rules with protocol
<literal>kernel</literal>). When false, it will not remove any foreign rules, keeping them even
if they are not configured in a .network file. Defaults to yes.
man: add version info This tries to add information about when each option was added. It goes back to version 183. The version info is included from a separate file to allow generating it, which would allow more control on the formatting of the final output.
2023-08-22 19:52:36 +03:00
</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
network: introduce ManageForeignRoutingPolicyRules= boolean setting in networkd.conf The commit 0b81225e5791f660506f7db0ab88078cf296b771 makes that networkd remove all foreign rules except those with "proto kernel". But, in some situation, people may want to manage routing policy rules with other tools, e.g. 'ip' command. To support such the situation, this introduce ManageForeignRoutingPolicyRules= boolean setting. Closes #19106.
2021-04-11 15:33:51 +03:00
</varlistentry>
network: Add support to ignore foreign routes
2020-02-11 15:35:11 +03:00
<varlistentry>
<term><varname>ManageForeignRoutes=</varname></term>
man: update description for ManageForeignRoutes=
2021-04-13 06:23:31 +03:00
<listitem><para>A boolean. When true, <command>systemd-networkd</command> will remove routes
that are not configured in .network files (except for routes with protocol
<literal>kernel</literal>, <literal>dhcp</literal> when <varname>KeepConfiguration=</varname>
is true or <literal>dhcp</literal>, and <literal>static</literal> when
<varname>KeepConfiguration=</varname> is true or <literal>static</literal>). When false, it will
not remove any foreign routes, keeping them even if they are not configured in a .network file.
man: add version info This tries to add information about when each option was added. It goes back to version 183. The version info is included from a separate file to allow generating it, which would allow more control on the formatting of the final output.
2023-08-22 19:52:36 +03:00
Defaults to yes.</para>
<xi:include href="version-info.xml" xpointer="v246"/></listitem>
network: Add support to ignore foreign routes
2020-02-11 15:35:11 +03:00
</varlistentry>
network/nexthop: introduce ManageForeignNextHops= boolean setting Closes #29034.
2023-12-11 20:29:25 +03:00
<varlistentry>
<term><varname>ManageForeignNextHops=</varname></term>
<listitem><para>A boolean. When true, <command>systemd-networkd</command> will remove nexthops
that are not configured in .network files (except for routes with protocol
<literal>kernel</literal>). When false, it will
not remove any foreign nexthops, keeping them even if they are not configured in a .network file.
Defaults to yes.</para>
<xi:include href="version-info.xml" xpointer="v256"/></listitem>
</varlistentry>
network: add support to RoutingPolicyRule lookup table name
2021-01-19 14:58:53 +03:00
<varlistentry>
<term><varname>RouteTable=</varname></term>
network: make RouteTable= setting can take multiple name:number pairs in a line Follow-up for c038ce4606f93d9e58147f87703125270fb744e2.
2021-01-20 08:33:21 +03:00
<listitem><para>Defines the route table name. Takes a whitespace-separated list of the pairs of
route table name and number. The route table name and number in each pair are separated with a
colon, i.e., <literal><replaceable>name</replaceable>:<replaceable>number</replaceable></literal>.
The route table name must not be <literal>default</literal>, <literal>main</literal>, or
<literal>local</literal>, as these route table names are predefined with route table number 253,
network: refuse to override predefined route table name
2023-07-14 10:08:03 +03:00
254, and 255, respectively. The route table number must be an integer in the range 1…4294967295,
except for predefined numbers 253, 254, and 255. This setting can be specified multiple times.
If an empty string is specified, then the list specified earlier are cleared. Defaults to unset.
man: add version info This tries to add information about when each option was added. It goes back to version 183. The version info is included from a separate file to allow generating it, which would allow more control on the formatting of the final output.
2023-08-22 19:52:36 +03:00
</para>
<xi:include href="version-info.xml" xpointer="v248"/></listitem>
network: add support to RoutingPolicyRule lookup table name
2021-01-19 14:58:53 +03:00
</varlistentry>
network: introduce per-interface IP forwarding settings This deprecates IPForward= setting, which unconditionally controled the global setting, even though it is a setting in .network file. Instead, this introduces new IPv4Forwarding= and IPv6Forwarding= settings both in .network and networkd.conf. If these settings are specified in a .network file, then the per-interface forwarding setting will be configured. If specified in networkd.conf, then the global IP forwarding setting will be configured. Closes #30648.
2024-02-21 00:20:45 +03:00
<varlistentry>
<term><varname>IPv4Forwarding=</varname></term>
<listitem>
<para>Configures IPv4 packet forwarding for the system. Takes a boolean value. This controls the
<filename>net.ipv4.conf.default.forwarding</filename> and
<filename>net.ipv4.conf.all.forwarding</filename>sysctl options. See
<ulink url="https://docs.kernel.org/networking/ip-sysctl.html">IP Sysctl</ulink>
for more details about the sysctl options. Defaults to unset and the sysctl options will not be
changed.</para>
<xi:include href="version-info.xml" xpointer="v256"/>
</listitem>
</varlistentry>
<varlistentry>
<term><varname>IPv6Forwarding=</varname></term>
<listitem>
<para>Configures IPv6 packet forwarding for the system. Takes a boolean value. This controls the
<filename>net.ipv6.conf.default.forwarding</filename> and
<filename>net.ipv6.conf.all.forwarding</filename> sysctl options. See
<ulink url="https://docs.kernel.org/networking/ip-sysctl.html">IP Sysctl</ulink>
for more details about the sysctl options. Defaults to unset and the sysctl options will not be
changed.</para>
<xi:include href="version-info.xml" xpointer="v256"/>
</listitem>
</varlistentry>
network: add global setting for IPv6PrivacyExtensions= Closes #28186.
2023-06-29 13:09:53 +03:00
<varlistentry>
<term><varname>IPv6PrivacyExtensions=</varname></term>
<listitem>
<para>Specifies the default value for per-network <varname>IPv6PrivacyExtensions=</varname>.
Takes a boolean or the special values <literal>prefer-public</literal> and
<literal>kernel</literal>. See for details in
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Defaults to <literal>no</literal>.</para>
man: add version info This tries to add information about when each option was added. It goes back to version 183. The version info is included from a separate file to allow generating it, which would allow more control on the formatting of the final output.
2023-08-22 19:52:36 +03:00
<xi:include href="version-info.xml" xpointer="v254"/>
network: add global setting for IPv6PrivacyExtensions= Closes #28186.
2023-06-29 13:09:53 +03:00
</listitem>
</varlistentry>
man: add entry about SpeedMeter= Closes #14002.
2019-11-18 18:03:35 +03:00
</variablelist>
</refsect1>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
<refsect1>
network: make IAID and DUID for DHCPv6 configurable explicitly Closes #18996.
2021-04-10 04:24:17 +03:00
<title>[DHCPv4] Section Options</title>
<para>This section configures the DHCP Unique Identifier (DUID) value used by DHCP protocol. DHCPv4
client protocol sends IAID and DUID to the DHCP server when acquiring a dynamic IPv4 address if
<option>ClientIdentifier=duid</option>. IAID and DUID allows a DHCP server to uniquely identify the
machine and the interface requesting a DHCP IP address. To configure IAID and ClientIdentifier, see
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
<para>The following options are understood:</para>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
<variablelist class='network-directives'>
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
<varlistentry>
<term><varname>DUIDType=</varname></term>
<listitem><para>Specifies how the DUID should be generated. See
<ulink url="https://tools.ietf.org/html/rfc3315#section-9">RFC 3315</ulink>
for a description of all the options.</para>
network/dhcp: make DUIDType= take an arbitrary integer Closes #26745.
2023-08-22 08:32:07 +03:00
<para>This takes an integer in the range 0…65535, or one of the following string values:
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
<variablelist>
<varlistentry>
man: mention that DUIDType=uuid uses the product UUID or machine-ID
2018-06-25 15:32:41 +03:00
<term><option>vendor</option></term>
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
<listitem><para>If <literal>DUIDType=vendor</literal>, then the DUID value will be generated using
<literal>43793</literal> as the vendor identifier (systemd) and hashed contents of
<citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
This is the default if <varname>DUIDType=</varname> is not specified.
man: update version information As I noticed a lot of missing information when trying to implement checking for missing info. I reimplemented the version information script to be more robust, and here is the result. Follow up to ec07c3c80b2b1bfa6788500202006ff85f5ae4f4
2023-09-18 18:03:38 +03:00
</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
</varlistentry>
<varlistentry>
man: mention that DUIDType=uuid uses the product UUID or machine-ID
2018-06-25 15:32:41 +03:00
<term><option>uuid</option></term>
<listitem><para>If <literal>DUIDType=uuid</literal>, and <varname>DUIDRawData=</varname> is not set,
then the product UUID is used as a DUID value. If a system does not have valid product UUID, then
an application-specific
<citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry>
is used as a DUID value. About the application-specific machine ID, see
<citerefentry><refentrytitle>sd_id128_get_machine_app_specific</refentrytitle><manvolnum>3</manvolnum></citerefentry>.
man: update version information As I noticed a lot of missing information when trying to implement checking for missing info. I reimplemented the version information script to be more robust, and here is the result. Follow up to ec07c3c80b2b1bfa6788500202006ff85f5ae4f4
2023-09-18 18:03:38 +03:00
</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
man: mention that DUIDType=uuid uses the product UUID or machine-ID
2018-06-25 15:32:41 +03:00
</varlistentry>
<varlistentry>
man: mention that DUIDType=link-layer-time or link-layer uses MAC address
2018-08-07 08:03:57 +03:00
<term><option>link-layer-time[:<replaceable>TIME</replaceable>]</option></term>
man: mention that DUIDType=uuid uses the product UUID or machine-ID
2018-06-25 15:32:41 +03:00
<term><option>link-layer</option></term>
man: mention that DUIDType=link-layer-time or link-layer uses MAC address
2018-08-07 08:03:57 +03:00
<listitem><para>If <literal>link-layer-time</literal> or <literal>link-layer</literal> is specified,
then the MAC address of the interface is used as a DUID value. The value <literal>link-layer-time</literal>
can take additional time value after a colon, e.g. <literal>link-layer-time:2018-01-23 12:34:56 UTC</literal>.
The default time value is <literal>2000-01-01 00:00:00 UTC</literal>.
man: update version information As I noticed a lot of missing information when trying to implement checking for missing info. I reimplemented the version information script to be more robust, and here is the result. Follow up to ec07c3c80b2b1bfa6788500202006ff85f5ae4f4
2023-09-18 18:03:38 +03:00
</para>
<xi:include href="version-info.xml" xpointer="v240"/></listitem>
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
</varlistentry>
</variablelist>
</para>
<para>In all cases, <varname>DUIDRawData=</varname> can be used to override the
man: update version information As I noticed a lot of missing information when trying to implement checking for missing info. I reimplemented the version information script to be more robust, and here is the result. Follow up to ec07c3c80b2b1bfa6788500202006ff85f5ae4f4
2023-09-18 18:03:38 +03:00
actual DUID value that is used.</para>
<xi:include href="version-info.xml" xpointer="v230"/></listitem>
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
</varlistentry>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
<varlistentry>
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
<term><varname>DUIDRawData=</varname></term>
<listitem><para>Specifies the DHCP DUID value as a single newline-terminated, hexadecimal string, with each
byte separated by <literal>:</literal>. The DUID that is sent is composed of the DUID type specified by
<varname>DUIDType=</varname> and the value configured here.</para>
man: mention that DUIDType=uuid uses the product UUID or machine-ID
2018-06-25 15:32:41 +03:00
<para>The DUID value specified here overrides the DUID that
<citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry>
generates from the machine ID. To configure DUID per-network, see
man: fix some internal man page references sd_journal-query_enumerate was an early draft, the name was changed to sd_j_enumerate_fields.
2016-08-06 23:38:09 +03:00
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
The configured DHCP DUID should conform to the specification in
<ulink url="http://tools.ietf.org/html/rfc3315#section-9">RFC 3315</ulink>,
<ulink url="http://tools.ietf.org/html/rfc6355">RFC 6355</ulink>. To configure IAID, see
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum>
</citerefentry>.</para>
<example>
<title>A <option>DUIDType=vendor</option> with a custom value</title>
<programlisting>DUIDType=vendor
DUIDRawData=00:00:ab:11:f9:2a:c2:77:29:f9:5c:00</programlisting>
<para>This specifies a 14 byte DUID, with the type DUID-EN (<literal>00:02</literal>), enterprise number
43793 (<literal>00:00:ab:11</literal>), and identifier value <literal>f9:2a:c2:77:29:f9:5c:00</literal>.
</para>
</example>
man: update version information As I noticed a lot of missing information when trying to implement checking for missing info. I reimplemented the version information script to be more robust, and here is the result. Follow up to ec07c3c80b2b1bfa6788500202006ff85f5ae4f4
2023-09-18 18:03:38 +03:00
<xi:include href="version-info.xml" xpointer="v230"/>
man: add a description of DUIDType and DUIDRawData This is essentially a revert of f38e0cce75ff2ffbd99f7e382ed39c160bb7d799 (which removed the documentation of DUIDType on purpose). The description is heavily updated for the new semantics. This addresses #3127 § 4.
2016-04-30 03:16:55 +03:00
</listitem>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
</varlistentry>
network: add mechanism to configure default UseDomains= setting, update man page and add test
2024-04-10 03:40:42 +03:00
<varlistentry>
<term><varname>UseDomains=</varname></term>
<listitem><para>Specifies the default value for per-network <varname>UseDomains=</varname>.
Takes a boolean. See for details in
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Defaults to <literal>no</literal>.</para>
<xi:include href="version-info.xml" xpointer="v256"/>
</listitem>
</varlistentry>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
</variablelist>
</refsect1>
network: make IAID and DUID for DHCPv6 configurable explicitly Closes #18996.
2021-04-10 04:24:17 +03:00
<refsect1>
<title>[DHCPv6] Section Options</title>
<para>This section configures the DHCP Unique Identifier (DUID) value used by DHCPv6 protocol.
DHCPv6 client protocol sends the DHCP Unique Identifier and the interface Identity Association
Identifier (IAID) to a DHCPv6 server when acquiring a dynamic IPv6 address. IAID and DUID allows a
DHCPv6 server to uniquely identify the machine and the interface requesting a DHCP IP address. To
configure IAID, see
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
</para>
<para>The following options are understood:</para>
<variablelist class='network-directives'>
<varlistentry>
<term><varname>DUIDType=</varname></term>
<term><varname>DUIDRawData=</varname></term>
man: add version info This tries to add information about when each option was added. It goes back to version 183. The version info is included from a separate file to allow generating it, which would allow more control on the formatting of the final output.
2023-08-22 19:52:36 +03:00
<listitem><para>As in the [DHCPv4] section.</para>
<xi:include href="version-info.xml" xpointer="v249"/></listitem>
network: make IAID and DUID for DHCPv6 configurable explicitly Closes #18996.
2021-04-10 04:24:17 +03:00
</varlistentry>
network: add mechanism to configure default UseDomains= setting, update man page and add test
2024-04-10 03:40:42 +03:00
<varlistentry>
<term><varname>UseDomains=</varname></term>
<listitem><para>As in the [DHCPv4] section.</para>
<xi:include href="version-info.xml" xpointer="v256"/></listitem>
</varlistentry>
network: make IAID and DUID for DHCPv6 configurable explicitly Closes #18996.
2021-04-10 04:24:17 +03:00
</variablelist>
</refsect1>
network/dhcp-server: introduce PersistLeases= setting Requested at https://github.com/systemd/systemd/pull/31772#issuecomment-2000053357.
2024-03-15 20:32:50 +03:00
<refsect1>
<title>[DHCPServer] Section Options</title>
<para>This section configures the default setting of the DHCP server. The following options are available
in the [DHCPServer] section:</para>
<variablelist class='network-directives'>
<varlistentry>
<term><varname>PersistLeases=</varname></term>
<listitem>
<para>Specifies the default value for per-network <varname>PersistLeases=</varname>.
Takes a boolean. See for details in
<citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
Defaults to <literal>yes</literal>.</para>
<xi:include href="version-info.xml" xpointer="v256"/>
</listitem>
</varlistentry>
</variablelist>
</refsect1>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
<refsect1>
<title>See Also</title>
man: use <simplelist> for 'See also' sections This is just a slight markup improvement; there should be no difference in rendering.
2023-12-22 21:09:32 +03:00
<para><simplelist type="inline">
<member><citerefentry><refentrytitle>systemd</refentrytitle><manvolnum>1</manvolnum></citerefentry></member>
<member><citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
<member><citerefentry><refentrytitle>systemd-networkd.service</refentrytitle><manvolnum>8</manvolnum></citerefentry></member>
<member><citerefentry><refentrytitle>machine-id</refentrytitle><manvolnum>5</manvolnum></citerefentry></member>
<member><citerefentry><refentrytitle>sd_id128_get_machine_app_specific</refentrytitle><manvolnum>3</manvolnum></citerefentry></member>
</simplelist></para>
DHCP DUID, IAID configuration options
2016-03-31 02:33:55 +03:00
</refsect1>
</refentry>
Copy Permalink