Server Down - How should Client Act?
David W. Hankins
David_Hankins at isc.org
Mon May 1 19:01:05 UTC 2006
On Mon, May 01, 2006 at 11:37:05AM -0700, Ted Lemon wrote:
> Of course, but that's not the point. The point is, does it keep trying DHCP,
> or just stay with link-local forever?
My understanding is that dhcpcd exits and is not restarted until
ifdown/ifup, but my understanding is flawed by not being first hand.
Literally, /etc/rc.d/ifup calls dhcpcd (via some /sbin script), it fails
and exits, the script detects this exit and elects to link-local address
the interface. When it exits, nothing is left running that knows to
try DHCP at all.
That's the story I heard anyway.
I also thought I remembered having a ticket on dhcp-bugs at isc.org that
described a Windows variety of client (95 or something like that)
which refused to do DHCP after selecting link-local. But my attempts
at searching the database are giving me too many false positives to
even attempt to look for it further.
But back to the point about linux, for it to work we need dhcp client
software to learn how to do link local themselves (so they stay operating
and keep looking for a server), if lilnk local is to be used at all.
David W. Hankins "If you don't do it right the first time,
Software Engineer you'll just have to do it again."
Internet Systems Consortium, Inc. -- Jack T. Hankins
More information about the dhcp-users