> Unless you hardcode your IPv6 addresses, they will be generated automatically and change quite frequently. If you're talking about "Privacy Addresses" [0], t

> Unless you hardcode your IPv6 addresses, they will be generated automatically and change quite frequently. If you're talking about "Privacy Addresses" [0], then your statement isn't always true. If you're not using "Privacy Addresses", [1] your SLAAC or DHCPv6-assigned address remains quite stable, unless your upstream provider changes the prefix that they've assigned to your network. > In fact, as far as I remember you can actually statically assign your machines easy to remember addresses... You don't even have to assign addresses. SLAAC automatically creates stable addresses. "Privacy Addressing" creates random, temporary addresses. You can use both at the same time. [0] https://tools.ietf.org/html/rfc4941 https://tools.ietf.org/html/rfc4941 [1] And I strongly recommend that you don't. For folks who are concerned about being able to be tracked because they have a stable last 64 on every network they attach to, there are alternative methods for generating the ID used to create the SLAAC address that mix in the network prefix. [2][3] This means that -for a particular network-, you get the same last 64 every time you connect, but your last 64 is never the same on any two networks. [2] https://tools.ietf.org/html/rfc7217 https://tools.ietf.org/html/rfc7217 [3] On linux, dhcpcd has the "slaac private" option which enables RFC7217 address generation. "slaac hwaddr" uses the traditional, MAC address based address generation. "slaac private" (or its equivalent in other daemons) is the default setting of every Linux distro I've used in the past 6->12 months. :)