Am 19.06.23 um 12:54 schrieb Martin-Éric Racine:
Greetings, Seeing how the ISC DHCP suite has reached EOL upstream, now might be a good time to re-visit Debian's choice of standard DHCP client shipping with priority:important. I hereby propose bin:dhcpcd-base: 1) already supported by ifupdown. 2) dual stack (DHCPv4, Bonjour, RA, DHCPv6 with PD) with privilege separation. 3) writes both IPv4 and IPv6 name servers to /etc/resolv.conf 4) supports /etc/resolv.conf.head and /etc/resolv.conf.tail 5) a mere inet line in /etc/network/interfaces is sufficient to configure both stacks. While dhcpcd development became somewhat erratic last year due to upstream's health issues, things are seemingly back to normal. Additionally, a new developer has joined and is willing to take over the development should upstream's health deteriorate again.
Why does isc-dhcp-client have priority:important to begin with?I don't think users care so much about a dhcp client but rather a network configuration system and each network configuration system has its own preferred dhcp implementation e.g NetworkManager no longer uses isc-dhcp-client by default and systemd-networkd doesn't use isc-dhcp-client either.
So maybe simply demoting the priority of isc-dhcp-client to normal is a better route. ifupdown already recommends isc-dhcp-client and if ifupdown want's to use dhcpcd in the future it could change this recommends.
Regards, Michael
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature