network doesnt start on bootup
Bob
manaually started via system-config-network.
Ive removed network manager from starting up in init.d.
I disabled it in system-config-network and heres my ifcfg-eth0 file:
# Networking Interface
DEVICE=eth0
BOOTPROTO=static
HWADDR=00:0C:F1:97:D1:BB
ONBOOT=yes
IPADDR=192.168.1.12
NETMASK=255.255.255.0
DNS2=167.206.7.4
TYPE=Ethernet
GATEWAY=192.168.1.1
DNS1=167.206.112.138
NM_CONTROLLED=no
IPV6INIT=no
USERCTL=no
Can someone tell me how to fix this?
I have another computer that randomly eth0 just
goes 'down' and I dont know why that is either.
And in the good ole days you could just:
ifconfig eth0 up
and it would work, but that doesnt work anymore
or Id write a script to do it every 5 minutes just in
case. Does someone have a solution for a script
as well that would do this?
Thanks
Nico Kadel-Garcia
> Fedora 11 - Whenever I bootup my computer, eth0 must be
> manaually started via system-config-network.
> Ive removed network manager from starting up in init.d.
??? What do you mean by this? You mean that you've disabled the /etc/
init.d/network init script, which is what would normally start it?
'NetworkManager' is, in my opinion, completely unnecessary for server
class and most desktop instalations. It seems to be aimed at DHCP
environments where no one competent has assigned DHCP reservations. It
can be safely deleted from most non-laptop setups.
Jim Haynes
> Fedora 11 - Whenever I bootup my computer, eth0 must be
> manaually started via system-config-network.
You need to go to system->administration->services and enable network
That will make entries in /etc/rc?.d to bring up the network when the
system goes into those runlevels.
Nico Kadel-Garcia
??? Isn't that just doing "/sbin/chkconfig network on"? You can check
the settings of those init scripts manually with "/sbin/chkconfig --
list". That will tell you if the 'network' init script is disabled at
boot time. It also
Tecknode
Try this, note the "auot line replacing the Device line......
# Networking Interface
auto eth0
Allen Kistler
I don't do the system-config-* tools myself, but chkconfig is definitely
the OP's problem.
Fedora installs Network Manager to manage the network. If you yank it
out, which I always do, too, then you need to re-enable the classic
network init script.
# chkconfig --levels 2345 network on
Bob
> # chkconfig --levels 2345 network on
This worked, and I also did:
vi /etc/sysconfig/firstboot
FIRSTBOOT=YES
Unsure if the second was necessary, but I do remember
doing the first on another machine and it not working,
although I could be wrong. Im just happy it works now.
Network manager seems to be far more problematic
than it helping, and yes as far as I can tell its just for
DHCP...again opinion, not necessarily fact.
Thanks for all your help!
Moe Trin
<e20fb69c-20ca-48cd...@v25g2000yqk.googlegroups.com>, Bob wrote:
NOTE: Posting from groups.google.com (or some web-forums) dramatically
reduces the chance of your post being seen. Find a real news server.
>I also did:
>vi /etc/sysconfig/firstboot
>FIRSTBOOT=YES
>Unsure if the second was necessary, but I do remember
>doing the first on another machine and it not working,
>although I could be wrong. Im just happy it works now.
If you read the script '/etc/rc.d/init.d/firstboot' you will find a
description:
# Short-Description: Starts the firstboot configuration program
# Description: Firstboot runs the first time a machine is booted after
# installation. It checks for the existance of an
# /etc/sysconfig/firstboot file. If the file exists and
# contains RUN_FIRSTBOOT=NO, firstboot will not run. Otherwise
# firstboot will be run. If /etc/reconfigSys exists or if
# "reconfig" is provided in the kernel boot arguments,
# firstboot will run in reconfiguration mode.
and near the end of the script, it runs chkconfig to disable this
service once it ran successfully. If you run the command
`chkconfig | grep firstboot` you should find that firstboot is disabled
on all run-levels, and thus the contents of that file are not
inspected. If you run the command 'rpm -qi firstboot' you will find
Summary : Initial system configuration utility
Description :
The firstboot utility runs after installation. It guides the user through
a series of steps that allows for easier configuration of the machine.
Whether or not the program may be useful depends on your *nix admin
skills. Some feel it's a waste of another Meg of disk space as nearly
all it does could be run directly as part of the install program.
Old guy
karthikbalaguru
Yes, in linux, chkconfig is very helpful and easy to use for
configuring the services.
The chkconfig command can be used to Enable/Disable certain services.
You can get the list of system services that are either Enabled/
Disabled by
using the chkconfig --list command. Here, you check whether the
network is ON/OFF.
If OFF, use chkconfig to enable network to be started in a specific
runlevel.
Checkout -
http://www.redhat.com/docs/manuals/linux/RHL-7.3-Manual/custom-guide/s1-services-chkconfig.html
Karthik Balaguru