Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 64507 - dhcp timeout
dhcp timeout
Product: Red Hat Linux
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
: FutureFeature
: 66283 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2002-05-06 18:33 EDT by Joshua Jensen
Modified: 2014-03-16 22:27 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-28 19:45:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joshua Jensen 2002-05-06 18:33:14 EDT
Description of Problem:

When waiting for a dhcp server, a timeout of 60 seconds is too long.  Could we
get the next version of Red Hat Linux to have an /etc/sysconfig/network file
that has:



Thank you,

Comment 1 Need Real Name 2002-05-09 12:04:27 EDT
Another nice feature is a possibility to have alternative network configuration when 
DHCPc doesn't get an answer.

Best regards,

Comment 2 Elliot Lee 2002-06-20 11:43:45 EDT
I believe initscripts has some sort of alarm for dhcpcd now...
Comment 3 Elliot Lee 2002-06-20 12:53:57 EDT
*** Bug 66283 has been marked as a duplicate of this bug. ***
Comment 4 Brian "netdragon" Bober 2002-07-04 18:53:44 EDT

I altered the /sbin/ifup file to allow you to add DHCP_CLIENT_TIMEOUT to any 
ifcfg-eth* file (such as /etc/sysconfig/network-scripts/ifcfg-eth0

Can you please build this into the Redhat distribution (and possibly add this 
to the kernel for all distributions)? (I'm not entirely sure if its 100% 
correctly done, but it works for me ;-)

excerpt /sbin/ifup

if [ -n "${DYNCONFIG}" ]; then
# Brian Bober
# Hacked to add ability for DHCP_CLIENT_TIMEOUT (in seconds)
# variable to /etc/sysconfig/network-scripts/ifcfg-eth* scripts
if [ -n "${DHCP_CLIENT_TIMEOUT}" ]; then
# End Hack
if [ -n "${DHCP_HOSTNAME}" ]; then
if [ -n "${NEEDHOSTNAME}" ]; then
PUMPARGS="${PUMPARGS} --lookup-hostname"
Comment 5 Brian "netdragon" Bober 2002-10-21 01:43:30 EDT
Why hasn't anyone replied with a statement like... "I am adding this into the
new Linux Kernel"? ;-)
Comment 6 Brian "netdragon" Bober 2002-12-05 19:50:10 EST
I was actually wondering in my previous comment if it was adequate or needs 
work. I didn't mean to sound rude. I was assuming it wasn't adequate because 
no one has responded.
Comment 7 Brian "netdragon" Bober 2002-12-05 19:51:30 EST
It worked for me, but might not work 100% of the time.
Comment 8 Bill Nottingham 2002-12-09 12:52:25 EST
Can't you just add it to DHCPCDARGS (or the equivalent for your client of choice?)
It inherits any *ARGS settings from the environment.
Comment 9 Joshua Jensen 2003-01-03 12:52:28 EST
Yes... it could be added to DHCPCDARGS.

But it seems like this is -such- a big complaint... that the timeout is
unbearably long when sitting in front of a booting machine.

I guess the question is:  Is it worth adding something like "DHCPTIMEOUT="30" to
ifup and /etc/sysconfig/network by default?  I would vote "yes", but I'm sure
you already have a lot on your plate.
Comment 10 Joshua Jensen 2004-06-11 19:22:43 EDT
Please close this ticket if you don't want to add the feature.
Comment 11 Bill Nottingham 2004-06-28 15:48:46 EDT
How often is this normally run into? With the link check, the only
places where it should currently time out would be where there's no
DHCP server available. I suppose a shorter return could help there,
but it should really be rare.
Comment 12 Joshua Jensen 2004-06-28 19:45:27 EDT
I agree.  Now with the link check, this isn't a problem that is all
that important to address.

Note You need to log in before you can comment on or make changes to this bug.