Avahi - Invalid response packet from host?

q54e3w · Mar 15, 2015, 7:53 PM

I'm using pfSense 2.2 and have recently noticed a steady stream of errors in my system log relating to avahi.
They look something like this….


...
Mar 15 18:06:58 pfsense avahi-daemon[86175]: Invalid response packet from host 192.168.110.10.
Mar 15 18:07:00 pfsense avahi-daemon[86175]: Invalid response packet from host 192.168.110.10.
Mar 15 18:07:01 pfsense avahi-daemon[86175]: Invalid response packet from host 192.168.110.10.
Mar 15 18:07:04 pfsense avahi-daemon[86175]: Invalid response packet from host 192.168.110.10.
Mar 15 18:07:08 pfsense avahi-daemon[86175]: Invalid response packet from host 192.168.110.10.
...

Theres a fair number of them and they are pretty evenly spread. I tried debugging to find the source of the errors but I've not found anything concrete yet. However I did want to ask about one thing I noticed which might be contributing.

I'm beta testing pfblockerNG v2 with DNSBL support and noticed that the interface used as the virtual interface (10.10.10.1) gets added to the avahi interfaces upon enumeration. It doesn't appear to be possible to exclude it as its not a 'real interface' and doesn't populate into the avahi dropdown box to exclude. I can move the problem around around by adjusting where the pfblockerNG VIP attaches, but I'm not able to rid the problem completely.

If its not possible to patch Avahi OR pfblockerNG to prevent this addtionalenumeration, what are the side effects, i.e spamming mDNS packets into a virtual interface, anything to worry about?


Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for fe80::a236:9fff:fe2d:eba8 on ovpns2.*.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for 192.168.210.1 on ovpns2.IPv4.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for fe80::ec4:7aff:fe07:d552 on igb6_vlan30.*.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for 192.168.51.1 on igb6_vlan30.IPv4.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for fe80::ec4:7aff:fe07:d552 on igb6_vlan20.*.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for 192.168.71.1 on igb6_vlan20.IPv4.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for fe80::ec4:7aff:fe07:d553 on igb7.*.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for 192.168.70.1 on igb7.IPv4.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for fe80::ec4:7aff:fe07:d551 on igb5.*.

Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for 10.10.10.1 on igb5.IPv4.

Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for 192.168.50.1 on igb5.IPv4.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for fe80::92e2:baff:fe37:fba5 on ix1.*.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for 192.168.110.1 on ix1.IPv4.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for fe80::92e2:baff:fe37:fba4 on ix0.*.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering new address record for 192.168.101.1 on ix0.IPv4.
Mar 15 18:05:20 pfsense avahi-daemon[86175]: Registering HINFO record with values 'AMD64'/'FREEBSD'.
Mar 15 18:05:21 pfsense avahi-daemon[86175]: Server startup complete. Host name is pfsense.local. Local service cookie is 1382368288.
Mar 15 18:05:22 pfsense avahi-daemon[86175]: Service "pfsense" (/usr/local/etc/avahi/services/ssh.service) successfully established.
Mar 15 18:05:22 pfsense avahi-daemon[86175]: Service "pfsense" (/usr/local/etc/avahi/services/sftp-ssh.service) successfully established.

jme · Feb 24, 2016, 7:01 AM

have the same Problem with Windows 10 Hosts, they will be flood the syslog file of pfsense.

this issue was fixed in avahi Version =>0.6.32.

Is there a chance to Update the pfsense Package to this Version?

Thanks a lot….

bryanlakatos · Aug 22, 2016, 1:53 PM

BUMP. I, too, would love to have the/a Avahi pfSense package updated to 0.6.32. Looks like Scott Ulrich was the original package's creator, and he apparently doesn't have much to do with pfSense anymore. Does anyone else have any experience creating pfSense packages and can help us out? I'd even be willing to pay someone for their time…

kpk · Sep 23, 2016, 12:02 PM

I would like to give a +1.
Avahi seems broken and so it isn't available in the result.
But it is mandatory for advanced network configurations with different clients. E.g. Time Machine Server for OSX.
Also, if any other package delivers what avahi would do, I am fine with that.

https://pkg.pfsense.org/pfSense_v2_3_2_amd64-pfSense_v2_3_2/All/gobject-introspection-1.46.0.txz: Operation timed out

Update: It seems it has been installed within the 3rd try, even with the error above. Will it work? Either functional or not, please ensure that it is functional and without errors.

luckman212 · Feb 17, 2017, 4:22 PM

I know this is an oldie-but-goodie … we have a couple of people that use this avahi package (I know, it's bad practice etc etc but there are use cases for it...)

Was wondering if anyone knows anything about getting the freebsd-port updated to 0.6.32 which apparently fixes this bug.

found a few references but the last update on Freshports is from April fools 2016 w/ the old 0.6.31 version
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1342400
https://patchwork.openembedded.org/patch/113401/

doktornotor · Feb 17, 2017, 5:10 PM

@luckman212:

Was wondering if anyone knows anything about getting the freebsd-port updated to 0.6.32 which apparently fixes this bug.

Try https://bugs.freebsd.org/bugzilla/; won't happen in pfSense until there's a port available.

luckman212 · Feb 17, 2017, 5:39 PM

Thx Dok ;)
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217179