-
Notifications
You must be signed in to change notification settings - Fork 7.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIFI_EVENT_STA_DISCONNECTED with reason=34 (not part of the err enum) (IDFGH-5899) #7593
Comments
Something to add here: If we don't use dhcpc to acquire an ip but set a static ip address, everything works fine. So error 34 might mean "no dhcp found on the network" ? |
Hi @0xFEEDC0DE64, the reason code 34 is "Association denied due to excessive frame loss rates and/or poor conditions on current operating channel". The reason codes < 200 are defined by IEEE standard and we covered most common ones in the enum. We will update the structure to cover all the defined ones. |
But this does not explain that it works if using static ip. |
@0xFEEDC0DE64 Can we have the sniffer capture and SDK config.Also can you enable the supplicant logs and MBEDTLS logs and try the connection once.What is the AP security config. |
Thanks for all your answers so far :) I will try my best to get the esp32 log output remotely (by modifying the esp-idf so that they are sent over websocket to me) but doing a remote wifi capture will be impossible. We are using an esp-idf branch/fork based on 4.4-dev Other clients are able to talk to the AP and also they get an ip address. I don't know the exact dhcp configuration on the customers wifi router (but if that is really the issue here, i will try to get at least that) |
@sagb2015 |
@0xFEEDC0DE64 |
Does this issue still happen or already fixed? BTW, since you are using v4.4, does it work with latest v4.4 code (e.g v4.4-beta1-308-gf3e0c8bc41)? |
i just checked with the newest esp-idf master, i cannot reproduce this error 34 with the same access point anymore, seems like a random binary blob update fixed the issues somehow. |
@sagb2015 I don't see any update for the wifi_err_reason_t. |
Hi,
a customer has a home wifi setup where the esp32 is not able to connect to his homenetwork.
I tried debugging remotely and got the conclusion, that esp-idf is emitting a WIFI_EVENT with WIFI_EVENT_STA_DISCONNECTED with reason = 34.
Reason 34 is not part of the
wifi_err_reason_t
.What does reason 34 mean? Is it coming from the closed-source binary blobs which do all the wifi magic? Can someone fill out the missing error reasons?
The text was updated successfully, but these errors were encountered: