diff options
| author | Alex Henrie <alexh@vpitech.com> | 2022-05-06 14:01:53 -0600 |
|---|---|---|
| committer | Alex Henrie <alexh@vpitech.com> | 2022-05-06 14:01:53 -0600 |
| commit | 0bcc6557fbba32ebcdf323e76688ced50e3c8d8e (patch) | |
| tree | 81c6a7e7d1869bcd03c9159fd58de72126251dd0 /man/systemd.network.xml | |
| parent | ad11dd94fd942b8f7531ed6420418d998fc3d34f (diff) | |
| download | systemd-0bcc6557fbba32ebcdf323e76688ced50e3c8d8e.tar.gz | |
network: clarify the relationship between RA flags and DHCPv6 modes
In the documentation, using the term "managed" for both the RA flag and
the DHCPv6 mode is confusing because the mode is referred to as
"solicit" both in the official DHCPv6 documentation (see RFC 8415) and
in the WithoutRA option.
Furthermore, calling the other RA flag "other information" or "other
address configuration" is confusing because its official name is simply
"other configuration" (see RFC 4861 and RFC 5175) and it isn't used to
assign IP addresses.
Rewrite the documentation for DHCPv6Client and WithoutRA to make it
clear that getting the "managed" RA flag triggers the same kind of DHCP
request as WithoutRA=solicit, whereas getting the "other configuration"
RA flag triggers the same kind of DHCP request as
WithoutRA=information-request.
Diffstat (limited to 'man/systemd.network.xml')
| -rw-r--r-- | man/systemd.network.xml | 19 |
1 files changed, 12 insertions, 7 deletions
diff --git a/man/systemd.network.xml b/man/systemd.network.xml index 530319606a..ac8cd1342d 100644 --- a/man/systemd.network.xml +++ b/man/systemd.network.xml @@ -2172,9 +2172,10 @@ Table=1234</programlisting></para> <varlistentry> <term><varname>WithoutRA=</varname></term> <listitem> - <para>Allows DHCPv6 client to start without router advertisements's managed or other - address configuration flag. Takes one of <literal>no</literal>, <literal>solicit</literal> - or <literal>information-request</literal>. If this is not specified, + <para>Allows DHCPv6 client to start without router advertisements's + <literal>managed</literal> or <literal>other configuration</literal> flag. Takes one of + <literal>no</literal>, <literal>solicit</literal>, or + <literal>information-request</literal>. If this is not specified, <literal>solicit</literal> is used when <varname>DHCPPrefixDelegation=</varname> is enabled and <varname>UplinkInterface=:self</varname> is specified in the [DHCPPrefixDelegation] section. Otherwise, defaults to <literal>no</literal>, and the DHCPv6 client will be started @@ -2507,10 +2508,14 @@ Token=prefixstable:2002:da8:1::</programlisting></para> <term><varname>DHCPv6Client=</varname></term> <listitem> <para>Takes a boolean, or the special value <literal>always</literal>. When true, the - DHCPv6 client will be started when the RA has the managed or other information flag. If set - to <literal>always</literal>, the DHCPv6 client will be started in managed mode when an RA - is received, even if neither managed nor other information flag is set in the RA. This will - be ignored when <varname>WithoutRA=</varname> in the [DHCPv6] section is enabled, or + DHCPv6 client will be started in <literal>solicit</literal> mode if the RA has the + <literal>managed</literal> flag or <literal>information-request</literal> mode if the RA + lacks the <literal>managed</literal> flag but has the + <literal>other configuration</literal> flag. If set to <literal>always</literal>, the + DHCPv6 client will be started in <literal>solicit</literal> mode when an RA is received, + even if neither the <literal>managed</literal> nor the + <literal>other configuration</literal> flag is set in the RA. This will be ignored when + <varname>WithoutRA=</varname> in the [DHCPv6] section is enabled, or <varname>UplinkInterface=:self</varname> in the [DHCPPrefixDelegation] section is specified. Defaults to true.</para> </listitem> |