Description of problem:
When installing via FTP/HTTP in a local network ( without gateway ) the network
interface is not activated. The given IPaddress is not shown via ifconfig.
Workaround: switch to virtual console 2 and activate interface via
'ifconfig ethx IP MASK up'. --> not practicable when installing virtual machine,
as switching to virtual console seems to be difficult/not working.
Steps to Reproduce:
1. boot from CD using ' linux askmethod' , install from FTP or HTTP
2. activate network interface, provide manual IP, no gateway
3. switch to virtual console 2 ( CTRL+ALT+F2 ), type 'ifconfig'
no IP address for interface eth0 ( IPv4)
Flagging for RHEL-5.2
Created attachment 154683 [details]
This request was evaluated by Red Hat Product Management for
inclusion, but this component is not scheduled to be updated in
the current Red Hat Enterprise Linux release. This request will
be reviewed for a future Red Hat Enterprise Linux release.
Fixed in libdhcp-1.20-7.el5 and later releases.
VERIFIED with anaconda-18.104.22.168-1 / libdhcp-1.20-9.el5
Configured eth0 to use address from the local network and no gateway. Stage2 was loaded successfully, ifconfig showed the correct address on tty2 and the install was able to complete.
Release note added. If any revisions are required, please set the
"requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly.
All revisions will be proofread by the Engineering Content Services team.
libdhcp did not allow for some situations where a static network configuration was specified. Specifically, when a configuration without a DHCP server was specified during installation, the network interface was not activated. This would preclude installations through FTP and HTTP. Libdhcp now activates the interface when a static configuration is specified, even when no DHCP server is present so that network-based installations are possible.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.