ISC plans to end maintenance of the ISC DHCP client and relay by the end of Q1, 2022.

The Internet Systems Consortium has stopped maintaining their DHCP client, which is standard on a lot of distros.
Debian has updated its documentation and now warns users to choose an alternative:

https://packages.debian.org/bookworm/isc-dhcp-client

On Debian Unstable, I was already forced to uninstall it in yesterday’s upgrade.
If you’re using network-manager, you don’t need to worry, since it includes its own dhcp client, but for others, this might be relevant.

On Arch, this concerns the dhcpd package:
https://wiki.archlinux.org/title/Dhcpd

  • RavuAlHemio@lemmy.world
    9·
    1 year ago

    On Arch, the client is in the dhclient package, which is generally also the name of the ISC DHCP client binary.

    dhcpcd (DHCP Client Daemon) is not affiliated with the ISC and still appears to be under active development.

    • KISSmyOS@lemmy.worldOP
      3·
      1 year ago

      I mentioned dhcpd (the ISC DHCP server demon), not dhcpcd, the unaffiliated DHCP Client demon.

      • RavuAlHemio@lemmy.world
        5·
        1 year ago

        Yes; I wanted to mention that dhcpcd is not affected because the title explicitly mentions the DHCP client (dhclient), so people might go looking for alternative DHCP clients in the comments.

        I think it’s a bit confusing that you mentioned the DHCP client (dhclient) and DHCP relay (dhrelay) in the title, then link to the Arch Wiki article about the DHCP server (dhcpd). Yes, dhrelay is contained in the dhcpd package (dhclient, however, is not), but I assume most people will be using a DHCP client and few will be operating a DHCP server or relay.

    • KISSmyOS@lemmy.worldOP
      7·
      1 year ago

      When I updated Debian Unstable 2 days ago, it forced me to uninstall isc-dhcp-client in order to upgrade network-manager.
      So I looked up the reason and found the ISC’s blog post. I shared it here thinking it might be interesting to some, since Debian’s packages are the basis for a lot of other distros that might be affected soon.

  • TCB13@lemmy.worldEnglish
    42·
    1 year ago

    And here I was thinking people were about to move to systemd-networkd so network would actually work decently on the Linux desktop and then I remembered that GNOME comes with the bs called network-manager.

      • TCB13@lemmy.worldEnglish
        2·
        1 year ago

        That’s gonna be a good day. I’m sure they’ll have the common sense to include systemd-desktopd-iconsd and systemd-desktopd-slow-transition-animationsd will be optional. :P

    • code@lemmy.zip
      2·
      1 year ago

      God i hate network manager and the vpnc plugin specifically. Its been broken for almost 2 years. You cannot add a vpnc vpn in network manager.

    • Laser@feddit.de
      1·
      1 year ago

      I use both depending on the device. My desktop at home and all servers use systemd-networkd and I’m very happy with it. Right now, I’m on vacation and NetworkManager comes in very helpful with the ability to quickly manage networks as a normal user with a graphical user interface.

      • TCB13@lemmy.worldEnglish
        32·
        1 year ago

        Question is: why can’t the GNOME people that are so eager to reinvent everything dedicate a few bucks out of their new 1M€ funding and integrate it with systemd-networkd and ditch the old NetworkManager for good. That thing is inconsistent and to make things worse now we’ve the “new network settings” with some settings and then the NetworkManager window/GUI with more settings and things are as coherent as Windows 10’s new Settings vs Control Panel… Fucks sake GNOME.

        For what’s worth in Windows I can pull the old Control Panel Network Connections settings go into properties and manage everything network adapters have to over with a simple tab based navigation. In GNOME right now it is a shit show of jumping around between the GNOME Settings and the older NetworkManager GUI to end up not being able to easily get a VLAN tag on some connection.