Description of problem: The system log is filled with many thousands of these messages: avahi-daemon[570]: Invalid response packet from host 10.6.13.57. There is no useful purpose to sending this message to the log; it bloats the file system; it obscures important messages. Version-Release number of selected component (if applicable): avahi-0.6.31-31.fc22.x86_64 How reproducible: always Steps to Reproduce: 1. Run f22 ona network with whatever avahi doesn't like. 2. 3. Actual results: thousands of messages. Expected results: fewer (one!) messages Additional info: This may be a regression -- it hasn't shown up in earlier releases: http://www.avahi.org/ticket/284 .
This is really silly and wasteful: garry@ifr$ journalctl|grep -c 'Invalid response packet' 122561 garry@ifr$
*** Bug 1260744 has been marked as a duplicate of this bug. ***
*** Bug 1177166 has been marked as a duplicate of this bug. ***
This is becoming unreasonable. This bug has been open for 9 months, and no action has been taken. Avahi is a useful service for those who need it. However, for some, it can fill the journal - when I take my laptop to my university and connect to the campus LAN, my journal is overwhelmed with reports of "Invalid response packet from host ..." Even here at home, I have one Canon MFP device that doesn't either doesn't implement the standard properly, or isn't interpreted by my laptop correctly, so an entry is logged every 20 seconds. A proper way to handle this is to log it once, and then ignore it. [dan@g55 ~]$ journalctl | grep -c 'Invalid response packet' 286620 [dan@g55 ~]$
Looks like http://avahi.org/ticket/352 has a concrete proposal on how to address this, maybe worth trying. any objections?
%changelog * Thu Sep 17 2015 Rex Dieter <rdieter> 0.6.31-39 - Syslog Filled With "Invalid response packet from host" Message (#1240711) - avahi-daemon manpage references file locations under /home/lennart/tmp (#991094)
avahi-0.6.31-40.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16117
avahi-0.6.31-40.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16118
avahi-0.6.31-40.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16119
avahi-0.6.31-40.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update avahi'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16117
avahi-0.6.31-40.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update avahi'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16119
Recently I've seen that mDNS implementation on some Windows 10 machines also violates RFC6762, in particular this clause, A Multicast DNS responder MUST only respond when it has a positive, non-null response to send, or it authoritatively knows that a particular record does not exist. For unique records, where the host has already established sole ownership of the name, it MUST return negative answers to queries for records that it knows not to exist. It does so by sending responses to queries asked by non fully compliant mDNS queriers (source port is high-number ephemeral UDP port, not 5353) with ANSCOUNT == 0. It literally sends back empty DNS packets without no RRs in them, nor any useful header flags (NXDOMAIN) set.
<nod>, since this snippet of code to me seems more like a tool for debugging, I was tempted to drop the syslog output for this case completely. If problems persist, we could consider doing that.
avahi-0.6.31-40.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update avahi'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16118
Hello Even with the http://pkgs.fedoraproject.org/cgit/avahi.git/tree/avahi-0.6.31-invalid_packet.patch I still get a lot of messages with the avahi-daemon[412]: Invalid response packet from host ... error :( Thanks for your help
(In reply to Pacho Ramos from comment #15) > Even with the > http://pkgs.fedoraproject.org/cgit/avahi.git/tree/avahi-0.6.31- > invalid_packet.patch I still get a lot of messages with the > avahi-daemon[412]: Invalid response packet from host ... > Do you have any Windows 10 machine on your network? If yes, then this is most likely caused by problem I described in comment #12.
Yes, there are machines with Windows 10 in the network of my center :/
avahi-0.6.31-42.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16118
avahi-0.6.31-42.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16119
avahi-0.6.31-40.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
The last patch finally works for me, thanks!
avahi-0.6.31-42.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update avahi' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16119
avahi-0.6.31-42.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update avahi' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16118
avahi-0.6.31-43.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16118
avahi-0.6.31-43.fc21 has been submitted as an update to Fedora 21. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16119
(In reply to Fedora Update System from comment #24) > avahi-0.6.31-43.fc22 has been submitted as an update to Fedora 22. That fixed it. Thank you.
avahi-0.6.31-43.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update avahi' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16118
avahi-0.6.31-43.fc21 has been pushed to the Fedora 21 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with $ su -c 'dnf --enablerepo=updates-testing update avahi' You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16119
avahi-0.6.31-43.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
avahi-0.6.31-43.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.