You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm developing for esp32 using esp-hal with embassy and face problems acquiring IP.
I have several TPLink Omada access points, and when several serve the same SSID the device fails to get the IP, or takes a lot of time (at least tens of seconds and even more).
When I leave only a single access point serving that SSID (others still work, just don't serve that SSID) the device gets the IP within a few seconds.
I discussed this in depth with the esp-hal team, and provided them with the relevant logs and they told me this part is handled by smoltcp.
I'm developing for esp32 using
esp-hal
withembassy
and face problems acquiring IP.I have several
TPLink Omada
access points, and when several serve the same SSID the device fails to get the IP, or takes a lot of time (at least tens of seconds and even more).When I leave only a single access point serving that SSID (others still work, just don't serve that SSID) the device gets the IP within a few seconds.
I discussed this in depth with the
esp-hal
team, and provided them with the relevant logs and they told me this part is handled bysmoltcp
.The full discussion is available at: esp-rs/esp-hal#2345
Logs with some more finIngs available at: esp-rs/esp-hal#2345 (reply in thread)
Some more analysis: esp-rs/esp-hal#2345 (reply in thread)
And there is more relevant information on that thread which I don't want to copy here.
Any pointers as to how to troubleshoot this? Maybe it's a known issue?
The text was updated successfully, but these errors were encountered: