Using Kickstart to configure NICs (2)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Problem:  I can't get kickstart to recognize
and install two NICs at the same time.  I have
a working ks.cfg and even my postinstall goes
great and configures my dns, ipchains and
everything.  The only setback is that every
time after the initial installation with KS,
I have to shut down, remove one card, reboot
and have it detect the remaining one with
kudzu during reboot, then shut down again,
put the other NIC in, reboot and reload the
second one, and then replace the ifcfg-eth0&1
files (i removed them after the first reboot
to avoid complications).  This is a tedious
process and requires me to be there physically.

In my ks.cfg I have the lines:

#external internet
network --bootproto static  --device eth0 --ip 128.193.40.73  --netmask 255.255.255.192  --gateway 128.193.40.65  --nameserver 128.193.38.105
#internal network
network --bootproto static  --device eth1 --ip 192.168.1.1  --netmask 255.255.255.0 --gateway 128.193.40.73

Am I missing something crucial here?  Do I
need to specify the types/modules to use in
the ks.cfg?  I thought detecting cards was done
automatically by the RedHat install process.

I know from the postings that kickstart has
successfully been used many times to quickly
boot a router.  I have been working on
kickstarting a router for some time now and
have almost gotten it perfected.  I am booting
off of a floppy using boot.img and installing
off of a cdrom.  Install specs, packages, and
post-commands all go perfect now (using a
PostInstall.sh script to do most of them as
recently posted on this list)

TIA -

- Tyler





[Index of Archives]     [Red Hat General]     [CentOS Users]     [Fedora Users]     [Fedora Maintainers]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux