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 reset the network card to use DHCP using Yast2, at Yast2 reports a failure. However, the /var/log/messages shows the following: Jan 18 22:59:31 penguin kernel: bridge-eth0: lost peer eth0 Jan 18 22:59:31 penguin kernel: bridge-eth0: down Jan 18 22:59:42 penguin kernel: bridge-eth0: found peer eth0 Jan 18 22:59:42 penguin kernel: bridge-eth0: up Jan 18 22:59:45 penguin dhcpcd[9597]: broadcasting DHCP_REQUEST for 192.168.10.3 Jan 18 22:59:45 penguin dhcpcd[9597]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.10.255 Jan 18 22:59:45 penguin dhcpcd[9597]: DHCP_ACK received from mars (192.168.10.1) Jan 18 22:59:45 penguin dhcpcd[9597]: infinite IP address lease time. Exiting Jan 18 22:59:49 penguin kernel: bridge-eth0: lost peer eth0 Jan 18 22:59:49 penguin kernel: bridge-eth0: down Jan 18 22:59:49 penguin kernel: bridge-eth0: found peer eth0 Jan 18 22:59:49 penguin kernel: bridge-eth0: up Jan 18 22:59:52 penguin dhcpcd[9639]: broadcasting DHCP_REQUEST for 192.168.10.3 Jan 18 22:59:52 penguin dhcpcd[9639]: broadcastAddr option is missing in DHCP server response. Assuming 192.168.10.255 Jan 18 22:59:52 penguin dhcpcd[9639]: DHCP_ACK received from mars (192.168.10.1) Jan 18 22:59:52 penguin dhcpcd[9639]: infinite IP address lease time. Exiting Jan 18 22:59:53 penguin startproc: startproc: exit status of /usr/sbin/rpc.lockd: 1 Jan 18 22:59:59 penguin kernel: eth0: no IPv6 routers present Jan 18 23:00:30 penguin startproc: startproc: exit status of /usr/sbin/rpc.lockd: 1 Jan 18 23:00:35 penguin PAM-unix2[8733]: session finished for user root, service su Jan 18 23:03:24 penguin su: (to root) rcordell on /dev/pts/1 Jan 18 23:03:24 penguin PAM-unix2[10687]: session started for user root, service su So, it looks like it may be working after all? -ronc