(talking about the client side thing for now, not to confuse with dhcpd server side)
I incidentally stumbled into some coherence issues in Client DHCP services:
wireless.js seems to mostly use dhcpcd (although some variable names may refer to the other due to historic reason).
However, dhcpcd has no proper systemd service set, as the service file is erroneously named .conf. It has a real .conf file though.
On the other hand dhclient has a proper service set and .conf file, but isc-dhcp-client or dhcp3-client are nowhere to be found...
Is this mix really intended or historical leftovers?
@earlchew could you help set some coherence and clean-up as per your earlier recommandations?
I guess all dhclient related stuff should probably go away, and dhcpcd stuff fine-tuned.
Thanks for thoughts.
(talking about the client side thing for now, not to confuse with
dhcpdserver side)I incidentally stumbled into some coherence issues in Client DHCP services:
wireless.jsseems to mostly usedhcpcd(although some variable names may refer to the other due to historic reason).However,
dhcpcdhas no propersystemdservice set, as the service file is erroneously named.conf. It has a real .conf file though.On the other hand
dhclienthas a proper service set and .conf file, butisc-dhcp-clientordhcp3-clientare nowhere to be found...Is this mix really intended or historical leftovers?
@earlchew could you help set some coherence and clean-up as per your earlier recommandations?
I guess all
dhclientrelated stuff should probably go away, anddhcpcdstuff fine-tuned.Thanks for thoughts.