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

Re: [Spacewalk-list] Kickstart Difficulties - Networking

On Wed, 2009-08-12 at 08:05 -0500, Daniel Robb wrote:
> Andy,
> I didn’t think this was possible.  From looking at the ks.cfg options
> documentations, it seems to be that if you do not supply the ip
> address in the ks.cfg file the installer assumes that the the
> installation should be done over eth0 via DHCP.
> You could try just supplying the ip address on the boot line (linux
> ip=nnn.nnn.nnn.nnn).
> -Dan

Hey, I'm with you on that one, it has me baffled.  My "network" line in
the kickstart consists of the following options (with correct IPs
replaced of course):

--device eth0 --bootproto static --noipv6 --netmask <mask> --gateway
<gw> --nameserver <dns1>,<dns2>

As you can see, I'm omitting the "--ip <someip>" directive.  What
happens in anaconda is that it pops up a box that asks me to configure
ipv4 and ipv6... with ipv6 already disabled, but dhcp selected for ipv4.
I change that to static... and move to the next screen.. .it then shows
a network configuration page with all of the data save IP pre-filled.  I
pop in the IP I expect the system to configure, and anaconda continues
on its merry way.  However, when the system is done, the IP that gets
configured is the IP that the system got from DHCP for PXE booting
rather than the IP that I supplied.

I'd rather not have to modify anything to get this to work.  I'm trying
to make this as admin-proof as possible for installs.  In fact, I wish
ipv4 would be pre-set to "static" as well, since that's what I told
anaconda with "--bootproto static" ... but eh... I'll settle for it just
using the IP that I told it to.



Attachment: signature.asc
Description: This is a digitally signed message part

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