wlan: Don't disconnect in case of HS2.0 for change in AP capability.
After connection, driver process beacon to detect any change in
AP's capabilities. Currently if privacy bit is set in beacon and
if rsn or wpa bit is not set, driver issues disconnect command.
In case of HS2.0, all security capabilities are part of vendor
specific information. Hence, both wpa and rsn bit is 0, though
privacy bit is set. Since driver considers it as a change in AP
security params, it issues disconnect. As a part of fix, make sure
that for OSEN capabilities disconnect is not issued.
Change-Id: I5554b24dfa2724c6c9b6faef2f738277e42028fb
CRs-Fixed: 796397
diff --git a/CORE/MAC/src/pe/lim/limApi.c b/CORE/MAC/src/pe/lim/limApi.c
index 953ab26..07461c9 100644
--- a/CORE/MAC/src/pe/lim/limApi.c
+++ b/CORE/MAC/src/pe/lim/limApi.c
@@ -1818,6 +1818,19 @@
(pSession->encryptType == eSIR_ED_AES_128_CMAC)))
return eSIR_TRUE;
+ /* For HS2.0, RSN ie is not present
+ * in beacon. Therefore no need to
+ * check for security type in case
+ * OSEN session.
+ */
+ /*TODO: AP capability mismatch
+ * is not checked here because
+ * no logic for beacon parsing
+ * is avilable for HS2.0.
+ */
+ if (pSession->bOSENAssociation)
+ return eSIR_TRUE;
+
return eSIR_FALSE;
}