from the quill of Chmouel Boudjnah <[EMAIL PROTECTED]> on scroll
<[EMAIL PROTECTED]>
>
> we have already two dhcp client pump and dhpcd. what problems with
> dhcpcd ?
The problem with both pump and dhcpcd is that neither goes to any effort
to maintain the client's address across a "REBOOT". This sucks because
if your client is served by mulitple DHCP servers each with their own
address pools you can wind up with a different address when you
start/stop the DHCP client. The ISC client does not suffer this problem
because it will remember the last address given and (more properly)
issue a DHCPREQUEST rather than restarting with a DHCPDISCOVER.
Further more, the ISC client is by far more configurable than either
dhcpcd and pump. I can specify exactly what parameters I want to accept
from the server and which ones I want to override, as well I can
configure what happens when an address is attainee, doing DDNS updates
for instance, or reconfiguring other software on the local machine that
needs to know that the address might have changed.
> we can't put 3 client on main cd, until the DVD coming we have to
> think about space.
Bah! The ISC client is already on the CD!! I am just proposing that it
get used in ifup for DHCP rather than, or in priority to dhcpcd. I
cannot see how dhcpcd nor pump are better solutions, indedd the ISC
dhclient offers far more functionality with no penalty.
b.
--
Brian J. Murrell InterLinx Support Services, Inc.
North Vancouver, B.C. 604 983 UNIX
Platform and Brand Independent UNIX Support - R3.2 - R4 - BSD
