Bug 41029 - redhat 7.1 DHCP/PUMP times out for getting IP address from DHCP server
Summary: redhat 7.1 DHCP/PUMP times out for getting IP address from DHCP server
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: pump   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Elliot Lee
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2001-05-16 23:35 UTC by moo kim
Modified: 2005-10-31 22:00 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-06-28 16:50:06 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description moo kim 2001-05-16 23:35:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.74 [en] (WinNT; U)

Description of problem:
I was running redhat 7.0 on the network via DHCP client.   Then I freshly installed the redhat7.1
and networking no longer works.    PUMP basically gets the timed out message in the /var/log.
I contacted the RedHat technical support and he suggested me to use the static address
(192.xx.xx.xx) to verify that the network card is functional or not.   With the static IP address
via netconfig utility, "ifup eth0" command worked fine and I was able to ping the dummy static
IP address with no problem.    So it must be something not working with PUMP.

Then I downgraded the PUMP RPM from 7.1 to 7.0 (0.8.11 to 0.8.3) and I am still
getting the "dhcpd: timed out..." message in the log file.    My NIC card is Digital DS21140.

Any suggestion or help would appreciate it.   I might have to go back to redhat 7.0 if
there is work-around to this problem.

How reproducible:

Steps to Reproduce:
1. After install the redhat 7.1, reboot

Actual Results:  There is a long timeout for eth0 network during boot time and "dhcpd: timed out" message
in the log file.  

Expected Results:  Get the IP address from the DHCP server and enable the networking.

Additional info:

Comment 1 Tru Huynh 2001-07-30 16:52:32 UTC
I have the same behaviour here.

The only thing is that the dhclient v3.0rc10 from ISC can 
manage to retrieve the dhcp config.



Comment 2 Elliot Lee 2001-08-26 21:01:12 UTC
Sorry for the delay.

I don't have any clues on what the problem is right now, but it would be helpful
to know if anyone out there is still experiencing this problem with the 2nd
Roswell beta.

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