Commit d3b82680 authored by Darren 'Tadgy' Austin's avatar Darren 'Tadgy' Austin

Update README.IPv6.

parent a270b7c3
......@@ -50,8 +50,8 @@ Implementation
auto configuration, even if DHCP6 is available on the network. If stateless RA auto
configuration is not available on the network, no IPv6 address will be assigned.
If this option is set to "yes", the options IPALIASES[x] and IPALIASES6[x] are ignored
as assigning aliases onto a stateless interface seems bad practice. [This limitation
can be removed if required].
as assigning static aliases onto a stateless interface seems bad practice.
[This limitation can be removed if required].
USE_DHCP6[x]="" Use dhcpcd to configure the interface. This will bring up the interface using DHCP6,
falling back to stateless RA auto configuration (if available on the network), or will
leave the interface unconfigured.
......@@ -70,9 +70,8 @@ Implementation
in the usual way using the IPv4 IPALIASES[x] option in rc.inet1.conf. IPv6 aliases are configured using the following
new option for rc.inet1.conf:
IPALIASES6[x]="" A space delimited list of IPv6 addresses and prefix combinations which should be added
to the interface.
Addresses should be listed in the format: ipaddr/prefix -- If no prefix is set, 64 is
assumed.
to the interface. Addresses should be listed in the format: ipaddr/prefix -- If no
prefix is set, 64 is assumed.
Changes from previous Slackware versions
......@@ -92,7 +91,7 @@ Changes from previous Slackware versions
is an configuration enhancement.
* In previous versions, the IP aliases configuration for IPv4 assumed a netmask of /32, making the interface only
addressable by itself. Now, a netmask of /24 is assumed where none is provided in the configuration. This is a
bugfix.
bugfix, but can be easily changed back to the old behaviour if undesired.
Known issues
......@@ -102,15 +101,15 @@ Known issues
previously configured - it can only stop the interface based upon its current configuration. This is a by-product of
the way the rc.inet1 script is coded (there is no record kept of the previous configuration type of an interface) and
is present (but doesn't seem to be documented anywhere) on previous versions of Slackware. This particular issue is
not specifically related to IPv6.
not specifically related to IPv6, but is documented here for completeness.
* When being killed in if_down(), dhcpcd requires some command line options to match those which were used to invoke it
- not only does the interface name need to match, but also the use of -4/-6. This can cause a problem during a
restart or stop/start of the interface if the configuration for DHCP has changed. This manifests itself in the same
way as the issue detailed above and is no more serious. In both cases, the end user must stop the dhcpcd daemon
manually. This issue is caused by the new way dhcpcd is invoked due to IPv6.
way as the issue detailed above and is no more serious. In both cases, the end user must kill the dhcpcd daemon
manually. This issue is caused by the new way dhcpcd is invoked when using/not using IPv6.
* If the interface is configured via DHCP (v4 or v6), there is a possibility that it will remain in the 'up' state (but
unconfigured with an IP address) after if_down() returns. This is because of an issue where rc.inet1 will
not configured with an IP address) after if_down() returns. This is because of an issue where rc.inet1 will
de-configure and take down the interface, only for the kernel to kick the interface back into 'up' state several
seconds after the interface first goes down. Without increasing the current 2 second delay to a minimum of 5 seconds
(the observed max lag time for this effect) there is no way to prevent this from happening. This issue was also
present on previous versions of Slackware, so is not change in behaviour, just an annoyance.
(the observed max lag time for this effect) there is no way to prevent this from happening. This issue is not related
to IPv6 and was also present on previous versions of Slackware; so is not change in behaviour, just an annoyance.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment