I am trying to configure a wireless connection from YAST under the Network Settings tool.
It doesn’t seem to do anything. My USB wifi device is detected in YAST > Hardware and I am using the module it says Hardware is using.
It doesn’t seem to save the module under YAST> Network Settings> Network Card Setup.
Is this tool broken or useless? It seems setting up WiFi should be easier than this. YAST should work shouldn’t it?
Additional info
/usr/bin/lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter
Bus 003 Device 002: ID 067b:2303 Prolific Technology, Inc. PL2303 Serial Port
Bus 004 Device 002: ID 08bb:2904 Texas Instruments Japan PCM2904 Audio Codec
Bus 006 Device 002: ID 0a81:0101 Chesen Electronics Corp. Keyboard
Bus 006 Device 003: ID 046d:c045 Logitech, Inc. Optical Mouse
/usr/sbin/iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 Ralink STA ESSID:""
Mode:Auto Frequency=2.412 GHz
Link Quality=10/100 Signal level:0 dBm Noise level:-143 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
sudo /usr/sbin/iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wlan0 Interface doesn't support scanning : Network is down
That works fine with my USB card. It generated “/etc/sysconfig/network/ifcfg-wlan0” and it successfully connects. You might check whether that file (with the appropriate name adjustment for the interface name" exists and has a recent time stamp.
There’s a setting for when to activate the interface. I have that set to “hotplug”. It connects to the configured network when I plug in the USB device.
Some USB devices need suitable firmware before they work. I don’t know if that applies to yours. Some part of the system managed to automatically install that firmware for my card, but I am not sure what triggers the install. It possibly happened when I was trying the device with NetworkManager on a different computer (also opensuse).
So, if we can assume you see your network devices in the YaST / Network Devices / Network Settings and you have not elected to use the Network Manager but rather Use the Traditional Method with ifup, you would open up a terminal session, become root and use the command ifdown eth0 and ifup wlan0 to switch to wireless. Then, in Network Settings, you can configure your wireless connection and even use the scanner. I would say though that with two network connections, I would run Network Manager and KWallet for Wireless connections, then you can select more easily, which one to use from your desktop.
Thank You,
I didn’t notice that “Network is down” before my first reply. Check with “/usr/sbin/rfkill list”. You might need to install “rfkill”.
What is Network Manager and where is it found? I seen o “Network Manger” in YAST and when I try to launch KNetorkManager from the KDE Menu> System> Desktop Applet nothing happens. It seems to be broken application too.
This connection isn’t going to be used all the time it’s just temporary while I am away from my wired connection. I do not want to replace my wired connection as the default connection. I am having to move out of my house while it’s fumigated for termites and I will be away three days with nothing to do and I want my computer. WiFi is the only connection type where I am having to stay.
The reason I put all that command line stuff in was because it is what is in the sticky.
I really don’t understand much of it at all. I am much more comfortable using GUI tools.
I can see that Hardware sees my USB WiFi interface and that is all I see that is working.
Is the CLI the only way to get WiFI working?
In the “Network Settings” page of Yast, choose the “Global Options” tab. There should be a choice there between “User Controlled with NetworkManager” and “Traditional Method with ifup”.
Running knetworkmanager won’t do anything useful until you switch those settings over in Yast.
OK I was able to flounder around and find I needed to install a firmware module for the USB WiFi interface
I also found how to launch NetworkManager ( It’s not Network Manager) by floundering around. The command is NetworkManager (refering to it as Network Manager is confusing.)
sudo /usr/sbin/iwlist scan
lo Interface doesn't support scanning.
eth0 Interface doesn't support scanning.
wlan0 Scan completed :
Cell 01 - Address: 00:14:BF:F4:93:6C
Protocol:802.11b/g
ESSID:"Ammeraal"
Mode:Managed
Channel:1
Quality:18/100 Signal level:-83 dBm Noise level:-115 dBm
Encryption key:on
Bit Rates:54 Mb/s
Cell 02 - Address: 00:1D:7E:C4:2F:75
Protocol:802.11b/g
ESSID:"kitfox"
Mode:Managed
Channel:6
Quality:100/100 Signal level:-31 dBm Noise level:-115 dBm
Encryption key:on
Bit Rates:54 Mb/s
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
Cell 03 - Address: 00:02:6F:9A:68:8C
Protocol:802.11b/g
ESSID:"kitfox"
Mode:Managed
Channel:6
Quality:26/100 Signal level:-79 dBm Noise level:-115 dBm
Encryption key:on
Bit Rates:54 Mb/s
IE: WPA Version 1
Group Cipher : TKIP
Pairwise Ciphers (1) : TKIP
Authentication Suites (1) : PSK
Cell 04 - Address: 00:24:B2:2A:A4:1C
Protocol:802.11b/g
ESSID:"SHWEFFERS"
Mode:Managed
Channel:11
Quality:2/100 Signal level:-89 dBm Noise level:-115 dBm
Encryption key:on
Bit Rates:36 Mb/s
It seems it’s not connecting me via the USB WiFI adapter even though NetworkManager says I am connected full strength. If I disconnect the CAT5 I have no internet.
Should I remove the configuration from YAST> Network Settings for wlan0 ?
ifconfig shows I am not getting an IP address for the USB WiFi adapter
ifconfig
eth0 Link encap:Ethernet HWaddr 6C:F0:49:07:E9:E5
inet addr:192.168.1.109 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::6ef0:49ff:fe07:e9e5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2469 errors:0 dropped:0 overruns:0 frame:0
TX packets:2367 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1369184 (1.3 Mb) TX bytes:464460 (453.5 Kb)
Interrupt:40 Base address:0xe000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:458 errors:0 dropped:0 overruns:0 frame:0
TX packets:458 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:40583 (39.6 Kb) TX bytes:40583 (39.6 Kb)
wlan0 Link encap:Ethernet HWaddr 00:A1:B0:C0:83:BC
inet6 addr: fe80::2a1:b0ff:fec0:83bc/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:10754 errors:0 dropped:0 overruns:0 frame:0
TX packets:242 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:951722 (929.4 Kb) TX bytes:16572 (16.1 Kb)
This is a Zonet ZEW2500P(04) in case anyone does a search for this device in the future.
I must have posted my last post while you posted. Sorry.
OK I did what you instructed and rebooted.
I still had to invoke NetworkManager from the CLI as su
It prompted me for a password and connected after I made the changes in YAST> Network Settings you suggested and I rebooted.
Do I need to delete entry for wlan0 I made in YAST> Network Settings? Since I really am going to use this on another network all together?
OK now the big question. I have no firewall turned on, on this box. It’s always lived it’s life on a wired connection behind a router firewall appliance so I didn’t need the hassle of having to open outside connections for stuff I do on the internet like XDCC that uses different ports and Bittorent. What do I do to turn on the firewall and still have the necessary connectivity to use NFS shares etc and be secure wirelessly at the same time?
Once you are using NetworkManager, the settings that you made with Yast are not used.
I’m not sure, but if the ethernet cable is connected, your routing will probably be over ethernet. To get internet access with just WiFi, you probably need to unplug the ethernet wire.
For the firewall, go to the Yast Security settings. You should be able to work your way through it.
Yes I discovered now the Network Settings in YAST are disabled now and NetworkManager controls both connections.
Is NetworkManager supposed to launch itself as I am having to launch it from the CLI?
I have to plug the USB WiFi adapter in to get it to mount as it’s off until I unplug it and plug it back in if it’s left plugged in at boot.
Dolphin can’t find the Network shares for a LONG time once I am connected to my Wireless/Wired router now as NFS isn’t started at boot (or it fails if it does I didn’t look yet.) and it’s start seems to be delayed until I actually look to access a file.
NetworkManager is supposed to be automatically launched, if you have the setting right.
Is it possible that you manually edited some of the “/etc/sysconf” scripts and broke something?
I have only tried the USB with plugging it in when the system is running. So I can’t comment on that. I think it is supposed to work if you leave it plugged in. But that might depend on other things, such as how the BIOS initialize the USB ports.
I never manually edited anything so that’s not the case. I don’t even know what /etc/sysconf is.
Well the USB wireless adapter is powered even when the computer is off if I leave it plugged in but I have booted it with it plugged in and and it’s not initialized and NetworkManager is not automatically started. I am pretty sure the kernel module loads the firmware so it can operate. Once I invoke NetworkManager it starts right up.
Is there a group I must be part of in YAST > Security and Users to have NetworkManager start on it’s own when my KDE session starts?
There’s a root NetworkManager daemon, “/usr/sbin/NetworkManager”. That one is supposed to automatically start as part of normal network startup.
Then there’s an applet that is run in your desktop session. Whether that starts or not might depend on desktop settings.
For me, the root daemon is starting automatically. In KDE, I am using the plasmoid network manager applet, and the startup of that can be configured in “Personal Settings” → “Startup and Shutdown” → “Service Manager”. It should default to being started. And then the panel/tray settings determine whether an icon shows up in the tray.
If your main root NetworkManager daemon is not starting automatically, then something is broken. I don’t know what causes that. Perhaps the logs will show a problem.
This might be a hint but trying to launch NetworkManager from the KDE start menu does nothing.
I am going to check the logs on that machine and see if I can find a hint there.
Is there a line I can add to the start up someplace or a line I need to change that will automatically start it?
OK. I am still using the KDE that shipped with 11.4 and you may be running a newer KDE I think. If I go into networking from “Personal Setting s (Configure Desktop)” It’s set to start.
Pouring over the boot log I see nothing but again I don’t really know what I am looking for I do see that the USB WiFi adapter is detected in the boot log but that’s it.
error log has some entries but none seem to relate to starting NetworkManager Perhaps someone else has had this problem. Since my wireless is now working do you think I should take this to “Applications”?
Jun 25 15:51:52 linux-edn0 ntpd[2510]: line 75 column 1 syntax error, unexpected T_EOC, expecting T_Default or T_Ipv4_flag or T_Ipv6_flag or T_String
Jun 25 15:51:52 linux-edn0 ntpd[2510]: syntax error in /etc/ntp.conf line 75, column 1
Jun 25 15:52:05 linux-edn0 kernel: 276.471203] ===>rt_ioctl_giwscan. 4(4) BSS returned, data->length = 701
Jun 25 15:52:12 linux-edn0 kernel: 283.431619] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:52:12 linux-edn0 kernel: 283.431627] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:52:44 linux-edn0 kernel: 314.552862] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:52:44 linux-edn0 kernel: 314.552870] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:52:46 linux-edn0 kernel: 317.471471] ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 412
Jun 25 15:53:14 linux-edn0 kernel: 345.469350] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:53:14 linux-edn0 kernel: 345.469357] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:53:45 linux-edn0 kernel: 376.488106] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:53:45 linux-edn0 kernel: 376.488113] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:53:47 linux-edn0 kernel: 378.476213] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 845
Jun 25 15:54:17 linux-edn0 kernel: 407.507071] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:54:17 linux-edn0 kernel: 407.507078] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:54:48 linux-edn0 kernel: 438.527012] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:54:48 linux-edn0 kernel: 438.527021] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:55:08 linux-edn0 kernel: 459.470247] ===>rt_ioctl_giwscan. 4(4) BSS returned, data->length = 701
Jun 25 15:55:18 linux-edn0 kernel: 468.523089] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:55:18 linux-edn0 kernel: 468.523091] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:55:49 linux-edn0 kernel: 499.542948] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:55:49 linux-edn0 kernel: 499.542955] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:56:19 linux-edn0 kernel: 530.460162] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:56:19 linux-edn0 kernel: 530.460170] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:56:49 linux-edn0 kernel: 560.475239] ===>rt_ioctl_giwscan. 5(5) BSS returned, data->length = 845
Jun 25 15:56:50 linux-edn0 kernel: 561.484393] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:56:50 linux-edn0 kernel: 561.484400] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:57:22 linux-edn0 kernel: 592.498776] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:57:22 linux-edn0 kernel: 592.498783] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:57:53 linux-edn0 kernel: 623.522921] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:57:53 linux-edn0 kernel: 623.522928] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:58:24 linux-edn0 kernel: 654.536964] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:58:24 linux-edn0 kernel: 654.536972] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:58:50 linux-edn0 kernel: 681.472231] ===>rt_ioctl_giwscan. 4(4) BSS returned, data->length = 701
Jun 25 15:58:55 linux-edn0 kernel: 685.564787] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:58:55 linux-edn0 kernel: 685.564794] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:59:25 linux-edn0 kernel: 716.472474] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:59:25 linux-edn0 kernel: 716.472481] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 15:59:57 linux-edn0 kernel: 747.491286] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 15:59:57 linux-edn0 kernel: 747.491293] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 16:00:28 linux-edn0 kernel: 778.510038] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 16:00:28 linux-edn0 kernel: 778.510045] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 16:00:51 linux-edn0 kernel: 802.472416] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 556
Jun 25 16:00:59 linux-edn0 kernel: 809.530097] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 16:00:59 linux-edn0 kernel: 809.530104] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 16:01:30 linux-edn0 kernel: 840.558424] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 16:01:30 linux-edn0 kernel: 840.558431] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 16:01:46 linux-edn0 kernel: 857.147416] martian source 192.168.1.255 from 192.168.1.104, on dev wlan0
Jun 25 16:01:46 linux-edn0 kernel: 857.147423] ll header: ff:ff:ff:ff:ff:ff:00:25:22:92:7a:e3:08:00
Jun 25 16:02:00 linux-edn0 kernel: 871.483340] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 16:02:00 linux-edn0 kernel: 871.483347] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 16:02:32 linux-edn0 kernel: 902.509847] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 16:02:32 linux-edn0 kernel: 902.509854] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 16:02:52 linux-edn0 kernel: 923.471625] ===>rt_ioctl_giwscan. 3(3) BSS returned, data->length = 556
Jun 25 16:03:02 linux-edn0 kernel: 932.818675] martian source 192.168.1.255 from 192.168.1.104, on dev wlan0
Jun 25 16:03:02 linux-edn0 kernel: 932.818682] ll header: ff:ff:ff:ff:ff:ff:00:25:22:92:7a:e3:08:00
Jun 25 16:03:03 linux-edn0 kernel: 933.535403] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 16:03:03 linux-edn0 kernel: 933.535410] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 16:03:34 linux-edn0 kernel: 964.568936] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 16:03:34 linux-edn0 kernel: 964.568943] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 16:04:05 linux-edn0 kernel: 995.601705] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 16:04:05 linux-edn0 kernel: 995.601708] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
Jun 25 16:04:36 linux-edn0 kernel: 1026.530679] martian source 192.168.1.255 from 192.168.1.100, on dev wlan0
Jun 25 16:04:36 linux-edn0 kernel: 1026.530686] ll header: ff:ff:ff:ff:ff:ff:6c:f0:49:b6:59:1b:08:00
I found this in /etc/NetworkManager
[main]
plugins=ifcfg-suse,keyfile
no-auto-default=6c:f0:49:07:e9:e5,
How do I make that “auto” or do I want to make that auto do I need to modify a start up setting someplace else?
Is NetworkManager a KDE app or a app that runs under KDE?
I found this thread NetworkManager will not start automatically. and am installing that plasmoid. once I get that done I’ll see about getting things to start automatically. This is a fail around machine so if I break things in some horrid way I can always do a reinstall. 
OK I got it to work at boot up my going back to the traditional ifup method and changing the setting for the wireless card to “On Cable Connection” in YAST> Network Settings>Network Card Setup> General tab.
It looks like I will have to manually add/change networks when I change to a different wireless network.
I did add plasmoid-networkmanagement and removed the NetworkManager that was installed off the 11.4 DVD but I could not figure out how to launch plasmoid-networkmenagement.
The settings in Personal Setting (configure Desktop) >Network Settings from the KDE start menu never seemed to do anything ever.
I do have to un-plug and plug the USB WiFi adapter when I reboot the machine as it is switched off when you shut down and doesn’t wake up until it’s un-plugged and plugged back in.
If you are using “ifup”, you can keep two different versions of “ifcfg-wlan0” around. Keep them in a different directory. Then move the one you want into place in “/etc/sysconfig/network”, and run (as root) “/etc/init.d/network” to switch.
Hmm, I had problems with switching networks when using “ifup” until I change the DHCP to use “dhclient”. You can configure that in the “/etc/sysysconfig” settings of Yast.
If it isn’t starting automatically, there should be a setting in “Personal Settings” –> “Startup and Shutdown” –> “Service Manager”. Make sure that there is a check in the box for “NetworkManager User Settings Service”.