On 01/06/2012 03:25 AM, Per Jessen wrote:
Per Jessen wrote:
So I then issued a "/etc/init.d/network restart-all-dhcp-clients". This option did a lot more as reflected in messages, but it still didn't renew the DHCP lease. It started dhcpcd but put it in background, then dhcpcd reported "eth0 timed out". At this point it tried to "use old lease in /var/lib/dhcpcd/dhcpcd-eth0.info'", which still contained the old lease info, and proceeded to reuse the old lease without broadcasting for a new one. It must have done a broadcast, otherwise why would it report "eth0 timed out"? Following a time-out, it seems reasonable to attempt a fall-back to the previous lease. In the logs you posted, there is a 20 second span between broadcast and time-out:
Jan 5 13:47:11 ironhead dhcpcd[6530]: eth0: broadcasting for a lease Jan 5 13:47:27 ironhead ifup-dhcp: eth0 DHCP4 continues in background Jan 5 13:47:31 ironhead dhcpcd[6530]: eth0: timed out Jan 5 13:47:31 ironhead dhcpcd[6530]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info'
Is there a problem with the DHCP server? If you check the server logs, you should see a complete trace of the negotation, but I guess the server isn't responding, hence the time-out.
Ah, good point about the timeout! The network is a large one, many thousands of hosts, and I don't have access to the server logs. But I know who does and will check with him today. I'll also try the switch in the opposite direction: from the big network to the natted side of a small router. There shouldn't be a timeout issue there. Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org