-
Notifications
You must be signed in to change notification settings - Fork 690
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
AT+MDNS does not produce the expected record #810
Comments
@SeraphimlabsLLC many thanks for your report, i agreed. on AT v1.7.4, esp-at uses hostname as the instance name: on AT v3.3.0, esp-at uses the service name as the instance name: maybe we should add one CW |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Answers checklist.
General issue report
AT versions 3.3 and higher do not appear to produce the expected mdns record. The host portion is being replaced by the service name. It is likely that this applies as far back as 2.2, I've only tested 3.3 and 4.1.
With a working AT 1.7.4, the command string AT+MDNS=1,"dcchost","withrottle",2560
results in avahi-browse --all showing
If I use AT 3.3 or 4.1 with the same AT+MDNS=1,"dcchost","withrottle",2560,
avahi-browse --all actually breaks with avahi_service_browser_new() failed: Invalid service type, this is actually a known bug with this tool when a malformed broadcast was made recently.
Using mdns-scan instead, I see the malformed
Please advise what can be done. I've tried a couple different ESP-AT versions on an ESP32-C3-WROOM-2 module, compiling from the git repository in order to assign the pin numbers correctly.
Edit:
Further comparison of the mdns output of 1.7.4 vs 3.3 using Wireshark, I can see that the 3.3 firmware is sending correct queries for the intended hostname before transmitting the malformed PTR records.
Compared to the 1.7.4 firmware where it just sends PTR records with the provided data. Could this have something to do with it? There is an extra setup step in the newer firmware that the documents missed?
The text was updated successfully, but these errors were encountered: