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

  • Strit@lemmy.linuxuserspace.show
    122·
    1 year ago

    The Arch wiki article already states it’s unmaintained since January 2023. So Arch users have had almost a year to find another solution at this point.

    • KISSmyOS@lemmy.worldOP
      9·
      1 year ago

      I posted mainly because Debian now seems to force a switch in Unstable and many distros rely on its packages.

  • 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.

  • Pantherina@feddit.de
    61·
    1 year ago

    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.

    So… every GNOME and KDE Distro is unaffected? Other Desktops too?

    • Laser@feddit.de
      5·
      1 year ago

      Neither GNOME nor Plasma depend on NetworkManager, do they? Plasma will happily show information about connections managed by something else than NetworkManager, but won’t be able to manage them itself. But desktop distributions will most likely ship it as it covers basically all use cases.

      • KISSmyOS@lemmy.worldOP
        3·
        1 year ago

        Neither GNOME nor Plasma depend on NetworkManager, do they?

        Not directly, but distros may choose to create a dependency.

        On Debian, installing recommended dependencies is enabled by default and disabling them can lead to all sorts of errors and missing functionality.
        gnome-shell recommends gnome-control-center, which recommends network-manager-gnome, which depends on network-manager.
        So unless you go out of your way to install a very minimal system, it gets pulled in.

        • Laser@feddit.de
          41·
          1 year ago

          From my point of view, nothing else but NetworkManager makes sense to ship by default for a distribution aimed at desktop use. So I fully understand distributions doing this. My point was rather that this is not related to any particular WM / DE.

          • kixik
            1·
            1 year ago

            I don’t think so. Dhcpcd + wpa_supplicant is really light, suitable for light installers, and live USB stick images.

            I’ve been using dhcpcd + wpa_supplicant for so long… I do understand currently users prefer NM, but I hope there’s no push for it to be the unique way to manage network connectivity, and on light installers, I hope I’m not force to use NM either.

            • Laser@feddit.de
              3·
              1 year ago

              I mean traditionally NetworkManager uses wpa_supplicant anyways though there is the option for iwd. So it will stay available for quite some time.

    • pastermil@sh.itjust.works
      11·
      1 year ago

      Other DEs should use network manager as well. I’ve tested this at least on MATE, XFCE, as well as Cinnamon.

      This is not a guarantee, tho, as users can pretty much install whatever they want.

    • 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.