dhcpcd-discuss

On 03/02/2016 13:41, Nicholas Williams wrote:
> So, is this a related problem? :
> 
> I noticed that each time I start dhcpcd for eth2, it always says this
> (and it's always the same address ending in d416, which is to be
> expected with autoconf):
> 
> eth2: adding address 2600:1004:b15b:f338:a00:27ff:fe21:d416/64
> 
> However, it actually adds TWO global addresses to the interface, not
> just that one ending in d416, and the second address is always
> different. Okay, no biggie ... this still isn't the problem.

I snipped the rest of the post which details dhcpcd not actually dealing
with any other addresses.
So if it's not dhcpcd, then what is?

The most likely answer is that you have the kernel handling IPv6
temporary addresses. You can see this using the `ip a` command instead
of ifconfig. Of course on a BSD system you would use ifconfig still ;)

Arch has a good wiki on this.
https://wiki.archlinux.org/index.php/IPv6#Privacy_extensions

Roy