I have also seen a lot
of people having the same problem here, without ever finding a solution to this problem.
It's always the same, the dhcp server keeps timing out, and the dhpc client never gets an ip assigned. I've experienced this on both Slackware and Gentoo, so I don't think this has anything to do with Slackware in particular. The strange thing is, sometimes it works and sometimes it doesn't. It seems completely random.
It's definitely not a problem with the physical connection to the internet; I'm running Slackware in a virtual machine on a Windows XP host, and the host never has any problems connecting to the dhcp server.
Originally Posted by bsdunix
If this is a home system and you have a router that has the DHCP server, check:
* Maximum number of DHCP lease users. (If set to say 2 and you are the 3rd user trying to get a lease, you won't get an IP address until one of the other 2 leases expire/release.)
This really fits, seeing how the dhcp client eventually gets an ip assigned. How does this apply to cable modems? I've noticed that a lot of people with this problem, myself included, use a cable modem to connect to the internet. It it possible that the modem needs to be setup to allow more than one lease, or could it be that the actual DHCP server only allows one lease?
Hmm, on second thought, once both my host and my virtual installation of Slackware get their respective ips, both of them can connect to the internet at the same time. Meaning, that at some point there are two leases in use.
This is really strange..
Originally Posted by ve1drg
Does anyone have any suggestions to keep things clean but working the way slackware is supposed to work.
You could add the following to your rc.local, assuming your connection is named eth0:
sleep 2 # dhcpcd needs a little time to delete the lock file, apparently.