OPINIONATED OMARCHY
TROUBLESHOOTING CORPUS
790
RECORDS
790
AUDITED
0
UNCHECKED
2388
SOURCES
LIVE
network high common DISPUTE

Connect to a WPA3-SAE or mixed WPA2/WPA3 network that refuses to associate

omarchyarchendeavouroscachyosmanjarolaptopdesktop
AUDITED Audited against its sources and confirmed accurate.
AUDIT NOTE

Every specific is correct and traceable to the cited sources. I checked the version-sensitive ones rather than trusting memory. https://networkmanager.dev/docs/api/latest/settings-802-11-wireless-security.html defines key-mgmt values exactly as the record uses them, with \"wpa-psk\" documented as \"(WPA2 + WPA3 personal)\" and \"sae\" as \"(WPA3 personal only)\", defines pmf as "0 (default), 1 (disable), 2 (optional), 3 (required)", matching the record character for character, and confirms the psk property carries the SAE passphrase ("The WPA3-Personal networks use a passphrase of any length for SAE authentication"), so setting .psk alongside key-mgmt sae is right and not a confusion of PSK with SAE. The bare-supplicant half is lifted faithfully from https://wiki.archlinux.org/title/Wpa_supplicant: its "Connections to pure WPA3-SAE access points" section is key_mgmt=SAE / sae_password="the.literal.wifi.password" / ieee80211w=2, its "Connections to mixed WPA2-PSK/WPA3-SAE access points" section is key_mgmt=WPA-PSK-SHA256 / psk= / ieee80211w=2, it gives the same sae_pwe=2 global for H2E-only APs, and its "Hardware 802.11w support" section is literally iw phy phy0 info | grep 00-0f-ac:6. I had reservations about WPA-PSK-SHA256 against transition-mode APs that advertise plain WPA-PSK plus SAE, but the record is reporting its cited source accurately, which is the standard being applied here. I also confirmed on this machine that Arch's wpa_supplicant@.service runs -c/etc/wpa_supplicant/wpa_supplicant-%I.conf -i%I, so the config path and unit name in the fix are exactly right, and that nmcli -f GENERAL.STATE,802-11-wireless-security.key-mgmt connection show --active <name> is accepted syntax. Nothing Omarchy-3 shaped, no pacman calls at all, no -Sy. Two cosmetic notes for a future revision: wlan0 and phy0 are hardcoded where Omarchy will normally have wlp*, and the bare-wpa_supplicant path should say to stop NetworkManager first, since running both against the same interface will fight.

Symptom

A network the phone joins fine will not connect from Linux. With wpa_supplicant directly you get wlan0: No PSK available for association followed by wlan0: SME: Failed to set WPA key management and encryption suites. Through NetworkManager it fails with Error: Connection activation failed: (7) Secrets were required, but not provided even though the password is correct, or it associates and immediately deauthenticates. wpa_cli scan_results shows the network flagged [WPA2-SAE-CCMP][ESS] or [WPA2-PSK+SAE-CCMP].

Cause

WPA3 Personal is SAE, not PSK. A WPA3-only AP needs key_mgmt=SAE with a literal sae_password=. A psk= line is simply not a credential SAE can use, hence "No PSK available". WPA3 also mandates Protected Management Frames (802.11w), so the connection fails unless PMF is negotiated. Mixed WPA2-PSK/WPA3-SAE "transition mode" APs are worse: the client has to pick the right key-mgmt suite and agree on PMF as *optional*, and a profile that hard-requires either mode fails against the other. Some APs are additionally configured for hash-to-element (H2E) only, which the supplicant will not use unless told to.

Fix

Find out what the AP is actually offering:


sudo wpa_cli -i wlan0 scan
sudo wpa_cli -i wlan0 scan_results | grep -i '<your-ssid>'
# [WPA2-SAE-CCMP]      -> WPA3 only
# [WPA2-PSK+SAE-CCMP]  -> transition mode

Check the card can do PMF at all:


iw phy phy0 info | grep 00-0f-ac:6     # any output means MFP/PMF is supported

**With NetworkManager (the normal case).** For a WPA3-only network:


nmcli connection modify "<SSID>" \
  802-11-wireless-security.key-mgmt sae \
  802-11-wireless-security.psk '<the literal wifi password>' \
  802-11-wireless-security.pmf 3
nmcli connection up "<SSID>"

For a mixed WPA2/WPA3 transition-mode network, use wpa-psk (which NetworkManager documents as "WPA2 + WPA3 personal") and leave PMF optional. This is the combination that works against both halves of the AP:


nmcli connection modify "<SSID>" \
  802-11-wireless-security.key-mgmt wpa-psk \
  802-11-wireless-security.pmf 2
nmcli connection up "<SSID>"

NetworkManager's pmf values are 0 default, 1 disable, 2 optional, 3 required. If an old AP breaks when PMF is even offered, pmf 1 disables it outright.

**With bare wpa_supplicant.** WPA3-only:


# /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
ctrl_interface=/run/wpa_supplicant
update_config=1
sae_pwe=2

network={
  ssid="<SSID>"
  key_mgmt=SAE
  sae_password="the.literal.wifi.password"
  ieee80211w=2
}

Mixed WPA2-PSK/WPA3-SAE:


network={
  ssid="<SSID>"
  key_mgmt=WPA-PSK-SHA256
  psk="the.literal.wifi.password"
  ieee80211w=2
}

sae_pwe=2 in the global section enables both hash-to-element and hunt-and-peck, which is required against APs configured for H2E only. ieee80211w is 0 disabled, 1 optional, 2 required.

Then:


sudo systemctl restart wpa_supplicant@wlan0.service
# or, to watch it fail loudly:
sudo wpa_supplicant -d -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf

If you use iwd as the backend instead, it supports WPA3 Personal natively and generally needs no key-mgmt configuration at all, so it is worth trying as a straight A/B test.

Verify

nmcli -f GENERAL.STATE,802-11-wireless-security.key-mgmt connection show --active "<SSID>" shows the connection active. iw dev wlan0 link reports the BSS and no repeated re-association. With wpa_supplicant running in the foreground you should see CTRL-EVENT-CONNECTED rather than No PSK available for association.

Sources

wpa3-sae-association-fails-no-psk-available