Red Hat Bugzilla – Bug 115481
kickstart network flag being set to DHCP
Last modified: 2007-07-31 10:29:44 EDT
Description of problem:
In the kickstart profile I select the network option to use static IP
address and yet the kickstart configuration file, and the kickstart
advanced options showing bootproto dhcp.
The end system completes the kickstart successfully using a static IP
address and not dhcp. The anaconda-ks.cfg file shows the setting of
network to device eth0 and bootproto static.
Version-Release number of selected component (if applicable):
The Network Configuration option on the Kickstart->Options page is
used by the bootloader to determine the network configuration for the
kickstart process. The 'network' command on the advanced options page
is the one used to generate the kickstart configuration file. The
options passed to the bootloader are different from those needed by
anaconda to configure the system. It is also possible that these two
settings might be different. A user might need to kickstart a system
using eth1, but eth0 is the primary network interface for the box.
I've changed the name to 'Kickstart Network Configuration'. Better
documentation of this difference is also in order.
*** Bug 117481 has been marked as a duplicate of this bug. ***