On Fri, 2002-01-18 at 23:13, Ron Cordell wrote:
On Friday 18 January 2002 10:53 pm, Ron Cordell wrote:
On Friday 18 January 2002 05:06 pm, James Bliss wrote:
I am surprised that you say that dhcpd client is broken in 2.4.16. I am on a cable modem and must run my external facing NIC using the dhcpd client and it runs flawlessly since I have upgraded to the 2.4.16 kernel. Can you enlighten me on what was broken so I can check to see if I am having any problems which I have not noticed.
Thanks,
Jim
I could very well be full of &*(#... but when I updated to 2.4.16, I could no longer get an IP address using the DHCP client daemon. I did a search and found some discussion saying that the dhcpd client was broken in some cases in 2.4.16 and was fixed in 2.4.17. I can't find that thread just now, when I search again, but I haven't tried very hard...
-ronc
I just restarted the machine with DHCP instead of a fixed address. The boot log shows:
Starting service dhcp client on eth0dhcpcd[260]: broadcasting DHCP_REQUEST for 192.168.10.3
dhcpcd[260]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.10.255
dhcpcd[260]: DHCP_ACK received from mars (192.168.10.1)
dhcpcd[260]: infinite IP address lease time. Exiting
failed
However, I have an IP address, shown correctly by ipconfig. Why is DHCPD showing failed?
-ronc
I've been getting these messages on bootup with Kernels 2.4.0, 2.4.4, and 2.4.16 (all official SuSE SMP kernels), and it always tells me that the service has failed on startup....but I've never had any problem with networking. I'd suspected that it was my Netgear router (the DHCP server) since it hadn't caused any problems on the client side. - David A. Riggs