Open perkelix opened 11 months ago
It's basically a race between the kernel adding the address and dhcpcd adding it. If a lladdr already exists then dhcpcd will use it.
By default dhcpcd will turn the sysctl off for the kernel adding lladdrs for the interface when it gets activated. This is because dhcpcd has supported stable private addresses for many years before any kernel did.
So don't turn the sysctls on and you should be fine.
On 10.0.2, since a few days, whenever delegating a prefix, dhcpcd creates a fresh fe80:: address on the bridge, in addition to the existing one:
As seen below, ::a887 is the address created when
ifupdown
creates the bridge. It has stable-privacy enabled viasysctl
on bootup. Meanwhile, ::733b is created as above by dhcpcd.Am I missing anything? Why wouldn't dhcpcd keep on using the existing IPv6 locallink?