Bug 31377 - Network Hangs when using dhcp
Summary: Network Hangs when using dhcp
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: dhcpcd   
(Show other bugs)
Version: 7.1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Elliot Lee
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2001-03-10 22:59 UTC by srambarr
Modified: 2008-05-01 15:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-09-01 13:33:40 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 srambarr 2001-03-10 22:59:01 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.0; Windows 98; DigExt)

at boot up the systen hangs at bring up eth0, I am using a cablemodem 
connection with dhcp, eth0 is a tulip card, eth1 is using eepro100

Reproducible: Always
Steps to Reproduce:
1.shut down and restart

Comment 1 Need Real Name 2001-05-02 18:18:08 UTC
Happens also with @home cable modems (although it does not hang,  it eventually 
times out).
Fixed it by modifying the ifup script to pass the hostname to pump - @home DHCP 
server expect the hostname in order to return the proper IP address.

Looking at the scripts (before mods) it appears that it should pass the 
hostname, but that doesn't seem to work.

To make matter worse,  the installer doesn't even ask for a hostname if DHCP is 

Comment 2 Need Real Name 2001-09-01 13:30:14 UTC
@home requires a hostname to assign your IP address.  This can be fixed in (at 
least) two ways, by editing ifup, which I personally think is a bit of a hack, 
or by adding the following line to /etc/sysconfig/network-scripts/ifcfg-eth0:
This parameter is passed to ifup and will satisfy @home's server.

Comment 3 Need Real Name 2001-09-01 13:33:36 UTC
Sorry about the misinformation in the previous comment, the '@home' string 
should not be included in the edit to ifcfg-eth0, correct line should be:


Comment 4 Elliot Lee 2001-09-11 00:19:36 UTC
Sounds resolved to me.

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