dhcpcd fails a lot

Dethredic · 2009-09-12 14:46:27

So I don't know if this is an Arch problem or a shitty cable, but 95% of the time when I try to start my network dhcpcd times out. I then try to start it manually several times after wiggling my cable around and after about 5 or 10 tries it finally picks up an IP. ethtool always says that I have a link and the light by the port is always on.

kjon · 2009-09-12 15:56:00

what's your nic? does dmesg show you something like 'Interrupt #(number) lost' or 'Interrupt #(number) ignored'?
And why don't you start checking the issue by it's most obvious solution? If you suspect of the cable... why don't you try another?

Dethredic · 2009-09-15 16:32:16

"dmesg | grep Interrupt" returned:

ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P2._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P8._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P9._PRT]
ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT]
ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 *11 12 14 15)
ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 10 11 12 14 *15)
ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 *5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 *14 15)
ACPI: PCI Interrupt Link [LNKG] (IRQs *3 4 5 6 7 10 11 12 14 15)
ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 *7 10 11 12 14 15)

I don't own another cable, I would have to go out and get one so it is not a preferable option. I didn't used to have this problem. It would happen once a month or something, but not everyday.

Last edited by Dethredic (2009-09-15 16:38:17)

Dethredic · 2009-09-16 11:38:20

anyone?

DarksideEE7 · 2009-09-19 04:21:02

Dethredic wrote:

anyone?

It may be worth trying to increase the timeout length in dhcpcd.conf. From the man on dhcpcd.conf:

timeout seconds
The default timeout for waiting for a DHCP response is 30 seconds which may be too long or too short and can
be changed here.

I seriously doubt that your DHCP server needs more than 30s to resolve an IP, but I suppose if you need to workaround faulty connections then this may help.

kjon · 2009-09-20 00:12:03

Sorry I couldn't answer before. I have been very busy.

I don't know what might be your problem. Probably a faulty router/gateway/modem/whatsoever. I've a dlink flashed with ddwrt and when I have dhcp issues, I just reset it. That's all.

p.s. I insist, you didn't provide your network card brand.

Dethredic · 2009-09-21 13:51:44

Sorry, I use the built in port on my P5Q motherboard. This just never happened in the last 6 months. I will get a new Ethernet cord when I go home in a week.

Last edited by Dethredic (2009-09-21 13:59:27)

Dethredic · 2009-09-26 13:45:50

anyone?

kjon · 2009-09-26 19:01:24

sorry. I've no idea...

purple12 · 2009-09-27 18:32:06

Sorta glad to know it's not just me having this issue...
I actually resorted to a twice-daily root cron job that does:
killall dhcpcd; dhcpcd eth0
--ugly fix, but seems to work.

kjon · 2009-09-27 21:53:48

if that were the case, why you don't just change the dhcp client? (pump or dhclient might be a viable alternative)

foxbunny · 2009-10-09 20:05:33

Hey, any luck with this issue? I'm having a hard time getting dhcp to pick up an IP. It works 1 out of 100.

enrique · 2009-10-10 10:30:22

I'm having problems getting a IP when connected to my office's Gigabit switch, if I'm connected to another 100mbps switch it works everytime. Also it does not matter if I use networkmanager or dhclient.

So maybe it is your switch?

toad · 2009-10-15 14:28:47

Try this:

http://wiki.archlinux.org/index.php/Con … ng_at_boot

Works for me every time

Arch Linux

#1 2009-09-12 14:46:27

dhcpcd fails a lot

#2 2009-09-12 15:56:00

Re: dhcpcd fails a lot

#3 2009-09-15 16:32:16

Re: dhcpcd fails a lot

#4 2009-09-16 11:38:20

Re: dhcpcd fails a lot

#5 2009-09-19 04:21:02

Re: dhcpcd fails a lot

#6 2009-09-20 00:12:03

Re: dhcpcd fails a lot

#7 2009-09-21 13:51:44

Re: dhcpcd fails a lot

#8 2009-09-26 13:45:50

Re: dhcpcd fails a lot

#9 2009-09-26 19:01:24

Re: dhcpcd fails a lot

#10 2009-09-27 18:32:06

Re: dhcpcd fails a lot

#11 2009-09-27 21:53:48

Re: dhcpcd fails a lot

#12 2009-10-09 20:05:33

Re: dhcpcd fails a lot

#13 2009-10-10 10:30:22

Re: dhcpcd fails a lot

#14 2009-10-15 14:28:47

Re: dhcpcd fails a lot

Board footer