Hi i just would like to know what the option really does and what not. The reason i ask is that i would like to keep hostname and ip from the network boot process provided by dhcp. Thus after the final installation the network configuration is static and does not depends on dhcp any more.
Also i would like to know if this function will keep ALL network configuration ( dsn server, gateway and what soever ) or can the autoinst.xml have still some network options.
Some example are appreciated
tia and have a nice weekend Hajo
============================ Hans-Joachim Ehlers UNIX Systems Engineer EUMETSAT Am Kavalleriesand, 31 64295, Darmstadt, Germany Tel : +49 6151 807-7307 mailto:hansjoachim.ehlers@eumetsat.int http://www.eumetsat.int
On Friday 22 February 2008, Hans-Joachim Ehlers wrote:
i just would like to know what the option really does and what not. The reason i ask is that i would like to keep hostname and ip from the network boot process provided by dhcp. Thus after the final installation the network configuration is static and does not depends on dhcp any more.
the config will not change from DHCP to static configuration. If you had DHCP during installation, DHCP it is in the running system too. If you had static configuration, then a static NIC configuration will be done.
Also i would like to know if this function will keep ALL network configuration ( dsn server, gateway and what soever ) or can the autoinst.xml have still some network options.
mixing <keep_network...> with "real" XML network configuration for the same interface is not defined. Maybe it works, maybe not.
Uwe Gansert wrote
On Friday 22 February 2008, Hans-Joachim Ehlers wrote:
i just would like to know what the option really does and what not. The reason i ask is that i would like to keep hostname and ip from the network boot process provided by dhcp. Thus after the final installation the network configuration is static and does not depends on dhcp any more.
the config will not change from DHCP to static configuration. If you had DHCP during installation, DHCP it is in the running system too. If you had static configuration, then a static NIC configuration will be done.
But you should be able to fetch all the information easily from /var/lib/dhcpcd/dhcpcd-eth0.info and creating a static ifcfg-eth0 from it will be as easy as possible. An ifcfg files looks like
BOOTPROTO='static' STARTMODE='onboot' IPADDR='x.x.x.30' NETMASK='255.255.255.0' NETWORK='x.x.x.0' BROADCAST='x.x.x.255'
And /var/lib/dhcpcd/dhcpcd-eth0.info shows: IPADDR=x.x.x.30 NETMASK=255.255.255.0 NETWORK=x.x.x.0 BROADCAST=x.x.x.255
and also all information about DNS, gateway etc. it got from dhcp. Just a few lines of a post-script to create resolv.conf, routes and ifcfg-eth0 before the host reboots :-)
cu, Frank
autoinstall@lists.opensuse.org
-
Frank Steiner -
Hans-Joachim Ehlers -
Uwe Gansert