-
-
Notifications
You must be signed in to change notification settings - Fork 222
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
mDNS doesn't appear to be reporting a hostname? #136
Comments
Well, it appears that the call wifi_manager_initialise_mdns() isn't implemented so I implemented my own, which I call when I receive WM_EVENT_STA_GOT_IP. Strange thing is. I'm now able to ping myhostname.local but when I point my browser to myhostname.local, it returns the AP address 10.10.0.1. Any ideas why? Fantastic project! I should have added. Thank you! |
I'm not sure how to read this but there is a response in HTTP from the esp32 (.126) claiming that the "Location:" is 10.10.0.1 (from Wireshark)? I'm not sure where this is coming from. The AP should be down? Any ideas? Frame 10207: 84 bytes on wire (672 bits), 84 bytes captured (672 bits) on interface en4, id 0 |
I'm not sure this is normal but it appears that the interface is still configured as both STA and AP? Could this be why I get the AP address? I would think the AP mode should be disabled since it's in STA mode and has an IP. Code I changed in esp-idf/mdns.c:
Output on console:
|
Prerequisites
Description
I'm looking for esp32 (appears to be default value) on my network but I'm not able to find it. I don't think mDNS is working. Is there a magic incantation?
Steps to Reproduce
Build, include in your project, try to access esp32.local (or whatever is required on your network).
System Configuration
esp-idf v4.2
DOIT ESP32 DEVKIT V1
Environment (Operating system, version and so on):
MacOS 10.15.7
Additional information:
The text was updated successfully, but these errors were encountered: