For SHA384 based 11r AKMs below: FT-FILS-SHA384, FT-SUITEB-SHA384, the FT MIC length is 24. But the host driver has MIC length hardcoded as 16, so only first 16 bytes of MIC is copied into MIC field and the rest 8 bytes are copied into R1KH-ID. This results in R1KH-ID and R0KH-ID parse failure. Due to this, the host driver sends R0KH-ID as 0 to the firmware in the R0KH-ID. So the next roaming fails in the firmware. For SHA384 based AKMs, add changes to reparse the association/ reassociation response FT element. Introduce new FTIE structure with MIC defined as array of 24 bytes. With this, the R0KH-ID and R1KH-ID will be populated correctly in to the assoc response structure and ultimately RSO command will carry the right R0KH-ID to firmware. Change-Id: I5aa50145fcd3ba91b1c92d4817b7f0e4fc216e3f CRs-Fixed: 2430828 |
||
---|---|---|
.. | ||
bmi | ||
cds | ||
dp | ||
hdd | ||
mac | ||
pld | ||
sap | ||
sme | ||
wma |