2062785 – [NMCI] simwifi_ap_wpa_psk_method_shared and simwifi_ap_in_bridge_wpa_psk_method_manual regressed again due to channel issue

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2062785 - [NMCI] simwifi_ap_wpa_psk_method_shared and simwifi_ap_in_bridge_wpa_psk_method_manual regressed again due to channel issue

Summary: [NMCI] simwifi_ap_wpa_psk_method_shared and simwifi_ap_in_bridge_wpa_psk_meth...

Keywords:
Status:	CLOSED CURRENTRELEASE
Alias:	None
Product:	Red Hat Enterprise Linux 9
Classification:	Red Hat
Component:	NetworkManager
Sub Component:
Version:	9.1
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	Beniamino Galvani
QA Contact:	Desktop QE
Docs Contact:
URL:
Whiteboard:
Depends On:	2032539
Blocks:
TreeView+	depends on / blocked

Reported:	2022-03-10 15:26 UTC by Vladimir Benes
Modified:	2022-03-14 08:24 UTC (History)
CC List:	10 users (show)
Fixed In Version:
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:	2032539
Environment:
Last Closed:	2022-03-14 08:24:31 UTC
Type:	Bug
Target Upstream Version:
Embargoed:
Dependent Products:

Attachments	(Terms of Use)

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Issue Tracker	RHELPLAN-115221	0	None	None	None	2022-03-10 15:35:50 UTC
freedesktop.org Gitlab	NetworkManager NetworkManager merge_requests 1142	0	None	opened	wifi: ignore disabled frequencies	2022-03-10 17:20:13 UTC

Description Vladimir Benes 2022-03-10 15:26:46 UTC

We are seeing regression in those two ap tests again. A workaround is to add 802-11-wireless.channel 1 802-11-wireless.band bg to profile creation.

Version:
NetworkManager-1.37.0-29798.copr.38290b1b86.el9.x86_64 (not exactly this one, no older available)


reproducer:
0. modprobe mac80211_hwsim
1. nmcli  connection add type wifi ifname wlan1 con-name wifi-ap ssid AP_test 802-11-wireless-security.key-mgmt wpa-psk 802-11-wireless-security.psk Secret123 mode ap ipv4.method shared

The profile should be connected instantly but stays in:
wlan1          wifi      connecting (configuring)  wifi-ap    

logs:
Mar 10 10:13:38 gsm-r5s7-01.wlan.rhts.eng.bos.redhat.com wpa_supplicant[94938]: nl80211: kernel reports: Channel is disabled
Mar 10 10:13:38 gsm-r5s7-01.wlan.rhts.eng.bos.redhat.com wpa_supplicant[94938]: nl80211: Failed to set channel (freq=2472): -22 (Invalid argument)


full log attached

Comment 4 Vladimir Benes 2022-03-10 15:32:16 UTC

git revert 3f96fe734a2c1bb616052c289213a8d3418cb29b should revert to buggy behavior

Comment 5 Beniamino Galvani 2022-03-10 16:34:26 UTC

Since https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/f18bf17deaa5ccdc445c33d7e9a0334f1de399a6 , the hotspot channel is randomized when not explicitly set.

For SSID "AP_test", frequency 2472 is choosen, since it's reported as supported by the driver.

# iw reg get
global
country 00: DFS-UNSET
        (2402 - 2472 @ 40), (N/A, 20), (N/A)
        (2457 - 2482 @ 20), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (2474 - 2494 @ 20), (N/A, 20), (N/A), NO-OFDM, PASSIVE-SCAN
        (5170 - 5250 @ 80), (N/A, 20), (N/A), AUTO-BW, PASSIVE-SCAN
        (5250 - 5330 @ 80), (N/A, 20), (0 ms), DFS, AUTO-BW, PASSIVE-SCAN
        (5490 - 5730 @ 160), (N/A, 20), (0 ms), DFS, PASSIVE-SCAN
        (5735 - 5835 @ 80), (N/A, 20), (N/A), PASSIVE-SCAN
        (57240 - 63720 @ 2160), (N/A, 0), (N/A)

However, that frequency fails to be set:

# iw phy1 set freq 2472
kernel reports: Channel is disabled
command failed: Invalid argument (-22)

I don't know why...

Comment 6 Beniamino Galvani 2022-03-10 16:37:34 UTC

With "iw phy phy1 info" I see:

                Frequencies:                                                                                           
                        * 2412 MHz [1] (30.0 dBm)                                                                      
                        * 2417 MHz [2] (30.0 dBm)                                                                      
                        * 2422 MHz [3] (30.0 dBm)                                                                      
                        * 2427 MHz [4] (30.0 dBm)                                                                      
                        * 2432 MHz [5] (30.0 dBm)                                                                      
                        * 2437 MHz [6] (30.0 dBm)                                                                      
                        * 2442 MHz [7] (30.0 dBm)                                                                      
                        * 2447 MHz [8] (30.0 dBm)                                                                                                                                                                                             
                        * 2452 MHz [9] (30.0 dBm)
                        * 2457 MHz [10] (30.0 dBm)
                        * 2462 MHz [11] (30.0 dBm)
                        * 2467 MHz [12] (disabled)
                        * 2472 MHz [13] (disabled)
                        * 2484 MHz [14] (disabled)

So, apparently the list of supported frequencies populated in nm_wifi_utils_nl80211_new() is not correct.

Comment 7 Thomas Haller 2022-03-11 09:00:41 UTC

the bug existed for a long time, but it became only relevant since commit [1].

Vladimir, above patch was merged mid/end of February, but the CI only fails since 8th March. Do you know why that might be, and why it wasn't caught earlier?
[2] is the CI test for the merge-request that introduced [1].


[1] https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/f18bf17deaa5ccdc445c33d7e9a0334f1de399a6.
[2] https://desktopqe-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/beaker-NetworkManager-gitlab-trigger-code-upstream/3114/artifact/artifacts/



What [1] does, it starts automatically choosing a channel, by hashing the SSID (the same should be chosen independently of architecture/host).
So we are lucky that NM-ci used a SSID that exposed the problem. But why only since 8th March?

Comment 8 Thomas Haller 2022-03-11 09:05:32 UTC

ah, on main-veth-rhel7 they were failing earlier...

to bad, this should have been discovered earlier.

But the gitlab-ci integrated tests still pass (why?). Which is the one that we mostly look at.

Comment 9 Beniamino Galvani 2022-03-14 08:24:31 UTC

Fixed on main branch.

Note You need to log in before you can comment on or make changes to this bug.