I've deleted all deprecated addresses from earlier, and it went through at least one other cycle of
Aug 13 22:27:50 murthe dhcpcd[335]: re1: unauthenticated RECONFIGURE6 from
fe80::a96:d7ff:fea9:5c20
Aug 13 22:27:50 murthe dhcpcd[335]: re0: unauthenticated RECONFIGURE6 from
fe80::a96:d7ff:fea9:5c20
Aug 13 22:27:50 murthe dhcpcd[335]: re0: not bound, ignoring RECONFIGURE6
Aug 13 22:27:50 murthe dhcpcd[335]: re1: DHCPv6 REPLY: not on link
and now the addresses on re1 look like
inet6 fe80::5d5:95c6:17e9:8ede%re1/64 flags 0x0 scopeid 0x2
1 inet6 2003:ca:5f1c:c900:3d0f:6b7d:e5d8:624d/64 flags 0x10<DEPRECATED>
2 inet6 2003:ca:5f1c:c900:5d5:95c6:17e9:8ede/128 flags 0x0
inet6 fd00::359b:6cd5:acb3:7bdc/64 flags 0x10<DEPRECATED>
3 inet6 2003:ca:5f1d:2d00:3255:ef34:771e:4a5/64 flags 0x0
4 inet6 2003:ca:5f1d:2d00:5d5:95c6:17e9:8ede/128 flags 0x0
It looks like (3) and (4) are new, and (1) and (2) are old.
It created TWO new addresses in the new prefix, but for the old ones, it
deprecated only one of the pair?
Neither of these addresses are based on my Ethernet address.
(3) may be the result of "slaac private", but the other one looks
random. I don't have sysctls set for "temp" addresses, in case it could
be related to that:
net.inet6.ip6.use_tempaddr = 0
net.inet6.ip6.prefer_tempaddr = 0
-Olaf.
--
Olaf 'Rhialto' Seibert -- rhialto at falu dot nl
___ Anyone who is capable of getting themselves made President should on
\X/ no account be allowed to do the job. --Douglas Adams, "THGTTG"
signature.asc
Description: PGP signature
