diff options
| author | Roy Marples <roy@marples.name> | 2015-01-21 19:37:39 +0000 |
|---|---|---|
| committer | Roy Marples <roy@marples.name> | 2015-01-21 19:37:39 +0000 |
| commit | 2e5933998317622c35b5f56d4e2cb20a7ea7decd (patch) | |
| tree | d7b7293e881a750e0485b0102a20907a9268dba3 /README | |
| parent | 6635ae0d32910efbdf67510967f19ba8a4f79467 (diff) | |
| download | dhcpcd-2e5933998317622c35b5f56d4e2cb20a7ea7decd.tar.xz | |
Update to reflect 3.16 or older kernels and the header mismatch in ArchLinux on ARM.
Diffstat (limited to 'README')
| -rw-r--r-- | README | 13 |
1 files changed, 13 insertions, 0 deletions
@@ -61,6 +61,19 @@ be assumed to be reachable until they either stop being a router or expire. BSD systems where this has been fixed or is known to work are: NetBSD-7.99.3 +Linux prior to 3.17 won't allow userland to manage IPv6 temporary addresses. +Either upgrade or don't allow dhcpcd to manage the RA, +so don't set either "ipv6ra_own" or "slaac private" in dhcpcd.conf if you +want to have working IPv6 temporary addresses. +SLAAC private addresses are just as private, just stable. + +ArchLinux presently sanitises all kernel headers to the latest version +regardless of the version for your CPU. As such, Arch presently ships a +3.12 kernel with 3.17 headers which claim that it suppors temporary address +management and no automatic prefix route generation, both of which are +obviously false. You will have to patch support either in the kernel or +out of the headers (or dhcpcd itself) to have correct operation. + We try and detect how dhcpcd should interact with system services at runtime. If we cannot auto-detect how do to this, or it is wrong then you can change this by passing shell commands to --serviceexists, |
