esp-idf: WPA2 ENT EAP example not connecting to ubiquiti network. 4.1.1 (IDFGH-5123)
Environment
- Development Kit: [none]
- Module or chip used: [ESP32-WROOM-32]
- IDF version v4.1 - > v4.1.1
- Build System: [Make]
- Compiler version xtensa-esp32-elf-gcc (crosstool-NG esp-2020r2) 8.2.0
- Operating System: [Linux]
- Using an IDE?: [No]
- Power Supply: [USB]
Problem Description
After updating to v4.1.1 from v4.1 WPA ENT PEAP no longer connects to the access point, Using either the example program or ours.
Expected Behavior
[0;32mI (2965) wpa: EAP-TLV: TLV Result - Success - EAP-TLV/Phase2 Completed[0m
[0;32mI (2975) wpa: >>>>>wpa2 FINISH
[0m
I (2995) wifi:connected with wpawep, aid = 2, channel 6, BW20, bssid = 3a:e8:29:5a:5a:e5
I (2995) wifi:security: WPA2-Ent, phy: bgn, rssi: -56
I (2995) wifi:pm start, type: 1
I (3045) wifi:AP's beacon interval = 102400 us, DTIM period = 1
[0;32mI (4965) example: ~~~~~~~~~~~[0m
[0;32mI (4965) example: IP:0.0.0.0[0m
[0;32mI (4965) example: MASK:0.0.0.0[0m
[0;32mI (4965) example: GW:0.0.0.0[0m
[0;32mI (4965) example: ~~~~~~~~~~~[0m
[0;32mI (5125) esp_netif_handlers: sta ip: 192.168.1.32, mask: 255.255.255.0, gw: 192.168.1.1[0m
[0;32mI (6965) example: ~~~~~~~~~~~[0m
[0;32mI (6965) example: IP:192.168.1.32[0m
[0;32mI (6965) example: MASK:255.255.255.0[0m
[0;32mI (6965) example: GW:192.168.1.1[0m
[0;32mI (6965) example: ~~~~~~~~~~~[0m
[0;32mI (8965) example: ~~~~~~~~~~~[0m
[0;32mI (8965) example: IP:192.168.1.32[0m
[0;32mI (8965) example: MASK:255.255.255.0[0m
[0;32mI (8965) example: GW:192.168.1.1[0m
[0;32mI (8965) example: ~~~~~~~~~~~[0m
Actual Behavior
I (15219) wifi:new:<6,0>, old:<6,0>, ap:<255,255>, sta:<6,0>, prof:1
I (15219) wifi:state: init -> auth (b0)
I (15239) wifi:state: auth -> assoc (0)
I (15249) wifi:state: assoc -> run (10)
[0;32mI (16909) example: ~~~~~~~~~~~[0m
[0;32mI (16909) example: IP:0.0.0.0[0m
[0;32mI (16909) example: MASK:0.0.0.0[0m
[0;32mI (16909) example: GW:0.0.0.0[0m
[0;32mI (16909) example: ~~~~~~~~~~~[0m
I (17319) wifi:state: run -> init (17c0)
I (17329) wifi:new:<6,0>, old:<6,0>, ap:<255,255>, sta:<6,0>, prof:1
I (17329) wifi:new:<6,0>, old:<6,0>, ap:<255,255>, sta:<6,0>, prof:1
[0;32mI (18909) example: ~~~~~~~~~~~[0m
[0;32mI (18909) example: IP:0.0.0.0[0m
[0;32mI (18909) example: MASK:0.0.0.0[0m
[0;32mI (18909) example: GW:0.0.0.0[0m
[0;32mI (18909) example: ~~~~~~~~~~~[0m
Steps to reproduce
- open wpa enterprise example
- change example configs,
#
# Example Configuration
#
CONFIG_EXAMPLE_WIFI_SSID="wpawep"
# CONFIG_EXAMPLE_VALIDATE_SERVER_CERT is not set
# CONFIG_EXAMPLE_EAP_METHOD_TLS is not set
CONFIG_EXAMPLE_EAP_METHOD_PEAP=y
# CONFIG_EXAMPLE_EAP_METHOD_TTLS is not set
CONFIG_EXAMPLE_EAP_METHOD=1
CONFIG_EXAMPLE_EAP_ID="example@espressif.com"
CONFIG_EXAMPLE_EAP_USERNAME="userr"
CONFIG_EXAMPLE_EAP_PASSWORD="userr123"
# end of Example Configuration
// If possible, attach a picture of your setup/wiring here. No wiring needed.
Code to reproduce this issue
WPA ENT example program
Debug Logs
I’ve attached logs of the default sdk config after changing the examples for PEAP, and one with verbose logging turned on.
Other items if possible
default-wpa4.1.1.log log-wpa4.1.1.log
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 21 (4 by maintainers)
@timmyhadwen Thanks for the conf files,Using the eap.conf,I am trying to repro the issue locally.Can you point me to the IDF commit you are using. I have tried on the latest 4.1.1 and 4.3 but did not see the issue. Can you pls share your commit ID? From the fail hostapd logs of 4.1.1 and sdkconfig, I see the following. The outer identity username which is supposed to be “example@espressif.com” is getting replaced by the inner identity username “fiffy” and the inner identity is left blank. 1.Are you using the example as such or are you calling the API’s and having your own code? a. If you are using your own code,Can you verify the assignment of outer identity and inner identity. b. If you are using the example,Can you do a idf.py fullclean,remove the build and sdk config and then build fresh. Erase the chip using “idf.py erase_flash” and then flash again.This will erase any previous identity stored on the chip. 2.Can you pls share the commit ID on 4.3 and 4.1.1 on which you are seeing the issue,so that we can check if there is any change in code.