On Sat, Nov 30, 2013 at 4:44 PM, ~Stack~ <[log in to unmask]> wrote:
> On 11/30/2013 09:34 AM, olli hauer wrote:
>>
>> grep network minimal.cfg
>> network --onboot yes --device eth0 --bootproto dhcp
>>
>> grep -i network /etc/sysconfig/network
>> NETWORKING=yes
>
> On 11/30/2013 09:23 AM, Tom H wrote:> On Sat, Nov 30, 2013 at 7:03 AM,
>>
>> Do you have "--onboot=yes" on the "network" line of the kickstart
>> file?
>
> I started out with this line in my kickstart:
> network --bootproto=dhcp --device=eth0 --onboot=on
>
> And I thought maybe that was the problem, but even after the change I
> still have the same problem with no DHCP on boot. Here is some more
> information:
>
> $ sed -e '/^#/d' -e '/^$/d' anaconda-ks.cfg
> ...
> %packages --nobase
> ...
> %end
>
> $ cat /etc/sysconfig/network-scripts/ifcfg-eth0
> DEVICE="eth0"
> BOOTPROTO="dhcp"
> HWADDR="00:22:19:E1:28:36"
> IPV6INIT="yes"
> MTU="1500"
> NM_CONTROLLED="yes"
> ONBOOT="yes"
> TYPE="Ethernet"
> UUID="61008086-5e0e-4db2-8732-5b62bf5fc866"
>
> I changed that to the following, but still it doesn't get a DHCP IP
> until I run `ifup eth0`:
> DEVICE="eth0"
> BOOTPROTO="dhcp"
> HWADDR="00:22:19:E1:28:36"
> IPV6INIT="yes"
> MTU="1500"
> NM_CONTROLLED="no"
> NETWORKING="yes"
> ONBOOT="yes"
> TYPE="Ethernet"
> UUID="61008086-5e0e-4db2-8732-5b62bf5fc866"
>
> I went back to the original ifcfg-eth0 and installed NetworkManager (and
> all of these other packages: ConsoleKit ConsoleKit-libs ModemManager
> NetworkManager-glib avahi-autoipd dbus dnsmasq eggdbus libdaemon
> libgudev1 libnl libpcap libudev mobile-broadband-provider-info polkit
> ppp wpa_supplicant), and now I get a DHCP IP on boot, but I don't
> understand why I have to install a bunch of extra packages to get a DHCP
> IP on boot.
>
> What am I missing here?

AIUI you're getting 'chkconfig network --list (network 0:off 1:off
2:on 3:on 4:on 5:on 6:off)', 'NETWORKING=yes' and 'ONBOOT="yes"'. That
should ensure that your nic's brought up at boot.

Does adding '--activate' to the 'network' line make a difference?
Instinctively, it shouldn't because that only controls bringing up the
network in anaconda...

Could it be that '%packages --nobase' isn't pulling in something
that's needed? Since you can run 'ifup eth0' to bring up the network,
all that's necessary must be installed.

Have you tried 'service network restart'? Does that bring up your nic?

Have you tried installing with '%packages' rather than with '%packages
--nobase'?

I've just tried 'yum --disablerepo=* --enablerepo=sl
--enablerepo=sl-security --installroot=/mnt install @core' and 'yum
--disablerepo=* --enablerepo=sl --enablerepo=sl-security
--installroot=/mnt install @base' on my laptop and they wanted to pull
in 189 and 343 packages respectively. I skimmed through the two lists
but couldn't spot anything that might help, sorry.

You shouldn't need to install NM in order to get networking to come up.