[PATCH] ft: defer PTK installation for unassociated AP clients
Christopher Griffin
christophergriffin05 at gmail.com
Sat Nov 14 06:45:03 PST 2026
(In reply to the patch of 18 Oct, which my mailbox doesn't hold, so
this may not thread.)
Hi Giuseppe,
I tested this patch on hardware, including the PMF re-add case. It
also supersedes my patch "FT: Configure the PTK after association with
full AP client state" (4 Nov), which went after the same error but left
the re-add case out. Jouni, please drop mine in favour of this one.
Setup: an Arista W-118 (IPQ4019, ath10k, mac80211) on OpenWrt main with
hostapd 831364bf.
- AP A: an FT-PSK BSS on the 5 GHz radio.
- AP B: a separate hostapd process on the 2.4 GHz radio, with the same
SSID and mobility domain and ft_psk_generate_local=1. Being a
separate process, B doesn't prune A's association, so the two act
like separate APs.
- Both use ieee80211w=2.
- The station is wpa_supplicant on the board's QCA9882, using FT-PSK
with ieee80211w=2. It roams over the air with ROAM every 6 s,
A -> B -> A, so every return reaches an AP that still holds its
authorized PMF association and goes through ap_sta_re_add().
With my patch: 8 of 8 roams completed, and all 7 re-add returns logged
"nl80211: kernel reports: key addition failed".
With yours: 8 of 8 roams completed, 8 re-add returns, no error. After
the last return, the station was authorized with MFP and its CCMP
pairwise key was in mac80211. A ping from the station moved that key's
RX PN from 4 to 11, so the key configured by the post-association retry
carries the data.
Tested-by: Christopher Griffin <christophergriffin05 at gmail.com>
OpenWrt now carries your patch in place of mine:
https://github.com/openwrt/openwrt/pull/26652
The tests and this report were done with Claude, an AI coding
assistant.
Christopher
More information about the Hostap
mailing list