[SOLVED] dhcpcd: timed out

merdin · 2011-02-24 22:10:38

Hello! It happend after upgrading of kernel... So I did the opposite, but result is the same

Last edited by merdin (2011-03-07 08:58:23)

ewaller · 2011-02-24 22:15:53

Can you provide some more data?

Wired or wireless?
output of:

lspci
ifconfig -a

If wireless, also the output of
iwconfig

merdin · 2011-02-24 22:37:39

Yes, of course

Wired.

[root@arch disk-1]# lspci
00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 12)
00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 12)
00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06)
00:1a.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 06)
00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 06)
00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 06)
00:1c.2 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 (rev 06)
00:1c.3 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 4 (rev 06)
00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 06)
00:1c.5 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 (rev 06)
00:1d.0 USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 06)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a6)
00:1f.0 ISA bridge: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller (rev 06)
00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 06)
00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 06)
01:00.0 VGA compatible controller: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series]
01:00.1 Audio device: ATI Technologies Inc RV710/730
03:00.0 Network controller: Intel Corporation Centrino Wireless-N 1000
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 03)
ff:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02)
ff:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02)
ff:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02)
ff:02.1 Host bridge: Intel Corporation Core Processor QPI Physical 0 (rev 02)
ff:02.2 Host bridge: Intel Corporation Core Processor Reserved (rev 02)
ff:02.3 Host bridge: Intel Corporation Core Processor Reserved (rev 02)

And also...

[root@arch disk-1]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:22:15:F9:8A:0D  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:1460 (1.4 Kb)
          Interrupt:41 Base address:0xa000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:500 (500.0 b)  TX bytes:500 (500.0 b)

wlan0     Link encap:Ethernet  HWaddr 00:26:C7:2D:92:DE  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

ewaller · 2011-02-24 22:55:38

Well, that all looks pretty reasonable. It even appears that you have managed to send some packets which probably makes moot my next question -- but I'll ask anyway...

Did you check the cables?

You would not believe how often gurus and rookies alike get caught by loose cables.

What is at the other end of the cable? If it is a local router, DSL Modem, etc, does the activity light on that device indicate a connection?
Does your NIC connection have an activity / connection indicator? Does it light?

Is the router or modem under your control, or do administration rights belong to someone else.
If you can log in to the administration page of your router / modem, does it know about your MAC address (shown above, in the ifconfig output -- you may want to go obfuscate that) ?

merdin · 2011-02-24 23:12:42

I use DSL modem. In Windows everything is fine . But in Arch i changed MAC by ifconfig eth0 down/ hw ether/ up and then ran dhcpcd... It worked for many months

Well, my modem detects everything correctly.

Last edited by merdin (2011-02-24 23:17:10)

merdin · 2011-02-26 20:06:24

Someone, please, help me!

whatshisname · 2011-02-26 22:52:16

merdin wrote:

Someone, please, help me!

Have you tried "dhclient" instead of "dhcpcd"?

Have you checked the wiki?

https://wiki.archlinux.org/index.php/Network

I had similar problems with my wireless interface on my laptop. The final solution for me was removing network manager:

https://bbs.archlinux.org/viewtopic.php?id=107609

merdin · 2011-02-27 16:37:39

Amazing, but sometimes, after booting, dhcpcd works!!! But sometimes....
I do not use networkmanager at all. Dhclient can not save my nerve too... I need my magic tambourine...

whatshisname · 2011-02-27 18:01:19

merdin wrote:

Amazing, but sometimes, after booting, dhcpcd works!!! But sometimes....
I do not use networkmanager at all. Dhclient can not save my nerve too... I need my magic tambourine...

OK. I just noticed you have a wireless interface as well as a wired one. When I first installed Arch this past summer on my laptop, my network interfaces would jump around. I think it's a Udev thing. Since I was always wireless with my laptop, I didn't pay attention to how the wired interface acted. But it might be worth your time to try to give all your network interfaces persistent names:

https://wiki.archlinux.org/index.php/Co … es_varying

I bring this up because you say "sometimes, after booting, hdcpcd works". That could mean "sometimes" your computer thinks your primary network card is eth0 and "sometimes" it thinks it's eth1.

Also, just happened to see this below the wiki link I posted above:

Realtek no link / WOL issue
Users with Realtek 8168 8169 8101 8111(C) based NICs (cards / and on-board) may notice an issue where the NIC seems to be disabled on boot and has no Link light. This can usually be found on a dual boot system where Windows is also installed. It seems that using the offical Realtek drivers (dated anything after May 2007) under Windows is the cause. These newer drivers disable the Wake-On-LAN feature by disabling the NIC at Windows shutdown time, where it will remain disabled until the next time Windows boots. You will be able to notice if this issue is affecting you if the Link light remains off until Windows boots up; during Windows shutdown the Link light will switch off. Normal operation should be that the link light is always on as long as the system is on, even during POST. This issue will also affect other operative systems without newer drivers (eg. Live CDs). Here are a few fixes for this issue:

Earlier I noticed you have a Realtek 8168b card. And you said Windows works fine so you must have a dual-boot system.

They talk about fixes here:

https://wiki.archlinux.org/index.php/Co … _WOL_issue

Might be worth taking a look at both of these issues, one at a time, though.

Good luck.

merdin · 2011-02-27 20:41:51

Thank you, whatshisname

