Axel Lin

@vik-gokhale I capture again (with a good one and a bad one), please take a look. What's wrong with the bad device, [a8_03_2a_e6_c4_f4_ng_log.pcapng.txt](https://github.com/user-attachments/files/16496320/a8_03_2a_e6_c4_f4_ng_log.pcapng.txt) [f0_08_d1_79_8c_60_ok_log.pcapng.txt](https://github.com/user-attachments/files/16496321/f0_08_d1_79_8c_60_ok_log.pcapng.txt)

> Hi @AxelLin, > > 1. These traces are captured from a LAN interface and not a WLAN interface. My previous capture using WLAN interface does not capture all packets....

@mhdong Just remind the v5.2 still needs fix.

@mhdong This issue seems not related to **dns**? I'm curious what was fixed by 00c2767 "fix(wifi): fix reset connection dns fail issue" ?

> @mhdong Just remind the v5.2 still needs fix. @mhdong In v5.0.7 release log, I found this: Fixed the issue of DNS failure caused by continuously initiating connections to the...

> @mhdong > > This issue seems not related to **dns**? I'm curious what was fixed by [00c2767](https://github.com/espressif/esp-idf/commit/00c2767ea9ac7eedb98bc278ed6007ae6da9b7b3) "fix(wifi): fix reset connection dns fail issue" ? I don't understand why...

@mhdong Ok, so could you share if this is fixed in all impacted branches? The thing is the backport commit log does not tell any useful information (e.g. fix(wifi): fix...

> The possible reasons are listed above, and you can further confirm the specific reasons by opening the debug level. menuconfig -> Component config -> Log output -> Default log...

> If all possible reasons are added as reason codes, it will result in too many reason codes. We will continue to add reasons that are meaningful to customers or...

@esp-lis I don't get it. It works if build with esp-idf-5.2 branch. It stop working after switch to 5.3+.