Arch Linux

Maos

Member

Registered: 2006-11-09

Posts: 46

problem with dhcpcd

Hi!

After upgrading dhcpcd from 1.3.22pl4-4.2 to 3.0.17-1 in Arch64 my network doesn't work...
When starting up I just get a "FAIL" for network in the daemon list at startup.

Now I have tested with both version of the package by doing "./dhcpcd eth0 -d -d" in /usr/sbin and in a directory where I have the old version extracted.

When doing it for dhcpcd in 1.3.22pl4-4.2 I get:
In console:
dhcpcd: MAC address = 00:13:d4:3e:e7:be
dhcpcd: your IP address = 83.209.35.6

And in everything.log:
Apr 22 21:28:57 rincewind dhcpcd[6525]: broadcasting DHCP_REQUEST for 83.209.35.6
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpServerIdentifier option is missing in DHCP server response. Assuming 172.16.16.1
Apr 22 21:28:57 rincewind dhcpcd[6525]: dns option is missing in DHCP server response. Assuming 172.16.16.1
Apr 22 21:28:57 rincewind dhcpcd[6525]: subnetMask option is missing in DHCP server response. Assuming 255.0.0.0
Apr 22 21:28:57 rincewind dhcpcd[6525]: broadcastAddr option is missing in DHCP server response. Assuming 0.255.255.255
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpIPaddrLeaseTime option is missing in DHCP server response. Assuming 4294967295 sec
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpT1value is missing in DHCP server response. Assuming 2147483647 sec
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpT2value is missing in DHCP server response. Assuming 3758096383 sec
Apr 22 21:28:57 rincewind dhcpcd[6525]: DHCP_NAK server response received
Apr 22 21:28:57 rincewind dhcpcd[6525]: broadcasting DHCP_DISCOVER
Apr 22 21:28:57 rincewind dhcpcd[6525]: broadcastAddr option is missing in DHCP server response. Assuming 83.209.35.255
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpIPaddrLeaseTime=3600 in DHCP server response.
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpT1value is missing in DHCP server response. Assuming 1800 sec
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpT2value is missing in DHCP server response. Assuming 3150 sec
Apr 22 21:28:57 rincewind dhcpcd[6525]: DHCP_OFFER received from  (83.209.34.1)
Apr 22 21:28:57 rincewind dhcpcd[6525]: broadcasting DHCP_REQUEST for 83.209.35.6
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpIPaddrLeaseTime=3600 in DHCP server response.
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpT1value is missing in DHCP server response. Assuming 1800 sec
Apr 22 21:28:57 rincewind dhcpcd[6525]: dhcpT2value is missing in DHCP server response. Assuming 3150 sec
Apr 22 21:28:57 rincewind dhcpcd[6525]: DHCP_ACK received from  (83.209.34.1)

And for 3.0.17-1:
console:
Info, eth0: dhcpcd 3.0.17 starting
Info, eth0: hardware address = 00:13:d4:3e:e7:be
Info, eth0: broadcasting for a lease
Debug, eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Debug, eth0: waiting on select for 20 seconds
Debug, eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Debug, eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Debug, eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Debug, eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Debug, eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Debug, eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Error, eth0: timed out
Info, eth0: exiting

everything.log:
Apr 22 21:26:51 rincewind dhcpcd[6524]: eth0: dhcpcd 3.0.17 starting
Apr 22 21:26:51 rincewind dhcpcd[6524]: eth0: hardware address = 00:13:d4:3e:e7:be
Apr 22 21:26:51 rincewind dhcpcd[6524]: eth0: broadcasting for a lease
Apr 22 21:26:51 rincewind dhcpcd[6524]: eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Apr 22 21:26:51 rincewind dhcpcd[6524]: eth0: waiting on select for 20 seconds
Apr 22 21:26:54 rincewind dhcpcd[6524]: eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Apr 22 21:26:57 rincewind dhcpcd[6524]: eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Apr 22 21:27:00 rincewind dhcpcd[6524]: eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Apr 22 21:27:03 rincewind dhcpcd[6524]: eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Apr 22 21:27:06 rincewind dhcpcd[6524]: eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Apr 22 21:27:09 rincewind dhcpcd[6524]: eth0: sending DHCP_DISCOVER with xid 0x481ecea4
Apr 22 21:27:11 rincewind dhcpcd[6524]: eth0: timed out
Apr 22 21:27:11 rincewind dhcpcd[6524]: eth0: exiting

Does anyone have any idea why this happen?

//Mårten

Maos

Member

Registered: 2006-11-09

Posts: 46

Re: problem with dhcpcd

I have the same problem with dhcpcd 3.0.19

[root@rincewind pacman]# dhcpcd -d eth0
Info, eth0: dhcpcd 3.0.19 starting
Info, eth0: hardware address = 00:13:d4:3e:e7:be
Info, eth0: broadcasting for a lease
Debug, eth0: sending DHCP_DISCOVER with xid 0x688aa0dc
Debug, eth0: waiting on select for 20 seconds
Debug, eth0: sending DHCP_DISCOVER with xid 0x688aa0dc
Debug, eth0: sending DHCP_DISCOVER with xid 0x688aa0dc
Debug, eth0: sending DHCP_DISCOVER with xid 0x688aa0dc
Debug, eth0: sending DHCP_DISCOVER with xid 0x688aa0dc
Debug, eth0: sending DHCP_DISCOVER with xid 0x688aa0dc
Debug, eth0: sending DHCP_DISCOVER with xid 0x688aa0dc
Error, eth0: timed out
Info, eth0: exiting

Noone who know why this happen?

//Mårten

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: problem with dhcpcd

Sorry, no idea. I suggest you file a bug report in flyspray : http://bugs.archlinux.org/

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

Maos

Member

Registered: 2006-11-09

Posts: 46

Re: problem with dhcpcd

ok thanks for the suggestion... Don't know why I didn't think of that...

//Mårten