LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware - Installation (http://www.linuxquestions.org/questions/slackware-installation-40/)
-   -   rc.inet1 (http://www.linuxquestions.org/questions/slackware-installation-40/rc-inet1-511119/)

ve1drg 12-16-2006 02:05 PM

rc.inet1
 
The rc.inet1 process seems to not always pick up my dhcp address. Things seem to load so fast that it sometimes misses picking up an ip address for me.

I took out the timer in rc.inet1 so it sits there a long(er) time but still no ip address (sometimes)....

Is there another way to make sure that an ip address is actually found before the system moves on from rc.inet1/rc.inet1.conf?? And it would be nice to see that it has found something when it stops at that point. I see nothing other than the long pause.
Than off it goes and finishes loading and sometimes there is no ip. (ugh....).

I have tried adding /etc/rc.d/rc.inet1 restart to my /etc/rc.d/rc.local file.
And that seems to work, but seems like an ugly way to get around my problem.

Does anyone have any suggestions to keep things clean but working the way slackware is supposed to work.

By the way - I read the other question posed a while back about the same problem as mine but can't seem to see a solution in there for me. At least mine works sometimes but since I am away a lot, and my machine reboots once in a while I would like it to be back on the internet whenever it does reboot. You know, when I am not here..

Thanks..

bsdunix 12-17-2006 07:24 PM

Quote:

I took out the timer in rc.inet1 so it sits there a long(er) time but still no ip address (sometimes)....
In case you haven't done so, here's some things you can do:
  • Look for bent pins on the RJ-45 female connector where your network cable plugs into your PC and hub/switch. (Bent pins cause problems)
  • Replace network cable. (Cable may have a broken wire inside)
  • Move network cable to a different port on your hub/switch. (Ports on hubs/switchs go bad)
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.)
If your home router is also a wireless access point and the wireless access is unsecured, your DHCP leases are being assigned to whatever system attaches to your access point.

odd2k 12-29-2006 11:48 AM

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.

Quote:

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..
Quote:

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:

Code:

dhcpcd -k
sleep 2      # dhcpcd needs a little time to delete the lock file, apparently.
dhpcd eth0



All times are GMT -5. The time now is 11:03 AM.