Red Hat Bugzilla – Bug 192
kickstart with bootp doesn't config static network
Last modified: 2008-05-01 11:37:48 EDT
I'm using a BOOTP server to obtain the network info for
a client doing a kickstart. The client obtains the
kickstart file just fine, reads everything in, NFS-mounts up
the RedHat5.2 distribution over NFS, and proceeds with the
installation. Even though I'm specifying a "network
--bootproto static ..." line in my kickstart client config
file, the machines comes up after the install and contacts
the BOOTP server once again to obtain its networking
I'm having to manually configure the following files in the
post-installation section to get around this bug:
The interesting thing is if I take the exact same kickstart
config file and copy it onto the bootdisk, and do a "linux
ks=floppy" the networking is configured correctly.
It appears that the kickstart installation program is making
the incorrect assumption that If I'm using a BOOTP server
during the install phase, that I will always want to use a
BOOTP server to obtain network config info. We should be
able to use a BOOTP server to do obtain a clients network
configuration (so that we can install the distribution over
NFS) and configure networking statically so that upon reboot
the machine can boot up without BOOTP.
I can provide you with my kickstart config file and bootptab
file if that helps.
I have verified this to be a bug. This is being assigned to a
Matt? Any progress on this one?
*** Bug 3920 has been marked as a duplicate of this bug. ***
Using the following kickstart file, after installation of
all packages, during the network configuraion step, the
install cannot do a reverse name lookup to determine the
host and domain name. Upon further inspection the network
device driver is being installed and eth0 exists, but is not
--------- begin ks.cfg ----------
device ethernet 3c59x
network --bootproto static --ip 192.168.73.7 --netmask
255.255.255.0 --gateway 192.168.73.254 --nameserver
# part <mntpt> --size <size in megs> [--grow] [--maxsize
<size in megs>]
part / --size 250
part swap --size 64
part /usr --size 800 --grow --maxsize 1200
part /var --size 500 --grow --maxsize 800
part /tmp --size 100 --grow --maxsize 800
xconfig --monitor "Generic08"
auth --useshadow --enablemd5
lilo --location mbr
# '@ component' may be used to include entire components
@ Printer Support
@ DOS/Windows Connectivity
@ SMB (Samba) Connectivity
@ DNS Name Server
@ Network Management Workstation
@ C Development
@ Development Libraries
@ C++ Development
@ Extra Documentation
--------- end ks.cfg ----------
------- Additional Comments From firstname.lastname@example.org 07/06/99 15:51 -------
One thing that might be causing what you are seeing is the fact that
it appears as if the network line of the config file is not on one
single line. It has to be on the same line in order for the install
to process it. As it is (where it appears to be on different lines)
the nameserver is not getting set and therefore no name lookup!
Reopen this bug if you still have problems after modifying this.
------- Additional Comments From Marty.Trey@MED.VA.GOV 07/07/99 06:52 -------
The network directive is on one single line.
*** Bug 2724 has been marked as a duplicate of this bug. ***
When doing a kickstart install, using a DHCP/NFS combination
for the install, if the kickstart file specifies network
--bootproto static in the config file, the installer fails
to change the ethernet config from BOOTP/DHCP to static.
Relevant bits of the kickstart file follows:
network --bootproto static --ip 220.127.116.11 --netmask
255.255.255.0 --gateway 18.104.22.168 --nameserver
(all on one line, of course)
After a reboot, you will notice that the
/etc/sysconfig/network-scripts/ifcfg-eth0 files have failed
to change to static from BOOTP/DHCP.
This is fixed in the latest installer (available in beta)