Bug 426301

Summary: network installation with dhcp client looses ip configuration after first boot
Product: [openSUSE] openSUSE 11.0 Reporter: Diego Ercolani <diego.ercolani>
Component: InstallationAssignee: E-mail List <bnc-team-screening>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: x86   
OS: openSUSE 11.0   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Diego Ercolani 2008-09-15 13:30:11 UTC
Hallo,
I have a network configuration that need mandatory use of proxy, so, when I want to install OpenSuSE, I send a peculiary cmdline in pxe configuration:


label install
        kernel linux
        append initrd=initrd splash=silent showopts install=http://download.opensuse.org/distribution/11.0/repo/oss proxy=http://192.168.21.253:3128 dhcpcd=-G netsetup=dhcp gateway=192.168.21.253 ipv4only=1 kexec=1 Keytable=it Language=it_IT nomdns=1

As written in http://en.opensuse.org/Linuxrc, I pass the installation repository, the proxy address and the gateway using dhcp

When Yast installation procedure makes the first boot for authomatic configuration, it popups an error message saying that Network is unreacheable "Failed to connect to 192.168.21.253: Network is unreacheable"

Switching to console and typing ifconfig shows that only loopback device is up.
if you type ifup eth0, eth0 will be configured and then switching back to yast, clicking retry you can continue installation procedure.
Comment 1 Diego Ercolani 2008-09-15 13:33:44 UTC
Additional comment:
with ifup eth0 ethernet 0 goes configured as dhcp client but without the exception to the default gateway as asked by the original commandline:
dhcpcd=-G netsetup=dhcp gateway=192.168.21.253

The network card simply gets and apply ALL the parameters sent by dhcp server.



Comment 2 Michal Zugec 2008-09-15 16:01:58 UTC
yes, this is known issue already fixed in 11.1 (for 11.0 we can't fix for installation and later doesn't make sense)

*** This bug has been marked as a duplicate of bug 399645 ***
Comment 3 Michal Zugec 2008-09-15 16:02:30 UTC
as workaround "rcnetwork restart" should be enough