i am doing some post-installation-steps: Setting up WLAN with knetworkmanager in OpenSuse Leap 42.2
at the moment i working - connected with the internet through an ethernet-cable. But i want to set up the WLAN…
therefore i did some requests:
eth0 no wireless extensions.
linux-m28l:/home/martin # rfkill list
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
linux-m28l:/home/martin # iwconfig
lo no wireless extensions.
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=0 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
eth0 no wireless extensions.
linux-m28l:/home/martin # systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
Active: active (running) since Mo 2017-05-01 15:11:08 CEST; 43min ago
Main PID: 874 (NetworkManager)
├─ 874 /usr/sbin/NetworkManager --no-daemon
└─1056 /sbin/dhclient -d -q -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-eth0.pid -lf /var/lib/NetworkManag...
Mai 01 15:11:16 linux-m28l NetworkManager: <info> NetworkManager state is now CONNECTED_LOCAL
Mai 01 15:11:16 linux-m28l NetworkManager: <info> NetworkManager state is now CONNECTED_SITE
Mai 01 15:11:16 linux-m28l NetworkManager: <info> Policy set 'Wired connection 1' (eth0) as default for IPv4 rou... DNS.
Mai 01 15:11:16 linux-m28l NetworkManager: <13>May 1 15:11:16 dns-resolver: ATTENTION: You have modified /etc/re...ed...
Mai 01 15:11:16 linux-m28l NetworkManager: <13>May 1 15:11:16 dns-resolver: You can find my version in /etc/reso...onfig
Mai 01 15:11:16 linux-m28l NetworkManager: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched...
Mai 01 15:11:16 linux-m28l NetworkManager: You can find my version in /etc/resolv.conf.netconfig ...
Mai 01 15:11:16 linux-m28l NetworkManager: <info> (eth0): Activation: successful, device activated.
Mai 01 15:11:16 linux-m28l NetworkManager: <info> startup complete
Mai 01 15:11:17 linux-m28l NetworkManager: <info> NetworkManager state is now CONNECTED_GLOBAL
Hint: Some lines were ellipsized, use -l to show in full.
I can only help so far. I would suggest using YAST instead and also using YAST to select wicked as the network manager.
Have to admit though that as you have used kde I can’t be sure that there wont be problems. Having used kde for a long time I always do this sort of thing via YAST and only use kde as a last resort. YAST will be fully aware of how opensuse do things at the hardware level - kde ??? I always wonder.
My set up is a little different. I access the web via eth0 to a router. I also use wlan0 to to access another network via it’s router to use a printer on it’s network. Wisdom often states that I must use static addressing to do this on wlan0. I had plenty of help trying to get that to work but it wouldn’t so in the end I just set wlan0 to take it’s address from the router it’s connected to via YAST and it sorted it out.
Using wicked ? YAST may well sort things out when networkmanager is being used as well so try that first. Activating wicked will probably overwrite anything kde has done also resetting things in YAST is likely to.
;)One thing for sure the wlan0 config file will be a lot more complicated than the one for eth0 - another good reason to use yast.
I used wicked because it was installed by default. As it turned out in my case YAST set wicked up so that it used part of networkmanagers usual set up to handle wlan0.
Where YAST can come in really handy with this sort of thing is that if a another bucket of software is needed it will download and install it. It can also offer direct control of aspects below the desktop. KDE5 for instance wont show my default sound card as the default - the first one in the list. Thanks to yast I’m 100% sure that the one I want to be default really is. Phonon doesn’t even show all of the modes that the card is capable of - or didn’t last time I looked. It does show the one I use.
Please do not make a mess of this. Wicked and NetworkManager are for different kinds of network setup. Their usage depends on where you use the system for/how you use the system. So there is no “better or worse”, there is only “better for this kind of task”.
Also try to understand the difference between what is the system and it’s configuration and what is the desktop and it’s configuration. The latter depends on what the system (configuration) offers and differs from user to user and from desktop used to desktop used.
When this important aspect of Unix/Linux as a multi-user/multi-session system is overlooked, much confusion will be in your mind.