Closed aquaticus closed 1 year ago
Hi @aquaticus , We have tried the mentioned steps with an AP configured similarly as yours and cannot seem to reproduce the same result. Could you please provide a sniffer capture which include the beacons of the AP you are facing the issue with?
I (3420) scan: SSID jash_wpa2_ent I (3420) scan: RSSI -25 I (3420) scan: Authmode WIFI_AUTH_WPA2_ENTERPRISE I (3430) scan: Pairwise Cipher WIFI_CIPHER_TYPE_CCMP I (3430) scan: Group Cipher WIFI_CIPHER_TYPE_CCMP I (3440) scan: Channel 11
@jgujarathi Please find attached beacon pcap dump (unzip file). mng_frame_enabled_beacon.zip
@aquaticus thanks for the capture, this will be corrected in next software fix.
Just want to check if v4.3 branch is impacted by this issue? I'm wondering if I should wait for this fix for v4.3 branch to build my application firmware.
Yes, v4.3 branch is also impacted by this. However its only a display issue and functionality won't change.
Yes, v4.3 branch is also impacted by this. However its only a display issue and functionality won't change.
Our configure interface does not allow user to set enterprise settings if it was recognized as WIFI_AUTH_OPEN. So this is not just a display issue, I have to wait for your fix.
@jgujarathi @kapilkedawat Any update for the fix?
@jgujarathi @kapilkedawat
All stable branches are impacted by this issue. I cannot workaround the issue since I think the issue is in wifi-lib. Could you fix it ASAP?
@aquaticus thanks for the capture, this will be corrected in next software fix.
There are several esp32-wifi-lib and esp-idf (including esp-idf-v4.4.5) updates recently, but still cannot find this fix in any branches.
@igrr @Alvin1Zhang Can someone help to fix this bug? The bug is in all release branches.
Answers checklist.
IDF version.
v5.1-dev-4557-gf404fe96b1
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
Custom Board
Power Supply used.
USB
What is the expected behavior?
When using WPA2-EAP authentication method is used and router enables 802.11w Management Frame Protection, WiFi scan reports network as
WIFI_AUTH_WPA2_ENTERPRISE
.After call to
esp_wifi_scan_get_ap_records()
wifi_auth_mode_t
member ofwifi_ap_record_t
should be set toWIFI_AUTH_WPA2_ENTERPRISE
.What is the actual behavior?
Instead WiFi scan authomode for the network is
WIFI_AUTH_OPEN
.After call to
esp_wifi_scan_get_ap_records()
wifi_auth_mode_t
member ofwifi_ap_record_t
is incorrectly set toWIFI_AUTH_OPEN
.Steps to reproduce.
Debug Logs.
More Information.
The issue was recreated on:
Chips: ESP32 and ESP32-C3
NOTES:
Output from
nmcli dev wifi
on Linux for the same network (proper WPA2 802.1X)