YaST -> System Services (Runlevel) produces the list of services that run at boot.
network, network-remotefs, nfs, nscd, and ntp are all “Yes*” at every boot. The biggest problem is that network hasn’t started and NetworkManager - or, namely, nm-applet, doesn’t show up and I cannot connect to my network.
If I enable network manually from System Services, NetworkManager appears, asks for the keyring password, connects, and I’m fine - until I reboot. Then I have to go back into System Services and manually enable network in order to connect.
YaST -> System Services (Runlevel) produces the list of services that run at boot.
network, network-remotefs, nfs, nscd, and ntp are all “Yes*” at every boot. The biggest problem is that network hasn’t started and NetworkManager - or, namely, nm-applet, doesn’t show up and I cannot connect to my network.
If I enable network manually from System Services, NetworkManager appears, asks for the keyring password, connects, and I’m fine - until I reboot. Then I have to go back into System Services and manually enable network in order to connect.
What would cause this? Any suggestions?
-Ian
If you open YaST (Enter Root User Password) / Network Devices / Network Services / Global Options Tab / Network Setup Method is the bullet for User Controlled with NetworkManager set? And, by the way, Welcome to the openSUSE forums EchoLynx!
Are you trying to connect using wireless but may also use a wired connection? When using wireless in gnome have you setup the application keyring, to keep your wireless passphrase? If you only use one network connection all of the time, using the Traditional Method using ifup will start up faster than using networkmanager. Use networkmanager when you are using a laptop and switch between networks a lot.
robin_listas: I think you’re right, though it doesn’t matter to me. I just want it to work without intervention.
jdmcdaniel3:
I am only using a wireless connection at the moment, so I tried ifup. Unfortunately, that didn’t work. After configuring the wireless card, the configuration application process hung on something like “starting network services”, the same way starting the network service manually from System Services takes several seconds, only this time it takes about twice as long and the end result isn’t a connection.
jdmcdaniel3:
I am only using a wireless connection at the moment, so I tried ifup. Unfortunately, that didn’t work. After configuring the wireless card, the configuration application process hung on something like “starting network services”, the same way starting the network service manually from System Services takes several seconds, only this time it takes about twice as long and the end result isn’t a connection.
Did you enter the network SSID and network passphrase into the ifup configuration? Basically, if you can connected with networkmanager, you can connect with ifup. Sometimes, I find you need to open up a terminal session once, become root with su - and enter the ifdown command for the hardwired network like ifdown eth0 for instance. When online, you can search on ifup and ifstatus to get a list of associated commands.
While I had configured the SSID and WPA key correctly, I hadn’t set the default gateway. Once done, I still couldn’t connect, so I did the following:
ian@ian-openSUSE:~> sudo su -
ian-openSUSE:~ # ifstatus wlan0
wlan0 device: RaLink RT2800 802.11n PCI
DHCP4 client NOT running
DHCP6 client NOT running
wlan0 is down
ian-openSUSE:~ # ifup wlan0
wlan0 device: RaLink RT2800 802.11n PCI
wlan0 starting wpa_supplicant
Starting DHCP4+DHCP6 client on wlan0. . . . . . . .
wlan0 IP address: 192.168.1.107/24
wlan0 DHCP6 continues in background
ian-openSUSE:~ #
Then I was connected. I tried restarting to see if the ‘network’ service was was running at boot time, and it was - but I still wasn’t connected. Run “ifup wlan0” and I’ll connect.
It seems like progress, but we aren’t there yet. I still have to do something to connect after every boot.
So, you could create a script that runs this command perhaps on each reboot. Use a text editor to create a netup script:
#!/bin/bash
#: Title : netup
#: Date Created: Sat Oct 8 12:14:16 CDT 2011
#: Last Edit : Sat Oct 8 12:14:16 CDT 2011
#: Author : EchoLynx
#: Version : 1.00
#: Description :
#: Options :
ifup wlan0
exit 0
# End Of Script
Then, you need to copy the file to /etc/init.d, mark it executable and assign it to run at some run level:
lets try a different tack. Lets add it to an existing file /etc/init.d/after.local. We need to edit this file as root. In kde you could do an Alt-F2 and enter:
kdesu kwrite /etc/init.d/after.local
Then add in your command at the end of the file.
#! /bin/sh
#
# Copyright (c) 2010 SuSE LINUX Products GmbH, Germany. All rights reserved.
#
# Author: Werner Fink, 2010
#
# /etc/init.d/after.local
#
# script with local commands to be executed from init after all scripts
# of a runlevel have been executed.
#
# Here you should add things, that should happen directly after
# runlevel has been reached. Common environment
# variables for this are:
# RUNLEVEL -- The current system runlevel.
# PREVLEVEL -- The previous runlevel (useful after a runlevel switch).
#
ifup wlan0
I found another suggestion to then add this after the previous line:
#! /bin/sh
#
# Copyright (c) 2010 SuSE LINUX Products GmbH, Germany. All rights reserved.
#
# Author: Werner Fink, 2010
#
# /etc/init.d/after.local
#
# script with local commands to be executed from init after all scripts
# of a runlevel have been executed.
#
# Here you should add things, that should happen directly after
# runlevel has been reached. Common environment
# variables for this are:
# RUNLEVEL -- The current system runlevel.
# PREVLEVEL -- The previous runlevel (useful after a runlevel switch).
#
ifup wlan0
iwlist wlan0 scan
Lets go back to the basics. Goto YaST (Enter Root User Password) / Network Devices / Network Settings / Overview Tab / Select Wireless Device with mouse / Press Edit Bottom Left / General Tab (of Edit now) / Device Activation / Activate Device says: **On NFSroot **is what my hard wired network connection says. What does yours say for the wireless adapter? You can just press Next and then OK to not change it. But, if it says Manually, that might be the problem.
On 2011-10-08 19:46, jdmcdaniel3 wrote:
> Then, you need to copy the file to /etc/init.d, mark it executable and
> assign it to run at some run level:
>
>
> Code:
> --------------------
> sudo cp netup /etc/init.d
> sudo chmod +x /etc/init.d/netup
> sudo ln -s /etc/rc5.d/netup /etc/init.d/netup
> --------------------
>
>
> There are other ways to do this I am sure, but this should work.
No, it should not. The symlinks are ignored in a normal openSUSE install.
You have to follow procedure as documented and call checkinstall.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)
I guess there is some detail that we are missing. If you remove the two commands added to after.local, restart, open up a terminal session and type in these commands, what do you get. Post the results here for use to see again.
su -
password:
ifup wlan0
iwlist wlan0 scan
What was the name of the service you would start to cause networking to come up when using networkmanager? We have started a second page and this keeps from needing to go backwards.
