I am having awful trouble establishing WLAN connection on a fresh Tumbleweed install, credentials not being saved, connection not being established, the GUI ‘yast lan’ tool exits silently after ‘completing’ all the steps (little checkmarks appear next to those’) and pretty much the only error I was able to identify is through investigation of the systemd log where I can see the wicked systemd unit throwing the error ‘WIRELESS_WPA_PSK value not specified’. The wired connection can be established withouth any issue, additionally I was able to use wireless during the installation (at least I think the connection was established due to the fact I believe it was checking for installator updates during the installation).
Any help and suggestions much appreciated. Weird issue, not sure how to proceed.
I have, and as I said credentials are not being stored, every time the settings are adjusted (credentials/connection type/etc. etc.) they disappear after applying the settings and do not seem to have any effect, the ‘yast2 lan’ window closes silently, apparently no error, yet the ‘wlp4s0’ interface is down, no effect.
I am aware of NM, decided on using wicked instead. If the switch to OpenSUSE is successful I want to be able to use SUSE-native solutions, yast2, wicked and other such system management solutions. Otherwise the switch to SUSE makes not much sense in my case.
haven’t supplied your wireless credentials via YaST yet?
I have, and as I said credentials are not being stored, every time the settings are adjusted (credentials/connection type/etc. etc.) they disappear after applying the settings and do not seem to have any effect, the ‘yast2 lan’ window closes silently, apparently no error, yet the ‘wlp4s0’ interface is down, no effect.
you may decide that NetworkManager is more convenient for you.
Thank you, I am aware of NM, decided on using wicked instead. If the switch to OpenSUSE is successful I want to be able to use SUSE-native solutions, yast2, wicked and other such system management solutions. Otherwise the switch to SUSE makes not much sense to me, in my case. The logo I really like and a sentiment to SUSE is not enough I’m afraid
haven’t supplied your wireless credentials via YaST yet?
If only it was that easy I have the credentials in, and as I said credentials are not being stored, every time the settings are adjusted (credentials/connection type/etc. etc.) they disappear after applying the settings and do not seem to have any effect, the ‘yast2 lan’ window closes silently, apparently no error, yet the ‘wlp4s0’ interface is down, no effect.
you may decide that NetworkManager is more convenient for you.
Thank you, I am aware of NM, decided on using wicked instead. If the switch to OpenSUSE is successful I want to be able to use SUSE-native solutions, yast2, wicked and other such system management solutions. Otherwise the switch to SUSE makes not much sense to me, in my case. The logo I really like and a sentiment to SUSE is not enough I’m afraid
Be aware that Wicked should “remember” the password long enough for the current network session, but if your machine moves to another location, the password will be “forgotten” when your new password is entered. This is why NM is recommended for wireless connections because it’s used so commonly by mobile machines like laptops.
At one time, in the past, I created a subdirectory of “/etc/sysconfig/network” and put copies of the file there with suitable names for where I was corrected. If I moved the laptop to a different location, I would just copy the appropriate file back. It is a convenient way for switching networks.
That was back in the days when NetworkManager did not work very well. These days, I just use NM.
I have the credentials in, and as I said credentials are not being stored, every time the settings are adjusted (credentials/connection type/etc. etc.) they disappear after applying the settings and do not seem to have any effect, the ‘yast2 lan’ window closes silently, apparently no error, yet the ‘wlp4s0’ interface is down, no effect.