Bug 120732 - LTC7527-DHCP Client doesn't receive address from DHCP server
Summary: LTC7527-DHCP Client doesn't receive address from DHCP server
Status: CLOSED DUPLICATE of bug 111540
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: dhcp   
(Show other bugs)
Version: 3.0
Hardware: s390 Linux
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-04-13 16:11 UTC by Helen Fischer
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 19:02:34 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 Helen Fischer 2004-04-13 16:11:28 UTC
The following has be reported by IBM LTC:  
DHCP Client doesn't receive address from DHCP server
Hardware Environment:
IBM z/990
OSA Express in QDIO mode

Software Environment:
z/VM 4.4
Linux guest running 2.4.21-11.EL or 2.4.21-12.EL (64 bit)
OSA entry in /etc/chandev.conf specifies fake_ll option

Steps to Reproduce:
1. Have a DHCP server running on either intel box or s/390 Linux 
2. From client issue : dhclient ethx (x is the interface)

Actual Results:
DHCP client times out without receiving IP address from server

Expected Results:
DHCP client would receive DHCP address.

Additional Information:

I believe in order for this scenario to work, the client has to be 
able to 
request that the server broadcast it's response back to the client.  
I do not 
see a way to pass such a request with dhclient.

Comment 1 Bob Johnson 2004-05-12 15:18:19 UTC
broadcast on internal network not possible ?

Comment 4 Jason Vas Dias 2004-08-04 22:22:03 UTC

*** This bug has been marked as a duplicate of 111540 ***

Comment 5 Red Hat Bugzilla 2006-02-21 19:02:34 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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