Hi @retob,
Thanks for moving the topic to the forum. By this way, we could also have a chance to help others who have similar problems.
I’m quite surprised that 3rd option (hack) did not work. I believe, it might be due to the missing freq_list variables. I made a quick check on my machine by using the wpa_cli tool. E.g.
sudo wpa_cli
> interface wlan0
> scan
wait a little bit since the request is async.
> scan_results
As a result, I got something like that;
bssid / frequency / signal level / flags / ssid
68:a0:3e:93:47:2f 5260 -38 [WPA2-PSK-CCMP][WPS][ESS] SUPERBOX_Wi-Fi_472B
6a:a0:3e:93:47:21 5260 -38 [WPA2-PSK-CCMP][ESS] \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
68:a0:3e:93:47:2b 2432 -31 [WPA2-PSK-CCMP][WPS][ESS] SUPERBOX_Wi-Fi_472B
74:45:2d:ce:dc:d0 2437 -76 [WPA2-PSK-CCMP][WPS][ESS] JONNYLE\xc5\x9e
88:41:fc:31:da:6e 2412 -82 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][WPS][ESS] AirTies_Air5750_D66Y
08:26:97:1c:46:a2 2417 -83 [WPA-PSK-CCMP+TKIP][WPA2-PSK-CCMP+TKIP][WPS][ESS] TurkTelekom_ZMR4N
6a:54:4b:63:69:29 2447 -66 [WPA2-PSK-CCMP+TKIP][ESS] ZyXEL_3
c8:54:4b:63:69:2b 2447 -67 [WPA2-PSK-CCMP+TKIP][WPS][ESS] BugraAydogar
6a:54:4b:63:69:2a 2447 -69 [WPA2-PSK-CCMP+TKIP][ESS] ZyXEL_4
6a:54:4b:63:69:28 2447 -46 [WPA2-PSK-CCMP+TKIP][ESS] ZyXEL_2
60:14:66:fc:29:72 2462 -75 [WPA2-PSK-CCMP][WPS][ESS] turkcellWifi_1411
As you can see, I never get a 2457 as a fundamental frequency. Please see the following link for the details. Maybe, this is somehow related with your issue. Also, please provide the logs of the wpa_supplicant by using sudo journalctl -u wpa_supplicant.service --no-pager.
https://en.wikipedia.org/wiki/List_of_WLAN_channels#2.4_GHz_(802.11b/g/n/ax)
Alternatively, there are two additional potential solutions;
-
Using the wpa_applicant’s scanning functionality available under https://w1.fi/wpa_supplicant/devel/dbus.html#dbus_interface and it allows passing a parameter called
Channels. -
I have seen that there is
NM_WIFI_DEVICE_CAP_FREQ_5GHZvariable under theNMDeviceWifiCapabilitiesenum. I am not really sure, if there is a way to disable this when the interface is created but keep it also in mind for further investigation. https://developer-old.gnome.org/NetworkManager/stable/nm-dbus-types.html#NMDeviceWifiCapabilities
These are the all options that I can think of currently. Do you guys have any suggestions @ogra, @abeato?