I have a subnet at home using DHCP. Everything connects wireless except my linux box which is hardwired on eth0 (the only one). I have never needed to configure anything and it always works fine.

The other day I suffered a couple power outages and now it won't connect. It just times out waiting for a response from the server.

I put a different machine (Windoze) on the hardline and it obtained an IP and connected no problem.

The light on the NIC and the light on the modem are on to indicate there is traffic on the wire.

Running ethtool gives me all the info on my adapter including "Link detected: yes."

I modified my syslog to send output to /var/log/dhcpcd.log.

It might be worth noting that it was trying to renew x.x.x.4, when it's last known address was x.x.x.5, so fearing it might be some kind of caching issue as a result of a cold boot I emptied resolv.conf and removed the .cache and .info files from /etc/dhcpc.

That didn't do anything except stop from trying to obtain it's old IP. It only sends DHCP_DISCOVER and times out waiting for the response.

One time just now as I write this, it got a DHCP_OFFER from a DHCP_DISCOVER, but then timed out on the DHCP_REQUEST. Now it's back to normal again.

Any ideas?

Slackware 12
Kernel 2.6
Pentium III i686

couple of updates that might help you help me...

I don't know if this mattered or not, but I started passing the device location (eth0) as an argument to dhcpcd. That is when I got my first nibble from the modem as I eluded to in my original post.

I just ran it again and actually got an ack from the modem. So my resolv.conf and dhcpcd-eth0.* files were all regenerated.

But I can't ping anything and none of my other machines can see it.

thanks,
the ofb

all this random behavior, and a comment in another thread tells me that maybe the LAN adapter his kicking the bucket.

I've decided to go wireless and started a new thread:
http://www.linuxquestions.org/questi...rapper-670030/