Comment # 7 on bug 1226586 from Martin Wilck
Background in my home network: I added new printer (HP smarttank 7305)
yesterday. This morning I saw the issue mentioned in this bug for the first
time. Because the printer is the only new device in my network, and it uses
mDNS to advertize its services, it's not unlikely that something this printer
is doing caused the issue.

However, the apparently broken mDNS records are not sent by the printer, but
from my Amazon fire TV stick (192.168.1.200) in packet 41. It appears that this
host violates the mDNS spec by responding with PTR records it doesn't provide
itself, such as _uscan._tcp.local
(https://datatracker.ietf.org/doc/html/rfc6762#section-6: "When a Multicast DNS
responder constructs and sends a Multicast DNS response message, the Resource
Record Sections of that message must contain only records for which that
responder is explicitly authoritative" - but I'm no expert on the mDNS
protocol). Some of these would naturally be provided by my printer only.

Anyway, no such breakage should cause the operation of avahi to be disrupted.


You are receiving this mail because: