OpenWrt/LEDE Project

  • Status Unconfirmed
  • Percent Complete
    0%
  • Task Type Bug Report
  • Category Packages
  • Assigned To No-one
  • Operating System All
  • Severity Medium
  • Priority Very Low
  • Reported Version Trunk
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Kirill Elagin - 17.11.2021

FS#4140 - umdns does not respect legacy queries (not from port 5353)

According to Section 6.7 of the RFC, if the query was sent not from port 5353, the responder MUST respond over unicast and, most importantly, to the same port that the query was sent from.

This is what currently prevents

dig -p 5353 @224.0.0.251 <hostname>

from working, since dig is expecting the response on the random port it sent its query from, but umdns, contrary to the specifiation, always sends to port 5353.

Kirill Elagin commented on 17.11.2021 20:18

I made a patch (untested!) that will ensure the response goes to the right address/port.

However, there are additional requirements that, IIUC, are currently not satisfied:

                                This unicast response MUST be a
   conventional unicast response as would be generated by a conventional
   Unicast DNS server; for example, it MUST repeat the query ID and the
   question given in the query message.  In addition, the cache-flush
   bit described in Section 10.2, "Announcements to Flush Outdated Cache
   Entries", MUST NOT be set in legacy unicast responses.

Loading...

Available keyboard shortcuts

Tasklist

Task Details

Task Editing