Hi

 

today have update one my pc to windows 10 pro start to get an errors

in my syslog

 

Jul 29 20:25:11 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

Jul 29 20:25:11 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

Jul 29 20:25:11 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

Jul 29 20:25:11 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

Jul 29 20:25:25 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

 

get them evey few mins in large packs check the ip address and it is the windows 10 pc

only start doing it since update to windows 10 befor it was on windows 8.1 pro

other computers/laptops in my network are fine just this one pc

 

any help on matter be good

thanks

Seeing the same here.  One Win10 Pro PC, two others waiting to upgrade.

 

avahi is the non-Apple version of Bonjour as far as I can tell, so pretty pointless for most people unless they're running Apple clients. 

 

Personally, I'd like to see an option that allows it to be disabled, because it's nonsense on my network.

hmm not sure about it tbh i am running windows 7 wait on the upgrade has well also i have 2 macbook and imac

today have update one my pc to windows 10 pro start to get an errors

in my syslog

 

Jul 29 20:25:11 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

Jul 29 20:25:11 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

Jul 29 20:25:11 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

Jul 29 20:25:11 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

Jul 29 20:25:25 Tower avahi-daemon[1623]: Invalid response packet from host 192.168.0.112.

 

There are several reports of that, always involving a Windows 10 station.  I'm not sure anything can be done about it in unRAID, until either the kernel networking modules or the Windows 10 machine are updated to fix it or ignore it.

in the long term will this error effect the unraid server if i simply ignore it

in the long term will this error effect the unraid server if i simply ignore it

 

It's an 'Invalid response packet'!  It's like asking a question, and getting an answer in gibberish.  It can't hurt you, and most of us ignore it and walk away.  It's not the response you were expecting, so if it makes you feel better, you can punch the guy, or punch the Windows 10 machine!   

 

You can't get paranoid about things that show up in a syslog.  Linux syslogs have much more of the nitty gritty of complex systems of complex sub-systems trying to work together, each one full of patches and workarounds.  These things happen just as often (or more) in Windows machines, but aren't reported to you (the 'ignorance is bliss' principle).

It's enabled so that someone can access the webGui via OS X using "tower.local" in the browser address bar instead of server's IP address.

It's enabled so that someone can access the webGui via OS X using "tower.local" in the browser address bar instead of server's IP address.

The logical next question is can you add a setting to disable it? 

I had this issue in windows 8 too. it went away, dont remember what i did or if i even did anything, but after upgrading 2 computers to 10, it's back.

i think i've found the answer.. i disabled ipv6 on both my win10 computers since i wasn't using it anyway and the avahi-daemon log entries have stopped,

i have disabled ipv6 on windows 10 pro computer and still get the error odd times