dfba36b6f6
Userspace may send RSNXE also in connect request irrespective of the connecting AP capabilities. This allows the driver to choose best candidate based on score. But the chosen candidate may not support the RSNXE features and may not advertise RSNXE in beacon/probe response. Station is not supposed to include the RSNX IE in assoc request in such cases as legacy APs may misbehave due to the new IE. It's observed that few legacy APs which don't support the RSNXE reject the connection at EAPOL stage. So, strip the IE when below conditions are met to avoid sending the RSNXE to legacy APs, 1. If AP doesn't support/advertise the RSNXE 2. If the connection is legacy than WPA3 mode 3. If no other bits are set than SAE_H2E, SAE_PK, SECURE_LTF, SECURE_RTT, PROT_RANGE_NEGOTIOATION in RSNXE capabilities field. This is a continuation to the partial fix Ia7dee29792718a6514da44b13b36b46586ef25ab (which is reverted as it's not a complete fix). Change-Id: Ib857e9358a5414841002966ca14bdbb30d6587c6 CRs-Fixed: 3255353
This is CNSS WLAN Host Driver for products starting from iHelium