[Bug 1157394] New: Configuring wifi interface via yast2 not working

newer
[Bug 1160711] netinstall did not...

older
[Bug 1159883] [wish] Remember tabs...

bugzilla_noreply＠novell.com

20 Nov 2019 20 Nov '19

23:02

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 Bug ID: 1157394 Summary: Configuring wifi interface via yast2 not working Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 Assignee: yast2-maintainers@suse.de Reporter: hpcoder@hpcoders.com.au QA Contact: jsrain@suse.com Found By: --- Blocker: --- 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. -- You are receiving this mail because: You are on the CC list for the bug.

Attachments:

attachment.htm (text/html — 3.3 KB)

Show replies by thread

bugzilla_noreply＠novell.com

22 Nov 22 Nov

06:16

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c2 --- Comment #2 from Russell Sandish --- Created attachment 824732 --> http://bugzilla.opensuse.org/attachment.cgi?id=824732&action=edit y2logs as requested -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

08:28

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 David Diaz changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(hpcoder@hpcoders. | |com.au) | -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:04

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c3 Knut Alejandro Anderssen González changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |knut.anderssen@suse.com Flags| |needinfo?(hpcoder@hpcoders. | |com.au) --- Comment #3 from Knut Alejandro Anderssen González --- (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? -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

23 Nov 23 Nov

01:15

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c4 --- Comment #4 from Russell Sandish --- 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... -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

25 Nov 25 Nov

07:11

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c5 --- Comment #5 from Russell Sandish --- 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. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10:35

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c6 --- Comment #6 from David Diaz --- 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? -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

12:24

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c7 --- Comment #7 from Knut Alejandro Anderssen González --- (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.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

13:49

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c8 --- Comment #8 from Knut Alejandro Anderssen González --- 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. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

26 Nov 26 Nov

03:22

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c9 --- Comment #9 from Russell Sandish --- @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. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:06

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c10 David Diaz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Flags|needinfo?(hpcoder@hpcoders. | |com.au) | --- Comment #10 from David Diaz --- (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 -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

30 Nov 30 Nov

14:24

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 Manu Maier changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mmanu84@outlook.de -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

1 Dec 1 Dec

23:49

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c14 --- Comment #14 from Russell Sandish --- 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. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

3 Dec 3 Dec

00:13

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c15 --- Comment #15 from Russell Sandish --- 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. -- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

09:49

New subject: [Bug 1157394] Configuring wifi interface via yast2 not working

http://bugzilla.opensuse.org/show_bug.cgi?id=1157394 http://bugzilla.opensuse.org/show_bug.cgi?id=1157394#c16 --- Comment #16 from Knut Alejandro Anderssen González --- (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.

-- You are receiving this mail because: You are on the CC list for the bug.

bugzilla_noreply＠novell.com

10 Dec 10 Dec