I tested both dhcp and static configuration using the "--bootproto=query" option inside the kickstart file. Both ways I end up in a dhcp ipv6 network configuration. So thats not working.
on 03/06/2013 – Made popular on 03/06/2013
I'm having 2 issues with kickstart for Fedora 19 that I don't seem to be able to resolve:
1) The hostname is NOT being set in the installation even though I DO have the --hostname listed in the kickstart file as follows:
network --bootproto=static --device=p6p1 --gateway=192.168.x.1 --hostname=slwfed005.slwdomain --ip=192.168.x.xx --nameserver=192.168.x.1 --netmask=255.255.255.0 --ipv6=auto -
I am trying to stop my kickstart CentOS install prompting me for TCP/IP information. After I click through this prompt (keeping IPv4 and IPv6 to their defaults) the installation continues and completes just fine.
i want to install a new fedora 12 system on my computer.
I have a dhcp serveur configured for PXE et a compatible client.
The client can boot via the network using the image stored on the server. The install begin, after he ask me the language and keyboard, and the next screen give me options like CD/DVD, hard drive , NFS directory and URL.
For those of us used to setting static ethernet configs in /etc/sysconfig/network-scripts, the use of "BOOTPROTO=none" in ifcfg files no longer works to set up a static interface in FC20. (The interface will fall back to dhcp.)
You need to explicitly use BOOTPROTO=static now.
I do not consider this a bug, just putting it here in case someone is searching.
I am trying to configure an installation from a centos server to a client. The server is running centos 6.5 and I have configure kickstart with dhcp and all the necessary parameters and I input the boot command at the client side and it fails to install. I am new to linux and have spent more than 20hrs trying to find a solution to no avail.