But i use x86_64. And do you think it's possible even if i always run dhcpcd with my own script(MAC changing, dhcpcd eth0) with eth0 as parameter?

Last edited by merdin (2011-02-27 20:43:26)

merdin · 2011-02-27 20:55:21

[root@arch disk-1]# cosmosTV 
dhcpcd[3028]: version 5.2.10 starting
dhcpcd[3028]: eth0: rebinding lease of 10.11.12.103
dhcpcd[3028]: eth0: broadcasting for a lease
dhcpcd[3028]: timed out

davidm · 2011-02-27 21:44:00

merdin wrote:

Amazing, but sometimes, after booting, dhcpcd works!!! But sometimes....
I do not use networkmanager at all. Dhclient can not save my nerve too... I need my magic tambourine...

It's really strange then since this seems to be for a wired connection but I wonder if changing DHCP_TIMEOUT to 60 seconds instead of the default 30 seconds (which should usually be way more than enough for the average wired connection) might help get around it. That it happens randomly is indicative of it probably not being a simple configuration problem, or if so, something with a bit of a fuzzy component to it.

Last edited by davidm (2011-02-27 21:45:34)

whatshisname · 2011-02-28 23:16:01

merdin wrote:

Thank you, whatshisname
But i use x86_64. And do you think it's possible even if i always run dhcpcd with my own script(MAC changing, dhcpcd eth0) with eth0 as parameter?

Merdin, please understand, I'm no expert. But I did have a helluva time getting my laptop to reliably connect to the Internet this summer and I went down several dead end paths trying to get it fixed. So while everything I say comes from my own experience, it often comes with not a lot of understanding behind it. :-)

As for your question above, I'm not sure what you're asking.

But *if* you're having a wandering interface problem, if "dhcpcd eth0" doesn't work and the interface it switches to is "eth1" then "dhcpcd eth1" *should* work. If it doesn't, then you have other problems. Good ol "ifconfig" will always tell you what interfaces your computer is recognizing at the moment.

Generally speaking, though, when I find myself in the snag you're in, I keep mucking around with the command-line tools until I find something that works. Having said that, I can see you're a command-line kindaguy already so probably all of my advice so far has been stuff you've already tried.

Wish I could tell you what to try next but I'm probably at the end of my "expertise" at this juncture. I'm sure someone else will jump in and help you soon, though. There are plenty of knowledgeable folks hanging around here.

merdin · 2011-03-06 11:16:25

Awesome!!! I put my script in /etc/rc.local and everything works now, after booting! But after releasing and rerunning dhcpcd again shows "timed out".

Last edited by merdin (2011-03-06 19:55:21)

whatshisname · 2011-03-06 19:21:50

merdin wrote:

Awesome!!! I put my script in /etc/rc.local and everything works now! But after releasing and rerunning dhcpcd again shows "timed out"

What command do you run to "release" and what is your dhcpcd command to reconnect?

Last edited by whatshisname (2011-03-06 19:25:40)

skunktrader · 2011-03-06 19:31:25

man dhcpcd

merdin · 2011-03-06 20:38:55

whatshisname wrote:

merdin wrote:
Awesome!!! I put my script in /etc/rc.local and everything works now! But after releasing and rerunning dhcpcd again shows "timed out"
What command do you run to "release" and what is your dhcpcd command to reconnect?

dhcpcd -k eth0
dhcpcd -d eth0

merdin · 2011-03-07 08:44:42

Thanks to All!
I use

 /etc/rc.d/network start

instead of

 dhcpcd -d eth0

...
To reconnect, after the cable plugged out, then in -

 /etc/rc.d/network restart

.
It works!!! For me, at least.

Last edited by merdin (2011-03-07 08:47:00)

Arch Linux

#1 2011-02-24 22:10:38

[SOLVED] dhcpcd: timed out

#2 2011-02-24 22:15:53

Re: [SOLVED] dhcpcd: timed out

#3 2011-02-24 22:37:39

Re: [SOLVED] dhcpcd: timed out

#4 2011-02-24 22:55:38

Re: [SOLVED] dhcpcd: timed out

#5 2011-02-24 23:12:42

Re: [SOLVED] dhcpcd: timed out

#6 2011-02-26 20:06:24

Re: [SOLVED] dhcpcd: timed out

#7 2011-02-26 22:52:16

Re: [SOLVED] dhcpcd: timed out

#8 2011-02-27 16:37:39

Re: [SOLVED] dhcpcd: timed out

#9 2011-02-27 18:01:19

Re: [SOLVED] dhcpcd: timed out

#10 2011-02-27 20:41:51

Re: [SOLVED] dhcpcd: timed out

#11 2011-02-27 20:55:21

Re: [SOLVED] dhcpcd: timed out

#12 2011-02-27 21:44:00

Re: [SOLVED] dhcpcd: timed out

#13 2011-02-28 23:16:01

Re: [SOLVED] dhcpcd: timed out

#14 2011-03-06 11:16:25

Re: [SOLVED] dhcpcd: timed out

#15 2011-03-06 19:21:50

Re: [SOLVED] dhcpcd: timed out

#16 2011-03-06 19:31:25

Re: [SOLVED] dhcpcd: timed out

#17 2011-03-06 20:38:55

Re: [SOLVED] dhcpcd: timed out

#18 2011-03-07 08:44:42

Re: [SOLVED] dhcpcd: timed out

Board footer