From 7f81ab9bbbe99dc2debf77a57278903582c3302f Mon Sep 17 00:00:00 2001 From: James Prestwood Date: Thu, 15 Sep 2022 15:07:29 -0700 Subject: [PATCH] station: don't set OCVC for FT AKMs Using OCV in FT is now disabled, so if the AKM is FT don't set the capability or AP's may reject FT attempts. --- src/station.c | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/src/station.c b/src/station.c index 4faac050..79d2c755 100644 --- a/src/station.c +++ b/src/station.c @@ -1110,9 +1110,15 @@ build_ie: * seen that they do not include the OCI in the 4-way handshake yet * still advertise the capability. Because of this OCV is disabled if * any offload features are detected (since IWD prefers to use offload). + * + * TODO: For now OCV is disabled if the network is FT capable. This is + * being done until support in the kernel is added to + * automatically include the OCI element for the association + * request. */ info.ocvc = !disable_ocv && bss_info.ocvc && info.mfpc && - !wiphy_can_offload(wiphy); + !wiphy_can_offload(wiphy) && + !IE_AKM_IS_FT(info.akm_suites); /* * IEEE 802.11-2020 9.4.2.24.4 states extended key IDs can only be used