dhcpcd-discuss

On 04/02/2016 22:41, Nicholas Williams wrote:
> Out of curiosity, what did you do?

For dhcpcd-6.10.0, it now loads all interfaces in the system regardless
of if they are being used by dhcpcd or not so it can better handle
addresses and routes it want to apply to the running interface which are
already resourced to other interfaces.
Part of this was adding an active flag to the interface, a simple
boolean. This was quite a large amount of work.

Now, it was just a matter of extending that flag so that we have
activated by user and activated by system (ie for Prefix Delegation).
When dhcpcd_activateinterface is called, it also accepts an option list
which DHCPv6 PD defines as follows

DHCPCD_IPV6 | DHCPCD_DHCP6

So all other options are off.
The freshly activated interface will inherit global options configured,
such as persistence and slaac privacy. There is currently no way to turn
this off per system activated interface - you will have to get dhcpcd to
control the interface fully as before, but I doubt this will be needed.

dhcpcd also allows you to turn a system activated interface into a user
one, stop it, rebind the master interface and the delegated interface
starts system activated again. So full control.

In other words, this long standing issue was only made possible by tech
changes from other issues. It was never a priority because you could
work around it by disabling IPv4 and others per interface. But this is
no longer needed :)

Enough of the history lesson for now!

Roy