You are not logged in.
Hi folks,
I am using a laptop with network manager that has worked well for quite a while. I typically use wireless but at work I have to sometimes go with the cable. Today I had a problem where I couldnt get an IP via eathernet. After some lont troubleshooting, I came up with:
dhcpcd --debug eth1
dhcpcd: version 5.1.4 starting
dhcpcd: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason PREINIT
dhcpcd: eth1: executing `/usr/lib/dhcpcd/dhcpcd-run-hooks', reason CARRIER
dhcpcd: eth1: reading lease `/var/lib/dhcpcd/dhcpcd-eth1.lease'
dhcpcd: eth1: broadcasting for a lease
dhcpcd: eth1: sending DHCP_DISCOVER (xid 0xa30f717), next in 3.38 seconds
dhcpcd: eth1: sending DHCP_DISCOVER (xid 0xa30f717), next in 8.56 seconds
dhcpcd: eth1: sending DHCP_DISCOVER (xid 0xa30f717), next in 16.82 seconds
dhcpcd: eth1: wrong xid 0x2f778173 (expecting 0xa30f717) from xxx.xxx.xxx.xxx
dhcpcd: eth1: sending DHCP_DISCOVER (xid 0xa30f717), next in 32.71 seconds
dhcpcd: timed outI then removed the lease file for eth1 and dhcpcd worked. Any reason I would have had a problem like this? Bug maybe?
-Shawn
Offline
Hi,
It must be the same issue as there : http://bbs.archlinux.org/viewtopic.php?pid=688286 ; http://bugs.archlinux.org/task/17838
Offline
Ya, it may be. I had timeout problem too. Don't see in the bugreport the same mesage reguarding the lease file though. Seems like the lease file must be removed or over written once the lease has expired or comes from a different dhcp server. Dosen't seem to be the case for me though.
-Shawn
Offline
It really seems to be the same problem. I just had another "timed out" with dhcpcd and removing the lease file worked for me too.
Offline
I had the same problem since the update to dhcpcd 5.1.4-1.
The really annoying thing is that I have to delete the lease file every time I restart.
Offline
I think I've got the exact same problem. Simply removing the lease (rm'ing the file) seems to work. Version is 5.2.5-1.
Offline