Bugzilla – Bug 1157394
Configuring wifi interface via yast2 not working
Last modified: 2023-01-24 16:02:54 UTC
Going into the network configuration panel, and selecting wicked as the network manager, and clicking edit on a wifi interface, it correctly scans and finds the SSIDs available. When selecting an SSID, the form indicates that the access point is "ad hoc" and unencrypted. I set the encryption to WPA2-PSK, and no matter whether I set the mode to ad hoc or managed, when I click next, yast2 immediately returns its starting panel (normally it would spend a while thinking while it configures the network), and networking is not configured. Wicked appears to be working correctly - I had saved some wicked configuration files, and I can load these and they work. But given wicked's XML configuration format doesn't appear to be documented, it has limited my ability to connect to new wifi connections that don't use the same encryption scheme. Normally, I do a zypper dup every week, so I always running close the the latest Tumbleweed distro. I first noticed this problem on 30th October, when I upgraded my network equipment at home, and attempted to connect to the new Wifi 4 AP (aka 802.11ac). I can also confirm that it did work on October 15th, so the problem could not have arisen much before that date.
Hi Russell, Could you please attach the logs collected running the save_y2logs command here? They will help a lot. More information available at https://en.opensuse.org/openSUSE:Report_a_YaST_bug Thanks in advance.
Created attachment 824732 [details] y2logs as requested
(In reply to Russell Sandish from comment #0) > Going into the network configuration panel, and selecting wicked as the > network manager, and clicking edit on a wifi interface, it correctly scans > and finds the SSIDs available. When selecting an SSID, the form indicates > that the access point is "ad hoc" and unencrypted. I set the encryption to > WPA2-PSK, and no matter whether I set the mode to ad hoc or managed, when I > click next, yast2 immediately returns its starting panel (normally it would > spend a while thinking while it configures the network), and networking is > not configured. The changes you have notice are mainly because we have done some re-factorization in yast2-network module. https://lizards.opensuse.org/2019/08/30/yast-sprint-83/ > > Wicked appears to be working correctly - I had saved some wicked > configuration files, and I can load these and they work. But given wicked's > XML configuration format doesn't appear to be documented, it has limited my > ability to connect to new wifi connections that don't use the same > encryption scheme. YaST do not use wicked XML configuration directly, but still writes down the ifcfg files which wicked reads for declaring it internal state. That is something we have been discussing and maybe something yast-network will do in the future. We have being modeling it in order to support multiple backends like NM, wicked or even systemd-network but as said it is something we still do not support. > > Normally, I do a zypper dup every week, so I always running close the the > latest Tumbleweed distro. > > I first noticed this problem on 30th October, when I upgraded my network > equipment at home, and attempted to connect to the new Wifi 4 AP (aka > 802.11ac). I can also confirm that it did work on October 15th, so the > problem could not have arisen much before that date. I already fixed a bug (https://bugzilla.suse.com/show_bug.cgi?id=1155639) related to WPA2-PSK configuration that will be available in yast2-network-4.2.26, so it could be already fixed. See https://github.com/yast/yast-network/pull/1001 But would be nice to have some feedback, so, once you get the new version, could you verify if you are still experimenting some problem related to WPA2-PSK configuration?
Just did a zypper dup, but the issue is still there. yast2-network exits immediately after pressing "next" in the edit network configuration, and no change of configuration happens. rusnuc>more /etc/os-release NAME="openSUSE Tumbleweed" # VERSION="20191121" ID="opensuse-tumbleweed" ID_LIKE="opensuse suse" VERSION_ID="20191121" PRETTY_NAME="openSUSE Tumbleweed" ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:tumbleweed:20191121" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" LOGO="distributor-logo" Maybe I should check what happens with a clean install...
I just did a completely fresh install of Tumbleweed on a spare NUC I have here, and can confirm that the wifi configuration problem still exists. Also, on a more minor note, the network installer fails to be able to use Wifi. This bug has been present a few weeks. I needed to plug in an ethernet cable to perform the installation.
Hi Russel, (In reply to Russell Sandish from comment #4) > Just did a zypper dup, but the issue is still there. yast2-network exits > Did you check if yast2-network version was >= 4.2.26?
(In reply to Russell Sandish from comment #0) > Going into the network configuration panel, and selecting wicked as the > network manager, and clicking edit on a wifi interface, it correctly scans > and finds the SSIDs available. When selecting an SSID, the form indicates > that the access point is "ad hoc" and unencrypted. I set the encryption to > WPA2-PSK, and no matter whether I set the mode to ad hoc or managed, when I > click next, yast2 immediately returns its starting panel (normally it would > spend a while thinking while it configures the network), and networking is > not configured. About returning directly to the interfaces list dialog, it is the expected behavior. That is, before 'network-ng' there were a sequence which first configured the interface address, hardware and general config, and then specific wireless configuration. Now, there is not an extra step for the specific wireless settings but it is in its own tab. Apart of that, when choosing a different auth method the dialog is changed dynamically showing fields or buttons depending on chosen option. > > Wicked appears to be working correctly - I had saved some wicked > configuration files, and I can load these and they work. But given wicked's > XML configuration format doesn't appear to be documented, it has limited my > ability to connect to new wifi connections that don't use the same > encryption scheme. > > Normally, I do a zypper dup every week, so I always running close the the > latest Tumbleweed distro. > > I first noticed this problem on 30th October, when I upgraded my network > equipment at home, and attempted to connect to the new Wifi 4 AP (aka > 802.11ac). I can also confirm that it did work on October 15th, so the > problem could not have arisen much before that date.
I tried to configure my Wifi with "Managed" mode and "WPA-PSK" and I can confirm it worked, but I found two issues when reading the sysconfig files. Basically the "mode" and "auth_mode" selected options are lost when reading the existing config. So, at least those issues should be solved.
@David Diaz, the version of yast2-network on bopth the zypper dupped machine, and the freshly installed machine was 4.2.28: Information for package yast2-network: -------------------------------------- Repository : Main Repository (OSS) Name : yast2-network Version : 4.2.28-1.1 Arch : noarch Vendor : openSUSE Installed Size : 1010.9 KiB Installed : Yes Status : up-to-date Source package : yast2-network-4.2.28-1.1.src Summary : YaST2 - Network Configuration Description : This package contains the YaST2 component for network configuration.
(In reply to Russell Sandish from comment #9) > @David Diaz, the version of yast2-network on bopth the zypper dupped > machine, and the freshly installed machine was 4.2.28: > > Information for package yast2-network: > -------------------------------------- > Repository : Main Repository (OSS) > Name : yast2-network > Version : 4.2.28-1.1 > Arch : noarch > Vendor : openSUSE > Installed Size : 1010.9 KiB > Installed : Yes > Status : up-to-date > Source package : yast2-network-4.2.28-1.1.src > Summary : YaST2 - Network Configuration > Description : > This package contains the YaST2 component for network configuration. Thanks Russell. It seems that @Knut already test it and found what is working as expected and what is wrong. See comment #8. And he is already working on it, see https://github.com/yast/yast-network/pull/1007
(In reply to Russell Sandish from comment #9) > @David Diaz, the version of yast2-network on bopth the zypper dupped > machine, and the freshly installed machine was 4.2.28: > > Information for package yast2-network: > -------------------------------------- > Repository : Main Repository (OSS) > Name : yast2-network > Version : 4.2.28-1.1 > Arch : noarch > Vendor : openSUSE > Installed Size : 1010.9 KiB > Installed : Yes > Status : up-to-date > Source package : yast2-network-4.2.28-1.1.src > Summary : YaST2 - Network Configuration > Description : > This package contains the YaST2 component for network configuration. Ruseel, as I commented previously, the return to the ma(In reply to Russell Sandish from comment #5) > I just did a completely fresh install of Tumbleweed on a spare NUC I have > here, and can confirm that the wifi configuration problem still exists. As David already commented, there were some issues I have solve recently. With version >= yast2-network-4.2.26 at least it should be written correctly, so, could you provide the written ifcfg-file and logs of the fresh installation to see what could be wrong there? In yast2-network-4.2.31 we have also solved some issue regarding the dialog initialization. That is, the wireless mode and auth-mode configured although read is not selected in the dialog when editing. > > Also, on a more minor note, the network installer fails to be able to use > Wifi. This bug has been present a few weeks. I needed to plug in an ethernet > cable to perform the installation. Ok, will test it, but as commented, logs and config files are appreciated just for check if it is a wrong configuration or something else.
(In reply to Russell Sandish from comment #5) > I just did a completely fresh install of Tumbleweed on a spare NUC I have > here, and can confirm that the wifi configuration problem still exists. > > Also, on a more minor note, the network installer fails to be able to use > Wifi. This bug has been present a few weeks. I needed to plug in an ethernet > cable to perform the installation. I tested with a recent release and also have problems configuring the WiFI, but not because of YaST settings. Tried configuring it through linuxrc and wicked is not able to bring up the interface.
(In reply to Knut Alejandro Anderssen González from comment #12) > (In reply to Russell Sandish from comment #5) > > I just did a completely fresh install of Tumbleweed on a spare NUC I have > > here, and can confirm that the wifi configuration problem still exists. > > > > Also, on a more minor note, the network installer fails to be able to use > > Wifi. This bug has been present a few weeks. I needed to plug in an ethernet > > cable to perform the installation. > > I tested with a recent release and also have problems configuring the WiFI, > but not because of YaST settings. Tried configuring it through linuxrc and > wicked is not able to bring up the interface. After testing it during a while, the current problems seems to be because of wpa_supplicant changes, it is using wpa_supplicant-2.9 since 20191111. as we can see in the repo https://download.opensuse.org/history/20191127/tumbleweed/repo/oss/x86_64/ I downloaded wpa_supplicant-2.6 and modified the iso with a dud, after killing wpa_supplicant and launching it again wicked is able to bring up the interface, so probably need to be adapted to cope with wpa_supplicant 2.9 changes. Assigning the bug to wicked team. Btw, Russel, if you found any specific YaST issue when writing the configuration in the ifcfg files just tell us and will try to handle it ASAP.
Re wicked not working, I just tried configuring wifi via wicked using a canned configuration, and now it does not work. When I first raised this issue, wicked would still work using a canned configuration, the problem was that yast2 failed to configure wicked. So it appears we have been hit by multiple bugs, or at least incompatibilities between different parts of the system. For now, I've fallen back to using NetworkManager, which I used to use up until about 6 months ago, when I discovered it had some problems with some Access Points, and switched to wicked. I'll zypper dup again in the next couple of days, and I'll post an update. If there's any logs you'd like to see, or other info please let me know, and I'll post them here. The syslog grepped for wicked has the following messages: Dec 02 10:34:35 zen systemd[1]: Starting wicked AutoIPv4 supplicant service... Dec 02 10:34:35 zen systemd[1]: Starting wicked DHCPv4 supplicant service... Dec 02 10:34:35 zen systemd[1]: Starting wicked DHCPv6 supplicant service... Dec 02 10:34:35 zen systemd[1]: Started wicked DHCPv4 supplicant service. Dec 02 10:34:35 zen systemd[1]: Started wicked DHCPv6 supplicant service. Dec 02 10:34:35 zen systemd[1]: Started wicked AutoIPv4 supplicant service. Dec 02 10:34:35 zen systemd[1]: Starting wicked network management service daemon... Dec 02 10:34:35 zen systemd[1]: Started wicked network management service daemon. Dec 02 10:34:35 zen systemd[1]: Starting wicked network nanny service... Dec 02 10:34:35 zen systemd[1]: Started wicked network nanny service. Dec 02 10:34:35 zen systemd[1]: Starting wicked managed network interfaces... Dec 02 10:34:35 zen dbus-daemon[880]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.823" (uid=0 pid=14145 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Dec 02 10:34:35 zen wickedd[14145]: ni_wpa_interface_bind(wlo1): Interrupted system call Dec 02 10:34:35 zen wickedd[14145]: wpa_supplicant doesn't know interface wlo1 Dec 02 10:34:35 zen wickedd-nanny[14147]: device wlo1: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure Dec 02 10:34:35 zen wickedd-nanny[14147]: wlo1: failed to bring up device, still continuing Dec 02 10:35:05 zen wicked[14148]: lo up Dec 02 10:35:05 zen wicked[14148]: wlo1 up Dec 02 10:35:05 zen wicked[14148]: enp0s20f0u1 no-device Dec 02 10:35:05 zen systemd[1]: Started wicked managed network interfaces. Dec 02 10:35:54 zen sudo[14652]: rks : TTY=pts/15 ; PWD=/home/rks ; USER=root ; COMMAND=/usr/sbin/wicked ifreload --ifconfig /home/rks/wifi/rapiscan.xml wlo1 Dec 02 10:35:54 zen dbus-daemon[880]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.823" (uid=0 pid=14145 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Dec 02 10:35:54 zen wickedd[14145]: ni_wpa_interface_bind(wlo1): Interrupted system call Dec 02 10:35:54 zen wickedd[14145]: wpa_supplicant doesn't know interface wlo1 Dec 02 10:35:54 zen dbus-daemon[880]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.823" (uid=0 pid=14145 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Dec 02 10:35:54 zen wickedd[14145]: ni_wpa_interface_bind(wlo1): Interrupted system call Dec 02 10:35:54 zen wickedd[14145]: wpa_supplicant doesn't know interface wlo1 Dec 02 10:35:54 zen wickedd-nanny[14147]: device wlo1: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure Dec 02 10:35:54 zen wickedd-nanny[14147]: wlo1: failed to bring up device, still continuing Dec 02 10:35:56 zen sudo[14663]: rks : TTY=pts/15 ; PWD=/home/rks ; USER=root ; COMMAND=/usr/sbin/wicked ifreload --ifconfig /home/rks/wifi/rapiscan.xml wlo1 Dec 02 10:35:56 zen wicked[14664]: ifreload: no configuration changes to reload Dec 02 10:36:07 zen sudo[14668]: rks : TTY=pts/15 ; PWD=/home/rks ; USER=root ; COMMAND=/usr/sbin/wicked ifreload --ifconfig /home/rks/wifi/rapiscan.xml wlo1 Dec 02 10:36:07 zen wicked[14669]: ifreload: no configuration changes to reload Dec 02 10:36:48 zen systemd[1]: Stopping wicked managed network interfaces... Dec 02 10:36:48 zen dbus-daemon[880]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.823" (uid=0 pid=14145 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Dec 02 10:36:48 zen wickedd[14145]: ni_wpa_interface_bind(wlo1): Interrupted system call Dec 02 10:36:48 zen wickedd[14145]: wpa_supplicant doesn't know interface wlo1 Dec 02 10:36:48 zen wicked[14839]: wlo1 device-ready Dec 02 10:36:48 zen systemd[1]: wicked.service: Succeeded. Dec 02 10:36:48 zen systemd[1]: Stopped wicked managed network interfaces. Dec 02 10:36:48 zen systemd[1]: Stopping wicked network nanny service... Dec 02 10:36:48 zen systemd[1]: wickedd-nanny.service: Succeeded. Dec 02 10:36:48 zen systemd[1]: Stopped wicked network nanny service. Dec 02 10:36:48 zen systemd[1]: Stopping wicked network management service daemon... Dec 02 10:36:48 zen systemd[1]: wickedd.service: Succeeded. Dec 02 10:36:48 zen systemd[1]: Stopped wicked network management service daemon. Dec 02 10:36:48 zen systemd[1]: Stopping wicked AutoIPv4 supplicant service... Dec 02 10:36:48 zen systemd[1]: Stopping wicked DHCPv4 supplicant service... Dec 02 10:36:48 zen systemd[1]: Stopping wicked DHCPv6 supplicant service... Dec 02 10:36:48 zen systemd[1]: wickedd-auto4.service: Succeeded. Dec 02 10:36:48 zen systemd[1]: Stopped wicked AutoIPv4 supplicant service. Dec 02 10:36:48 zen systemd[1]: wickedd-dhcp4.service: Succeeded. Dec 02 10:36:48 zen systemd[1]: Stopped wicked DHCPv4 supplicant service. Dec 02 10:36:48 zen systemd[1]: wickedd-dhcp6.service: Succeeded. Dec 02 10:36:48 zen systemd[1]: Stopped wicked DHCPv6 supplicant service.
Just tried a zypper dup. Machine is now running Tumbleweed 20191128. Yast2-network is 4.2.28. The problem is still outstanding, I cannot configure the network through Yast. The file /etc/sysconfig/network/ifcfg-wlp2s0 appears to be being updated correctly by yast2. Configuring using wicked using a previously saved wicked configuration no longer works - the network interface is just left in a down state. Since the wicked configuration file format is undocumented AFAICT, it is possible that the configuration format changed, and that my saved version is no longer recognisable by wicked. The only thing I can do is continue to use NetworkManager, which does work, however I have problems setting a static IP number using that technique, which I'd much rather do.
(In reply to Russell Sandish from comment #15) > Just tried a zypper dup. Machine is now running Tumbleweed 20191128. > Yast2-network is 4.2.28. The problem is still outstanding, I cannot > configure the network through Yast. The file > /etc/sysconfig/network/ifcfg-wlp2s0 appears to be being updated correctly by > yast2. Configuring using wicked using a previously saved wicked > configuration no longer works - the network interface is just left in a down > state. Since the wicked configuration file format is undocumented AFAICT, it > is possible that the configuration format changed, and that my saved version > is no longer recognisable by wicked. As commented in #13, the problem is that TW ships with wpa_supplicant 2.9, and wicked has to cope with the new API, but it is still not ready for that. I have assigned the bug to them because of that. > > The only thing I can do is continue to use NetworkManager, which does work, > however I have problems setting a static IP number using that technique, > which I'd much rather do.
Another week, another zypper dup. Now on VERSION="20191207" The yast2 configuration appears to get further, but ends up with an unnetworked state. Here's the relevant lines from syslog: Dec 10 17:55:14 rusnuc dbus-daemon[1033]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.41" (uid=0 pid=7440 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Dec 10 17:55:14 rusnuc wickedd[7440]: ni_wpa_interface_bind(wlp2s0): Interrupted system call Dec 10 17:55:14 rusnuc wickedd[7440]: wpa_supplicant doesn't know interface wlp2s0 Dec 10 17:55:14 rusnuc wicked[24002]: enp0s25 device-ready Dec 10 17:55:14 rusnuc wicked[24002]: wlp2s0 device-ready Dec 10 17:55:14 rusnuc systemd[1]: wicked.service: Succeeded. Dec 10 17:55:14 rusnuc systemd[1]: Stopped wicked managed network interfaces. Dec 10 17:55:14 rusnuc systemd[1]: Starting wicked managed network interfaces... Dec 10 17:55:14 rusnuc dbus-daemon[1033]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.41" (uid=0 pid=7440 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Dec 10 17:55:14 rusnuc wickedd[7440]: ni_wpa_interface_bind(wlp2s0): Interrupted system call Dec 10 17:55:14 rusnuc wickedd[7440]: wpa_supplicant doesn't know interface wlp2s0 Dec 10 17:55:14 rusnuc wickedd-nanny[7442]: device wlp2s0: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure Dec 10 17:55:44 rusnuc wicked[24023]: lo up Dec 10 17:55:44 rusnuc wicked[24023]: enp0s25 setup-in-progress Dec 10 17:55:44 rusnuc wicked[24023]: wlp2s0 device-not-running Dec 10 17:55:44 rusnuc systemd[1]: Started wicked managed network interfaces.
Another week and another dup. VERSION_ID="20191214" Yast2 still fails to bring up the wireless interface. Syslog reports: Dec 18 09:24:58 rusnuc systemd[1]: Reloading wicked managed network interfaces. Dec 18 09:24:58 rusnuc dbus-daemon[1030]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.41" (uid=0 pid=4715 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Dec 18 09:24:58 rusnuc wickedd[4715]: ni_wpa_interface_bind(wlp2s0): Interrupted system call Dec 18 09:24:58 rusnuc wickedd[4715]: wpa_supplicant doesn't know interface wlp2s0 Dec 18 09:24:58 rusnuc kernel: wlp2s0: deauthenticating from ec:08:6b:89:22:b4 by local choice (Reason: 3=DEAUTH_LEAVING) Dec 18 09:24:58 rusnuc dbus-daemon[1030]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.41" (uid=0 pid=4715 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Dec 18 09:24:58 rusnuc wickedd[4715]: ni_wpa_interface_bind(wlp2s0): Interrupted system call Dec 18 09:24:58 rusnuc wickedd[4715]: wpa_supplicant doesn't know interface wlp2s0 Dec 18 09:24:58 rusnuc wickedd-nanny[4717]: device wlp2s0: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure Dec 18 09:24:58 rusnuc wicked[21979]: wlp2s0 device-ready Dec 18 09:24:58 rusnuc wicked[21979]: wlp2s0 device-not-running Dec 18 09:24:58 rusnuc systemd[1]: Reloaded wicked managed network interfaces. Back to using NetworkManager. Which is not ideal, as dhcp continuously overrides my static IP no, and I am unable to access Wifi 4 (aka 802.11ac) services with NetworkManager.
Another week, another dup. Now at VERSION_ID="20191216" No change to status.
Another dup, and still yast2/wicked does not work with wifi. Attached is syslog when I try: Jan 13 19:53:20 zen systemd-udevd[2625]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jan 13 19:53:20 zen systemd-udevd[2624]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. Jan 13 19:53:21 zen systemd[1]: Reloading wicked managed network interfaces. Jan 13 19:53:21 zen dbus-daemon[1203]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=0 pid=1304 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Jan 13 19:53:21 zen wickedd[1304]: ni_wpa_interface_bind(wlo1): Interrupted system call Jan 13 19:53:21 zen wickedd[1304]: wpa_supplicant doesn't know interface wlo1 Jan 13 19:53:22 zen ModemManager[1363]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin Jan 13 19:53:51 zen wicked[2641]: device enp0s20f0u1: operation timed out Jan 13 19:53:51 zen dbus-daemon[1203]: [system] Rejected send message, 1 matched rules; type="method_call", sender=":1.13" (uid=0 pid=1304 comm="/usr/sbin/wickedd --systemd --foreground ") interface="fi.epitest.hostap.WPASupplicant" member="getInterface" error name="(unset)" requested_reply="0" destination="fi.epitest.hostap.WPASupplicant" (bus) Jan 13 19:53:51 zen wickedd[1304]: ni_wpa_interface_bind(wlo1): Interrupted system call Jan 13 19:53:51 zen wickedd[1304]: wpa_supplicant doesn't know interface wlo1 Jan 13 19:53:51 zen wickedd-nanny[1364]: device wlo1: call to org.opensuse.Network.Wireless.changeDevice() failed: General failure Jan 13 19:53:51 zen wickedd-nanny[1364]: wlo1: failed to bring up device, still continuing Jan 13 19:54:21 zen wicked[2641]: wlo1 device-ready Jan 13 19:54:21 zen wicked[2641]: wlo1 device-not-running Jan 13 19:54:21 zen wicked[2641]: enp0s20f0u1 no-device Jan 13 19:54:21 zen systemd[1]: Reloaded wicked managed network interfaces.
Hi Russell, Knut is right, the reason why wireless (while using wicked) is not working on TW right now is the upgrade to wpa_supplicant 2.9 -> see https://bugzilla.suse.com/show_bug.cgi?id=1156920 To summarize, wicked needs to be updated to use the new wpa_supplicant dbus API, as the old one was removed in 2.8 (TW package was upgraded a few weeks ago from 2.6 to 2.9). We are working on it already and will report as soon as we have some progress.
*** Bug 1160711 has been marked as a duplicate of this bug. ***
(In reply to Knut Alejandro Anderssen González from comment #22) > *** Bug 1160711 has been marked as a duplicate of this bug. *** Maybe not, because i had try to connect to wifi network without any passwords.
@Igor: wpa_supplicant is also used in such case; it is indeed a duplicate.
Marking as duplicate of https://bugzilla.suse.com/show_bug.cgi?id=1156920 as both issues are caused due to the usage of wpa_supplicant 2.9 *** This bug has been marked as a duplicate of bug 1156920 ***