diff options
| author | Tom Gundersen <teg@jklm.no> | 2016-02-23 00:21:53 +0100 |
|---|---|---|
| committer | Tom Gundersen <teg@jklm.no> | 2016-02-23 01:25:32 +0100 |
| commit | eb142d8ec11b4d0dbda882c18da7c859a5919459 (patch) | |
| tree | cb37c3eb361b19b7db3d1384d089047e397369dc | |
| parent | 4d080d7798c938c3accc8555182e5ef515967bae (diff) | |
man: network - improve IPv6Token documentation
Enabling router advertisement may even trigger SLAAC or DHCPv6 to be used to configure
IPv6 addresses on the link. It may not be obvious that only in the SLAAC case will the
Token have an effect. Clarify this in the man page.
Addresses issue #863.
| -rw-r--r-- | man/systemd.network.xml | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/man/systemd.network.xml b/man/systemd.network.xml index b6f81cc9ba..a6e059ed17 100644 --- a/man/systemd.network.xml +++ b/man/systemd.network.xml @@ -270,8 +270,10 @@ <term><varname>IPv6Token=</varname></term> <listitem> <para>An IPv6 address with the top 64 bits unset. When set, indicates the - 64-bit interface part of SLAAC IPv6 addresses for this link. By default, - it is autogenerated.</para> + 64-bit interface part of SLAAC IPv6 addresses for this link. Note that + the token is only ever used for SLAAC, and not for DHCPv6 addresses, even + in the case DHCP is requested by router advertisment. By default, the + token is autogenerated.</para> </listitem> </varlistentry> <varlistentry> |