diff options
| author | Fiona Klute <fiona.klute@gmx.de> | 2024-01-09 10:59:26 +0100 |
|---|---|---|
| committer | Denis Kenzior <denkenz@gmail.com> | 2024-01-09 21:32:28 -0600 |
| commit | a6638513d47cefa5c941789de898b8c36d7fc49c (patch) | |
| tree | 3d5a533918f4d00903a99af903dfcabc8c3fe00b | |
| parent | 5abf54f2dc620192672d055d65949db6687e2177 (diff) | |
Log falling back from SAE to WPA2
I've had connections to a WPA3-Personal only network fail with no log
message from iwd, and eventually figured out to was because the driver
would've required using CMD_EXTERNAL_AUTH. With the added log messages
the reason becomes obvious.
Additionally the fallback may happen even if the user explicitly
configured WPA3 in NetworkManager, I believe a warning is appropriate
there.
| -rw-r--r-- | src/wiphy.c | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/src/wiphy.c b/src/wiphy.c index 766df3487..3258b761a 100644 --- a/src/wiphy.c +++ b/src/wiphy.c @@ -248,6 +248,9 @@ static bool wiphy_can_connect_sae(struct wiphy *wiphy) * * TODO: No support for CMD_EXTERNAL_AUTH yet. */ + l_warn("SAE unsupported: %s needs CMD_EXTERNAL_AUTH for SAE", + wiphy->driver_str); + return false; } @@ -312,8 +315,10 @@ enum ie_rsn_akm_suite wiphy_select_akm(struct wiphy *wiphy, if (ie_rsne_is_wpa3_personal(info)) { l_debug("Network is WPA3-Personal..."); - if (!wiphy_can_connect_sae(wiphy)) + if (!wiphy_can_connect_sae(wiphy)) { + l_debug("Can't use SAE, trying WPA2"); goto wpa2_personal; + } if (info->akm_suites & IE_RSN_AKM_SUITE_FT_OVER_SAE_SHA256) |