[gentoo-dev] news item: dhcpcd-6.4.2 defaults to stable private ipv6 addresses

[gentoo-dev] news item: dhcpcd-6.4.2 defaults to stable private ipv6 addresses

[William Hubbs]

[-- Attachment #1.1: Type: text/plain, Size: 480 bytes --]

All,

this is a newsitem I want to post for the newest dhcpcd in the nesxt few
days.

I'm not interested in commenting out "slaac private" in the new
dhcpcd.conf by default, because as you will see in the references, there
are good reasons to keep that setting. However, what I would like to
know is whether I can nail down more how to describe when connectivity
can be lost so people don't get a surprise after they upgrade.

Any suggestions would be helpful.

Thanks,

William


[-- Attachment #1.2: 2014-07-17_dhcpcd_stable_private_ipv6_address_support.en.txt --]
[-- Type: text/plain, Size: 1165 bytes --]

Title: dhcpcd 6.4.2 defaults to stable private ipv6 addresses
Author: William Hubbs <williamh@gentoo.org>
Content-Type: text/plain
Posted: 2014-07-17
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <net-misc/dhcpcd-6.4.2

dhcpcd-6.4.2 and newer supports ipv6 stable private addresses when using
ipv6 stateless address autoconfiguration (SLAAC) as described in
RFC-7217 [1]. The configuration file shipped with dhcpcd activates this
feature by default, because it means that a machine cannot be tracked
across multiple networks since its address will no longer be based on
the hardware address of the interface.

We did receive a report in testing that ipv6 connectivity was lost due
to this change [2]. If you are concerned about losing ipv6 connectivity,
I recommend commenting out the line in dhcpcd.conf that says "slaac
private" when you upgrade.

See the references below for why the upstream default is to use private
addresses.

[1] http://tools.ietf.org/html/rfc7217
[2] https://bugs.gentoo.org/show_bug.cgi?id=514198
[3] http://tools.ietf.org/html/draft-ietf-6man-default-iids-00
[4] http://mail-index.netbsd.org/tech-net/2014/06/04/msg004572.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-dev] news item: dhcpcd-6.4.2 defaults to stable private ipv6 addresses

[William Hubbs]

[-- Attachment #1.1: Type: text/plain, Size: 118 bytes --]

All,

I am reposting this because I got a couple of updates from IRC.

Let me know what you think.

Thanks,

William


[-- Attachment #1.2: 2014-07-17_dhcpcd_stable_private_ipv6_address_support.en.txt --]
[-- Type: text/plain, Size: 1166 bytes --]

Title: dhcpcd 6.4.2 defaults to stable private IPv6 addresses
Author: William Hubbs <williamh@gentoo.org>
Content-Type: text/plain
Posted: 2014-07-17
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <=net-misc/dhcpcd-6.4.2

dhcpcd-6.4.2 and newer supports IPv6 stable private addresses when using
IPv6 stateless address autoconfiguration (SLAAC) as described in
RFC-7217 [1]. The configuration file shipped with dhcpcd activates this
feature by default, because it means that a machine cannot be tracked
across multiple networks since its address will no longer be based on
the hardware address of the interface.

We did receive a report in testing that IPv6 connectivity was lost due
to this change [2]. If you are concerned about losing IPv6 connectivity,
I recommend commenting out the line in dhcpcd.conf that says "slaac
private" when you upgrade.

See the references below for why the upstream default is to use private
addresses.

[1] http://tools.ietf.org/html/rfc7217
[2] https://bugs.gentoo.org/show_bug.cgi?id=514198
[3] http://tools.ietf.org/html/draft-ietf-6man-default-iids-00
[4] http://mail-index.netbsd.org/tech-net/2014/06/04/msg004572.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-dev] news item: dhcpcd-6.4.2 defaults to stable private ipv6 addresses

[William Hubbs]

[-- Attachment #1.1: Type: text/plain, Size: 176 bytes --]

All,

here is the second update from IRC today.

I reworded the title and added more information to the body recommending
that users adjust to the new configuration.

William


[-- Attachment #1.2: 2014-07-17-dhcpcd_6.4.2_changes_defaults_for_ipv6.en.txt --]
[-- Type: text/plain, Size: 1227 bytes --]

Title: dhcpcd >= 6.4.2 changes defaults for IPv6
Author: William Hubbs <williamh@gentoo.org>
Content-Type: text/plain
Posted: 2014-07-17
Revision: 1
News-Item-Format: 1.0
Display-If-Installed: <=net-misc/dhcpcd-6.4.2

dhcpcd-6.4.2 and newer supports IPv6 stable private addresses when using
IPv6 stateless address autoconfiguration (SLAAC) as described in
RFC-7217 [1]. The configuration file shipped with dhcpcd activates this
feature by default, because it means that a machine cannot be tracked
across multiple networks since its address will no longer be based on
the hardware address of the interface.

We did receive a report in testing that IPv6 connectivity was lost due
to this change [2]. If you are concerned about losing IPv6 connectivity,
I recommend temporarily commenting out the line in dhcpcd.conf that says
"slaac private" until you can adjust to the new configuration.

See the references below for why the upstream default is to use stable
private instead of hardware-based addresses.

[1] http://tools.ietf.org/html/rfc7217
[2] https://bugs.gentoo.org/show_bug.cgi?id=514198
[3] http://tools.ietf.org/html/draft-ietf-6man-default-iids-00
[4] http://mail-index.netbsd.org/tech-net/2014/06/04/msg004572.html

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

Re: [gentoo-dev] news item: dhcpcd-6.4.2 defaults to stable private ipv6 addresses

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 166 bytes --]

>>>>> On Mon, 14 Jul 2014, William Hubbs wrote:

> We did receive a report [...]
> I recommend [...]

Use either plural or singular throughout, but not both.

Ulrich

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]