mDNS reporting wrong IP address with esp32-wifi-manager
Posted: Mon Jul 12, 2021 4:24 pm
I'm not sure where to ask this but I'm hoping someone has run into this and has a fix.
I'm using esp32-wifi-manager (https://github.com/tonyp7/esp32-wifi-manager) in my project. It works great and appears pretty simple. When the WiFi is uninitialized it starts initialized the WiFi in AP mode and provides a web page for configuring the SSID and PW to attach to. Then it switches into STA (station) mode and attached to the access point you specified and as long as it can re-attach to that access point it will stay in STA mode.
When I start mDNS in STA mode, defining an HTML service, and try to attach to my device (ex: http://myesp32.local) the address that is resolved by mDNS is the address of the AP mode, not what was served by DHCP in STA mode. I can, however, ping myesp32.local just fine. The address is properly resolved.
Any ideas?
I'm using esp32-wifi-manager (https://github.com/tonyp7/esp32-wifi-manager) in my project. It works great and appears pretty simple. When the WiFi is uninitialized it starts initialized the WiFi in AP mode and provides a web page for configuring the SSID and PW to attach to. Then it switches into STA (station) mode and attached to the access point you specified and as long as it can re-attach to that access point it will stay in STA mode.
When I start mDNS in STA mode, defining an HTML service, and try to attach to my device (ex: http://myesp32.local) the address that is resolved by mDNS is the address of the AP mode, not what was served by DHCP in STA mode. I can, however, ping myesp32.local just fine. The address is properly resolved.
Any ideas?