Opened 7 weeks ago

Last modified 4 weeks ago

#16527 new task

dhclient End of Maintenance (wait for next version)

Reported by: pierre Owned by: blfs-book
Priority: normal Milestone: 99-Waiting
Component: BOOK Version: git
Severity: normal Keywords:


As said in this blog post dhcp-4.4.3 is the last version of ISC dhcp containing a client.

We may want to:

  1. check whether anybody uses the server part, and if nobody, remove dhcp altogether
  2. see if we want to find a replacement for the client or content with dhcpcd in the book

Change History (3)

comment:1 by Bruce Dubbs, 7 weeks ago

I'm good with only dhcpcd as a client.

I do think we need to keep dhcp as a server though. For instance if someone is setting up a network, then someone may want explicit control over how ip addresses are assigned. I admit the most of our users probably use the built in dhcp server in their router, but we still need it for completeness.

Removing dhclient will require changes in several places: wpa_supplicant, networkmanager, and unbound come to mind as well as the dhcp page itself. Also the bootscripts and systemd-units will need to be reviewed.

comment:2 by Bruce Dubbs, 7 weeks ago

Milestone: 11.299-Waiting
Summary: dhclient End of Maintenancedhclient End of Maintenance (wait for next version)

dhclient is OK for now. Address this when it is actually removed.

comment:3 by thomas, 4 weeks ago

I'd also vote for keeping a dhcp server in the book. DHCP is an essential part of a network which contains more devices than just a few. We cannot assume that dhcp provided by the routers is usable for everyone. It might, but it need not to be. When it comes to (experimental) use of network boot setup, a more detailed configuration of dhcp is required which is often impossible with dhcp servers built in routers.

Maybe we want to have a look at Kea, the successor of the ISC-DHCP product, at anyhow.

Note: See TracTickets for help on using tickets.