buck <(E-Mail Removed)> wrote:
> Cross/multi posted to alt.linux.slakware and comp.os.linux.networking.
> Not posted to alt.os.linux.slackware because there are already plenty
> of a-holes in my life.
>
> I wish to "demand" my old IP from my ISP when obtaining an IP. If the
> IP I want has not already been assigned, then my DHCP client should
> insist on what I specify, giving up only after many (hopefully a
> configurable number of) refusals.
>
> A google search turns up a dhclient.conf that does this, but nothing
> with respect to dhcpcd.
>
> 1) Slackware 10.0 uses dhcpcd. There must be a pretty compelling
> reason to use it rather than dhclient. Why?
> 2) With dhcpcd, all my attempts to write a command line that
> accomplishes my objective fail. What is the correct syntax?
> 3) Are there any "gotchas" in dhclient similar to those in dhcpcd?
> dhcpcd replaces resolv.conf and ntp.conf when the IP is assigned
> unless -N -R are specified.
> 4) Please advise me: Is it a good idea to switch from dhcpcd to
> dhclient?
> 5) dhcpcd runs dhcpcd.exe. Does dhclient cause anything else to run?
> --
> buck
I switched from dhcpcd to dhclient because it works better with my DSL
modem's implemtation of DHCP. With dhcpcd, if I didn't release the
lease, during shutdown, for example, it'd have problems re-acquiring
any addressr. Usually I'd power cycle the DSL modem. With dhclient I
have no problems, works like a charm!
dhclient's OS interface is a script /sbin/dhclient-script, you can
modify this to do just about anything you might want. Also
/etc/dhclient/dhclient-exit-hooks is called when dhclient-script is
about to return to dhclient, I use it to save various pieces of
information that dhclient has set for the connection.
The only downside of dhclient is that it's configuration is much more
complicated than dhcpcd's. Also the OMAPI/omshell feature is poorly
documented, I've never been able to get it to do anything.
Jerry
|
Similar Threads
Linear Mode
