Hi, ifupdown2 doesn't have any plan to provide support for a new DHCP client. We are open to community proposal/PR to add support for a new client.
Julien On Mon, 02 Jun 2025 09:56:14 +0200 Fabian =?iso-8859-1?q?Gr=FCnbichler?= <f.gruenbich...@proxmox.com<mailto:f.gruenbich...@proxmox.com>> wrote: > On May 27, 2025 7:58 pm, Thomas Lange wrote: > > Hi, > > > > this bug also affects more packages that are not in the reverse dependency. > > Several packages call dhclient and sometimes with options that are > > only available for the isc dhcp client, like -lf ,-pf, -sf > > > > Following packages may be affected by the removal of isc-dhcp from > > trixie, because I couldn't find code that supports another dhcp > > client/server in those packages: > > > > - [..] > > - ifupdown2 in ifupdownaddons/dhclient.py > > - [..] > > related upstream (stalled) PR: > > https://github.com/CumulusNetworks/ifupdown2/pull/253 > > note that ifupdown2 currently only Suggests isc-dhcp-client, while DHCP > support is optional in a technical sense (Recommends might still have > been a better fit), it is quite important for many setups, so dropping > it altogether is not really an option IMHO. > > I'll try to get progress on that (or a similar) PR going again to allow > ifupdown2 to drop its usage of isc-dhcp-client in favor of one or more > more suitable client implementations for Forky, but I think there is no > (reasonable) solution for Trixie other than keeping isc-dhcp-client > around (with no security support). > > >
