Wifi Easy Connect failure - credential exchange / handshake fails (IDFGH-16552)

[sakshmika]

Answers checklist.

• I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
• I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
• I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report

Utilizing the dpp-enrollee example for esp32 but facing challenges. Using stock Android’s native WiFi Easy Connect configurator utility to test this.
Usually, the session times-out or the credential exchange / handshake fails. Tried the sequence on different (but recent) IDF versions, different Android devices as well as esp32 & esp32-s3 as targets.
Attaching the failure logs herewith.

Link to tried implementation : https://github.com/espressif/esp-idf/tree/release/v5.5/examples/wifi/wifi_easy_connect/dpp-enrollee

Thanks.

v5.5_failLogs.txt

[Shreyas0-7]

Hey @sakshmika we have recently made changes 0e00b0f for DPP.
Can you please check if you are facing this issue on top of this commit

[sakshmika]

Hey @Shreyas0-7
I’ve tested the dpp-enrollee example using the latest changes, including commit 0e00b0f.
While I do see occasional successful provisioning, the behavior remains inconsistent. In many cases, the session either times out or fails during the credential exchange/handshake phase. This intermittent success suggests the issue may not be entirely resolved.

I’ve attached failure logs as well as success logs from these runs for reference. Please let me know if there are additional patches or configuration tweaks I should try to help narrow this down further.
Thanks again for your support.

Failure logs-

dppLogs_0e00b0f45.txt

Success Logs-

successdpp_0e00b0f45.txt

[Shreyas0-7]

Hey @sakshmika thanks for trying this out which new changes.
To debug the inconsistency that you have faced,we would need supplicant logs and sniffer capture.

To enable supplicant logs, please enable this ESP_WIFI_DEBUG_PRINT in idf.py menuconfig

Here are steps, can you please try this to capture sniffer
If you are using a Windows machine, try: https://www.youtube.com/watch?v=As9BUoOMk_A
If you are using an iOS machine, try: https://youtu.be/hxtgin0hgf8?si=nRvTdL24KiKHOPIs
If you are using a Linux machine do iwconfig, and select interface which you are not using
For example your interface is wlp0s20f3, try:

ifconfig wlp0s20f3 down
iwconfig wlp0s20f3 mode monitor
ifconfig wlp0s20f3 up
iwconfig wlp0s20f3 channel 6
wireshark

Please note that a lot of WiFi cards (NIC) don't support putting them in monitor mode. So it is vital to check the compatibility of your laptop's NIC.

[sakshmika]

Hey @Shreyas0-7 I've tried this out.

To help debug the inconsistency I faced, I've captured ESP logs with supplicant logs enabled and the sniffer trace.
For sniffer setup:
I’m using a Linux machine, and followed these steps:
ifconfig wlp0s20f3 down
iwconfig wlp0s20f3 mode monitor
ifconfig wlp0s20f3 up
iwconfig wlp0s20f3 channel 6
tcpdump -i wlp0s20f3 -w file_name.pcap

Attached are the files-

fail_SupplicantEnable_0e00b0f45.txt

dpp_capture.zip

Thanks.

[Shreyas0-7]

Hey @sakshmika, thanks for the logs. I can see a TX_FAILURE for ESP. To debug this further, we needa sniffer capture. The sniffer you attached doesn't have 802.11 packets. Can you please check the following things?

1. Sniffer is capturing on channel 6
2. The interface used for sniffing is not connected to any Access Point

[sakshmika]

Hey @Shreyas0-7 , please find the attached logs along with sniffer -

logs_dpp.txt
sniff_dpp.zip

Thanks.

[Shreyas0-7]

Hey @sakshmika, thanks for log. I can see esp is sending GAS Config request after authentication confirmation. But the configurator is not able to ack it. We can see a delay which might be introduced due to logs between the authentication confirmation and tx of Gas config request. Is it possible for you to test it again without logs and a capture sniffer? Thank you

[sakshmika]

Hi @Shreyas0-7 , please find the attachments as asked.
I can see in logs that "Failed to connect to SSID:" even when showing shared successfully on configurator side.

27Nov.txt

27nov1.zip

[Shreyas0-7]

Hey @sakshmika can you please check if Airtel_Home_5G is active on 2.4ghz or 5ghz. Also, if it's your personal router I would suggest you to remove the password from the logs.

[sakshmika]

Hi @Shreyas0-7 , Airtel_Home_5G is active on 5ghz. Also I have updated the attached of logs by removing the password.
Thanks.