Windows 10 is Causes avahi-daemon to Spam Log File

[JosephAE]

Does Netgear have a fix that will stop Windows 10 from causing the avahi-daemon to fill up the log file with 'invalid response packages'?

[mdgm-ntgr]

Which ReadyNAS model and which firmware?

Can you send me your logs (see the Sending Logs link in my sig)?

[mdgm-ntgr]

Microsoft is violating the mDNS RFC. There is a discussion about this here: https://github.com/lathiat/avahi/issues/10#issuecomment-131972196

Have you installed the latest Windows updates for your PC?

[JosephAE]

They talk about it but what is the fix? Yes I have the latest Windows updates.

[mdgm-ntgr]

The fix would be for Microsoft to provide an update with the fix.

[JosephAE]

You imply that Microsoft doesn't have an update so can you download avahi-daemon 0.6.32? And from where can you get it?

[mdgm-ntgr]

Well Microsoft should have already provided an update that addressed this according to that github issue. The problem is in their court.

[JosephAE]

So your confirming that Microsoft doesn't have a fix. Where can you download avahi-daemon 0.6.32?

[StephenB]

---

@mdgm wrote:

Microsoft is violating the mDNS RFC. There is a discussion about this here: https://github.com/lathiat/avahi/issues/10#issuecomment-131972196

Have you installed the latest Windows updates for your PC?

---

Based on the discussion in the github, I'd agree they are violating the RFC.  

However, it would still make sense to update the avahi-daemon to prevent flooding in the log file.  For better or worse, there are no standards police, and this particular issue seems easy to deal with.  

[JosephAE]

Is there a Netgear location or a distro where I can download the latest software (avahi-daemon 0.6.32)?

[JosephAE]

No answer? Is avahi-daemon 0.6.32 not compatible with my Netgear device or do you not know of a location where I can download that version?

[mdgm-ntgr]

It may not be so simple as updating the avahi-daemon package as there may be a range of other changes needed to keep things working.

This particular issue is a bug with Windows and hopefully Microsoft addresses it.

Which ReadyNAS model do you have and which firmware is it running?

[JosephAE]

The log files that I previously provide would have that but it is version 4.2.28 and the device is a ReadyNAS Pro Business.