Re: Automatic start of network services

On Thu, 01 Jun 2006 08:08:46 +0100, Jedi Fans wrote:

On 01/06/06 01:49, Alejandro Montiel Scribbled:
Jedi Fans wrote:
On 30/05/06 22:00, Alejandro Montiel Scribbled:
Hello all,

I have an issue with 10.1 wherein every time I start my system, the
network services are not started and my wireless card cannot connect.
The
oonly way I can get it to work is to go into YaST every single time and
simply run the Network Card module and click Next to the end and then
when
the configuration runs, the services start and I can connect.
How can I solve this?

Thank you.

Alex
Open "konsole" or the terminal program of your choice and su to root
(type "su" and hit enter then enter your root password).
Type (where # is the prompt):
# rcnetwork status
it is says it isnt running, do:
# rcnetwork start
if it responds with an error, post it here ;)

IF that starts the network stuff you were on about, in YaST goto
system then "Runlevel editor" and Enable "network". This should
force it to start each time (unless there is an error!)


Hello,

it was my mistake that I forgot to mention that I did check the Runlevel
Editor and the network service was checked for runlevels 2, 3 and 5 and
it was enabled. Obviously rcnetwork status shows nothing when I have
just started my system because the network services are not running
until I manually go into Yast -> Network Devices -> Network Card module
and just click Next until it comes to the screen when the services are
started, only THEN can I connect to the internet. I did a lot of
searching on google groups and found one similar cases where this
behavior started happening after running an online update or other
instances where no specific connection was noted. So, apparently I am
not alone on this one.

I am open to any suggestions. It is just annoying to manually have to
run the network device module every time I start my system.

Alex

What does:
# rcnetwork start
do? If that solves it I am sure we can figure out a hack (as in,
adding it to /etc/init.d/boot.local perhaps).


Hi,

I just rebooted my system and did not run the Network module from YaST.
This is the output of the rcnetwork start command:

# rcnetwork start
Hint: you may set mandatory devices in /etc/sysconfig/network/config
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8 done
wlan0 device: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)
wlan0 warning: wpa_supplicant already running on interface
wlan0 IP address: 192.168.1.101/24 (DHCP was already running)done
Setting up service network . . . . . . . . . . . . . . done.

However, even after doing this, I had no connection to the internet. I
still had to run the module from YaST so I could post this message. Where
should I look?

Thank you,

Alex
.

Relevant Pages

  • Re: Automatic start of network services
    ... network services are not started and my wireless card cannot connect. ... I just rebooted my system and did not run the Network module from YaST. ...
    (alt.os.linux.suse)
  • Re: [SLE] : To SuSE people who builds the "kernel of the day"
    ... On Thursday 21 July 2005 01:05 pm, Catimimi wrote: ... USB doesn't work and my network refused to start up at boot time. ... when YAST finished the network would be up... ... rcnetwork start didn't start it up. ...
    (SuSE)
  • Re: win98 firewall
    ... in all or three posts still no argument or evidence proving or just ... >activated file sharing and no other network services. ... Read my post lower down about why you need a firewall ...
    (comp.security.firewalls)
  • Re: eth0 before pcmcia
    ... > initializing pcmcia. ... The NIC does ultimately get an IP and I'm on the network without ... automatically start any NICs which are PCMCIA cards anyway). ... start PCMCIA before the network services, the PCMCIA service will try to ...
    (Fedora)
  • Re: Sebastian - Re: What is blocking my ports?
    ... A packer filter will only give you security if you have in-depth ... I have over 104 services running on my machine, but these aren't network services. ...
    (comp.security.firewalls)