我在连接专用 6 GHz 网络时遇到问题。过去,我升级到最新的 Ubuntu 22.04 LTS 内核版本以获取有效的固件。之后,我现在可以看到所有需要的通道,包括 2,4/5/6 GHz,就像它应该的那样:
root@cloud:/etc# iw reg get
global
phy#0 (self-managed)
country DE: DFS-UNSET
(2402 - 2437 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40MINUS, NO-80MHZ, NO-160MHZ
(2422 - 2462 @ 40), (6, 22), (N/A), AUTO-BW, NO-80MHZ, NO-160MHZ
(2447 - 2482 @ 40), (6, 22), (N/A), AUTO-BW, NO-HT40PLUS, NO-80MHZ, NO-160MHZ
(5170 - 5190 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN
(5190 - 5210 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN
(5210 - 5230 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN
(5230 - 5250 @ 160), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN
...
...
(6325 - 6345 @ 480), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN
(6345 - 6365 @ 480), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN
(6365 - 6385 @ 480), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN
(6385 - 6405 @ 480), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40PLUS, PASSIVE-SCAN
(6405 - 6425 @ 480), (6, 22), (N/A), NO-OUTDOOR, AUTO-BW, IR-CONCURRENT, NO-HT40MINUS, PASSIVE-SCAN
乍一看配置似乎没问题。我在内核上运行6.2.0-36-通用#37~22.04.1-Ubuntu和核心72。如果我尝试连接到 2.4/5 GHz,一切都会按预期进行:
root@cloud:/etc# wpa_supplicant -c /etc/wpa_supplicant.conf -i wlp2s0
Successfully initialized wpa_supplicant
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=DE
wlp2s0: SME: Trying to authenticate with e4:38:83:43:62:fa (SSID='J.A.R.V.I.S.' freq=5200 MHz)
wlp2s0: Trying to associate with e4:38:83:43:62:fa (SSID='J.A.R.V.I.S.' freq=5200 MHz)
wlp2s0: Associated with e4:38:83:43:62:fa
wlp2s0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
wlp2s0: WPA: Key negotiation completed with e4:38:83:43:62:fa [PTK=CCMP GTK=CCMP]
wlp2s0: CTRL-EVENT-CONNECTED - Connection to e4:38:83:43:62:fa completed [id=0 id_str=]
...
^Cp2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
p2p-dev-wlp2s0: CTRL-EVENT-TERMINATING
wlp2s0: CTRL-EVENT-DISCONNECTED bssid=e4:38:83:43:62:fa reason=3 locally_generated=1
wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
wlp2s0: CTRL-EVENT-TERMINATING
但如果我尝试连接到我的专用 6 GHz 网络,连接就会卡住:
Successfully initialized wpa_supplicant
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
wlp2s0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=DE
...
^Cp2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
p2p-dev-wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
nl80211: deinit ifname=p2p-dev-wlp2s0 disabled_11b_rates=0
p2p-dev-wlp2s0: CTRL-EVENT-TERMINATING
wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
wlp2s0: CTRL-EVENT-DSCP-POLICY clear_all
nl80211: deinit ifname=wlp2s0 disabled_11b_rates=0
wlp2s0: CTRL-EVENT-TERMINATING
所以需要你的帮助来弄清楚,这种“不连接”的根本原因是什么。
答案1
与此同时,我和另一位专家一起找到了解决方案。似乎“wpa_supplicant”不会自动在 6 GHz 网络上使用 WPA3,并尝试使用在该信道上不起作用的 WPA/WPA2。
因此我将配置更改为所需的最少部分:
root@cloud:/# cat /etc/wpa_supplicant/wpa_supplicant.conf
network={
ssid="<my network>"
key_mgmt=SAE
sae_password="<my password>"
ieee80211w=2
}