Setting up WiFi was originally painless and has worked since I installed Leap around June of last year. Now, for some reason, during a system update no less, the system will not connect to the router (FIOS on the 2.4 GHz band) after a reboot or shutdown. The last update seemed to cause the problem. I can setup WiFi an the morning to use the system during the day but not connect after a reboot.
Network controller: Qualcomm Atheros AR9485 Wireless Network Adapter (rev 01) made by TP Link (IIRC). We have a 100 Mbps FIOS setup from Verizon. Phones and tablet are fine. This PC runs an AMD 8320E CPU on an AMD 760 uATX mainboard. Everything else seems to work. I tried a USB stick temporarily but I’m too far away from the router to use those as this setup uses a larger antenna for extra gain across our apartment.
I looked at the libraries associated with Yast and noticed that Yast-online-update-configuration is showing as deprecated (red) on the list generated by Yast during a lookup. That’s the only odd thing I can find.
Should I have filed a bug report? Has anyone else seen this problem with wireless.
Further to the above, I assume that you’re using NetworkManager (and not wicked)? How is your wifi system connection defined? Examine the connection configuration defined in the /etc/NetworkManager/system-connections/ directory and report back. You can obfuscate the connection credentials if you want to share the config here. Is the connection defined as a user connection or system connection? Explanation about that here…
Well, that confirms that wlan0 (wireless device node) is active, with IP address assigned and DNS servers configured. Is the problem that you’re just not getting connected automatically during boot?
Yes. It’s like I setup the WiFi in Yast but the system has no record of it. It should return after shutdown or reboot but the connection is forgotten later.
You’re using wicked (not NetworkManager), so that is why there is no configuration in the /etc/NetworkManager/system-connections/ directory. Instead, the relevant config file is /etc/sysconfig/network/ifcfg-wlan0
I’m not sure why you’re not connecting at boot, but you can examine the log with
I’m having a similar problem after one of the recent patches. My wlan configuration is not lost, but my wlan no longer starts automatically after a reboot. I can start it manually after login with “wicked ifup wlan0”. I have the following errors logged on boot but haven’t been able to figure out the problem. Not sure what patch broke it, one of the ones that came out in the last week or two.
Mar 21 09:00:18 HP-Linux dbus-daemon[1012]: [system] Failed to activate service 'fi.epitest.hostap.WPASupplicant': timed out (service_start_timeout=25000ms)
Mar 21 09:00:18 HP-Linux wickedd[1230]: ni_wpa_interface_bind(wlan0): Operation not permitted
Mar 21 09:00:18 HP-Linux wickedd[1230]: wpa_supplicant doesn't know interface wlan0
Mar 21 09:00:18 HP-Linux wickedd-nanny[1236]: device wlan0: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure
Mar 21 09:00:18 HP-Linux wickedd-nanny[1236]: wlan0: failed to bring up device, still continuing
Mar 21 09:00:23 HP-Linux wicked[1237]: lo up
Mar 21 09:00:23 HP-Linux wicked[1237]: wlan0 device-not-running
Mar 21 09:00:23 HP-Linux wicked[1237]: eth0 no-device
Mar 21 09:00:23 HP-Linux wicked[1237]: wlan0-save no-device
Mar 21 09:00:23 HP-Linux systemd[1]: Started wicked managed network interfaces.
Mar 21 09:00:23 HP-Linux systemd[1]: Reached target Network.
Mar 21 09:00:23 HP-Linux systemd[1]: Starting OpenSSH Daemon...
Mar 21 09:00:23 HP-Linux systemd[1]: Starting WPA Supplicant daemon...
Mar 21 09:00:23 HP-Linux systemd[1]: Started Backup of /etc/sysconfig.
I installed the older version of wpa_supplicant using Yast. Isn’t the version that keeps trying to update my system the broken version or am I missing something? Installing the older version of wpa_supplicant does result in a network connection after a restart. Would copying the version shown above to my system and installing manually fix the problem? It seems like I’d end up unable to connect again.
Install the version that works. Then lock that version so it won’t update. To lock in Yast, right-click on the installed package, and select “protected - do not modify”.
You will probably get a conflict when running Yast online update, and one of the choices will be to skip that patch.
I probably should have. But that bugs description indicated a wifi setup failure and indicated the interface could only be managed by network manager and that wicked fails. My problem is only that my wlan fails to start on boot and can be managed by wicked with no problem other than needing a manual “wicked ifup wlan0” command at login. It is undoubtedly caused by the same patch, but not having any experience with openSUSE bug reporting I didn’t know how important it is to have an accurate description so I created my own. I figured it could always be closed as a dup if that was appropriate. I’m open to guidance on when to open a new bug or update a similar one.
As explained in the first bug report, on boot wpa_supplicant fails to start when wickedd attempts to setup interface; when you bring up interface manually, wpa_supplicant is already started so everything works.