summaryrefslogtreecommitdiff
path: root/man/systemd.network.xml
diff options
context:
space:
mode:
authorYu Watanabe <watanabe.yu+github@gmail.com>2022-07-22 13:11:20 +0900
committerYu Watanabe <watanabe.yu+github@gmail.com>2022-07-22 21:28:20 +0900
commit50ee1fec3a7db383903ce9870239161bce908787 (patch)
treed1fc134113a5992526e7490503e206377f0e49eb /man/systemd.network.xml
parent4397967f8ccaf50885eecfbc5df927613852de66 (diff)
downloadsystemd-50ee1fec3a7db383903ce9870239161bce908787.tar.gz
network: dhcp6: re-introduce RapidCommit= setting
Previous implementation of disabling rapid commit was broken, and dropped by 308d01f3c4decf3240ca0c6c7f91049953df7299. Let's re-introduce the option in the correct way, as some servers seem to return borked message when the solicit message contain the rapid commit option. Closes #24065.
Diffstat (limited to 'man/systemd.network.xml')
-rw-r--r--man/systemd.network.xml13
1 files changed, 13 insertions, 0 deletions
diff --git a/man/systemd.network.xml b/man/systemd.network.xml
index 2d3bb66e39..76a924cec7 100644
--- a/man/systemd.network.xml
+++ b/man/systemd.network.xml
@@ -2147,6 +2147,19 @@ Table=1234</programlisting></para>
</listitem>
</varlistentry>
+ <varlistentry>
+ <term><varname>RapidCommit=</varname></term>
+ <listitem>
+ <para>Takes a boolean. The DHCPv6 client can obtain configuration parameters from a DHCPv6 server
+ through a rapid two-message exchange (solicit and reply). When the rapid commit option is set by
+ both the DHCPv6 client and the DHCPv6 server, the two-message exchange is used. Otherwise, the
+ four-message exchange (solicit, advertise, request, and reply) is used. The two-message exchange
+ 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>
+ </listitem>
+ </varlistentry>
+
<!-- How to use the DHCP lease -->
<varlistentry>