If I understand all this correctly. Your router box is getting the IP
address from RR and keeping it for itself. This is correct. It is
masquerading all of the local boxes and they get private IP addresses,
192.169.x.x via DHCP. There isn't really a good reason not to give them
infinite leases. The dynamic IP address is negotiated between RR and
the router box and you never see it. The router is acting as both a
DHCP client as far as RR is concerned, and a DHCP server as far as the
boxes on your LAN. This is all correct.
You may wish to configure your DHCP client to not change the host name
and accept infinite leases. Other than that I don't see anything
obvious that's a problem.
Jeffrey
Quoting Joshua Trutwin
Gladly!
I have my SuSE box connected to a hardware router, which in turn is connected to a cable modem. From what I can tell about the router's configuration, it is set up as the DHCP server. The dhclient program has been running since day 1, it was configured as part of the SuSE installation and this error has always shown up, though it did not seem to present any problems to access to the Internet/LAN. The dhclient script is the program that raises the dhcpcd errors, that is the only script in /etc/init.d related to DHCP. When all is said and done, neither are running (ps -deaf | grep dh). If I try to reboot without running dhclient, network access is hosed, so it must be doing something important. I do not need an infinite IP lease as my cable provider (RoadRunner) uses dynamic IP address assignment.
Does that help or is there something else I can provide?
Josh
-- I don't do Windows and I don't come to work before nine. -- Johnny Paycheck