rc.inet1 and a DHCP address

ve1drg · 11-11-2006, 08:48 AM

I am wondering if there is a way to have Slackware know when it picks up its DHCP address and if not for it to try again. Or at least to keep trying until it gets one.

I have had to put a 'sleep' statement in the rc.inet1.conf file to get the system to slow down when booting up. Otherwise it goes right by / misses getting the DHCP address.

I am wondering if somehow I adjusted the rc.inet1 config file such that it would do a check to see if it actually got the address and if not to say it was trying again until it either failed or was successful. And if it failed a message to that effect would pop up.

So, is there a statement I can add to that rc.inet1 config file that would tell slackware to check to see it actually had optained the dhcp address or not?

PS: When I notice that it misses picking up the dhcp address I go and rerun the rc.inet1 file. I do ./rc.inet1 stop and than ./rc.inet1 start. That usually gets the address for me. Why can't Slackware do something like this??

bsdunix · 11-11-2006, 01:16 PM

Look at your /etc/rc.d/rc.inet1 file for this line:

Code:

/sbin/dhcpcd -d -t ${DHCP_TIMEOUT[$i]:-60} ${DHCP_OPTIONS} ${1}

Notice the "${DHCP_TIMEOUT[$i]:-60}" entry.

Look at

Code:

# man dhcpcd

for the "-t <timeout>" option. Here's the part you probably want:

"... Setting the timeout to zero disables it: dhcp will keep trying forever to get a lease, and if the lease is lost, it will try forever to get another."

I haven't tried if it works, so it would be nice if you post back with your results.

Good luck.

ve1drg · 11-11-2006, 05:19 PM

Quote:

Originally Posted by bsdunix

Look at your /etc/rc.d/rc.inet1 file for this line:

Code:

/sbin/dhcpcd -d -t ${DHCP_TIMEOUT[$i]:-60} ${DHCP_OPTIONS} ${1}

Notice the "${DHCP_TIMEOUT[$i]:-60}" entry.

Look at

Code:

# man dhcpcd

for the "-t <timeout>" option. Here's the part you probably want:

"... Setting the timeout to zero disables it: dhcp will keep trying forever to get a lease, and if the lease is lost, it will try forever to get another."

I haven't tried if it works, so it would be nice if you post back with your results.

Good luck.

I believe that did the trick. I amended my rc.inet1 file to show '0' for the time and rebooted the system a couple of times and in every case the system waited at the point where it was looking for a DHCP address until it received one.

I will keep an eye on this but now with no 'sleep' statements in place, the boot-up process stops at the DHCP point and moves on after it gets the ip address. Seems like this change fixes my problem.

Thanks...