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 have used the latest released firmware or have updated my ESP-AT branch (master or release) to the latest version and checked that the issue is present there.
I have searched the issue tracker for a similar issue and not found a similar issue.
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
enp41s0 IPv4 dcchost _withrottle._tcp local
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
withrottle.withrottle._tcp.local instead.
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:
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: