- Add support for WPA3 + WPA3_EXT_PSK mixed mode
- Improvements in scan and connect path as per specifications along with
minor bugfixes
- When AP advertises all PSK modes (WPA, WPA2 and WPA3), make sure that
station treats it as WPA2_WPA3_PSK mixed mode.
Closes https://github.com/espressif/esp-idf/issues/12517
- WIFI_REASON_NO_AP_FOUND_W_COMPATIBLE_SECURITY will be reported for the following
reasons
-- AP has PMF required but station is not configured for pmf capable/required.
-- Station has PMF required but AP is not configured for pmf capable/required.
-- The AP is using unsupported group management/pairwise ciphers
-- OWE not enabled by station for found OWE AP
-- AP RSNXE parsing failed in supplicant
-- AP is in Independent BSS mode
1. fix the bug that station can't found AP when the authmode is WPA
2. fix wifi mode error when mesh start after station has connected to router
Closes https://github.com/espressif/esp-idf/issues/12646
This commit deprecates the "freertos/xtensa_api.h" and "xtensa/xtensa_api.h"
include paths. Users should use "xtensa_api.h" instead.
- Replace legacy include paths
- Removed some unnecessary includes of "xtensa_api.h"
- Replaced some calls with "esp_cpu_..." equivalents
- Add warning to compatibility header
1. Avoid possible crash scenarios while forming datapath
2. Modify peer records structure thus fixing issues in datapath establishment
3. Fix timer out of bound issue causing "No timer handle" warning
4. Fix miscellaneous service discovery and datapath issues
- Fixes issue with connecting and discovering WEP APs
- Expsnds the reasons for trigerring a disconnect using
REASON_NO_AP_FOUND_WITH_COMPATIBLE_SECURITY
-- SAE-PK configured as compulsory in sta config but disabled for the AP
-- SAE-H2e configured as compulsory in sta config but disabled for an AP
that has authmode as WPA3-PSK or WPA3-WPA2-PSK.
-- Open AP found but we have set password or enabled enterprise mode.
-- SAE H2E only ap but we have SAE HnP setup in config.
-- WPA3-EXT_PSK AP but SAE-H2E disabled in config
Adds 3 more ddisconnect reasons in case of No AP found.
1. REASON_NO_AP_FOUND_IN_RSSI_THRESHOLD : AP rejected because it did
not meet rssi threshold.
2. REASON_NO_AP_FOUND_IN_AUTHMODE THRESHOLD : AP rejected because it
did not meet security threshold.
3. REASON_NO_AP_FOUND_WITH_COMPATIBLE_ SECURITY : AP rejected because
of incompatible security configuration. These situations could include
-- bss offerring WEP, but our password is not WEP compliant,
-- Encrypted AP bss but we have no password config set.
-- AP is Enterprise but we have not setup enterprise config and vice versa
Closes https://github.com/espressif/esp-idf/issues/5957
Jiang Jiang Jian