]> git.ipfire.org Git - thirdparty/hostap.git/commit
Allow MLO disabled connection to legacy open/WPA2-Personal-only AP MLDs
authorVeerendranath Jakkam <quic_vjakkam@quicinc.com>
Thu, 23 Mar 2023 13:33:01 +0000 (19:03 +0530)
committerJouni Malinen <j@w1.fi>
Tue, 25 Apr 2023 14:04:44 +0000 (17:04 +0300)
commit8bc84fceeb41f88a627fcc30f81e81ceca40e3fb
tree5957370222c595aaf8a0ec0585b38273e8404851
parentb9c3b57a99e824c1e3beeed9695d1cdfb83eb45b
Allow MLO disabled connection to legacy open/WPA2-Personal-only AP MLDs

wpa_supplicant was skipping MLD APs from network selection when the AP
advertise legacy open, WPA2-Personal-only (PSK without SAE), or PMF
disabled. However, there are already some early Wi-Fi 7 APs in the
market which advertise legacy open, WPA2-Personal-only, or PMF disabled
even though these combinations are unlikely to be allowed for Wi-Fi 7 in
the end.

To avoid connectivity issues with such APs, allow stations to connect
with MLO disabled when an AP MLD is detected to advertise legacy open,
WPA2-Personal-only (PSK without SAE), or PMF disabled.

This reverts commit 7d8b96dcfdbb ("wpa_supplicant: Apply same
restrictions for MLD as for 6 GHz BSS") except WEP and TKIP checks,
i.e., AP MLDs which advertise only WEP or TKIP are still skipped from
network selection.

For the SME-in-wpa_supplicant case, skip configuring MLD parameters to
the driver if the STA can connect only in legacy open,
WPA2-Personal-only, or PMF disabled mode. For the SME-in-driver case, it
is the driver's responsibility to initiate connection with MLO disabled
with such APs.

Signed-off-by: Veerendranath Jakkam <quic_vjakkam@quicinc.com>
wpa_supplicant/events.c
wpa_supplicant/sme.c