avahi-daemon[12278]: Invalid response packet from host

I've just noticed these entries in the Syslog.  Not typical errors I see and ignore, so I wanted to see if someone might know the cause and if their is a simple fix or not.

 

For reference, the two devices related to the IP's in the BOLD lines below are both mine (my Blackberry and my Laptop).

 

I ran a command I seen someone else suggest elsewhere (results further below) and what stands out is this part:

RX packets:36049503 errors:0 dropped:49278

 

Jul 26 09:26:59 Tower avahi-daemon[12278]: Invalid response packet from host 192.168.1.32.

Jul 26 09:30:17 Tower avahi-daemon[12278]: Invalid response packet from host 192.168.1.32.

Jul 26 09:33:37 Tower avahi-daemon[12278]: Invalid response packet from host 192.168.1.32.

Jul 26 09:36:55 Tower avahi-daemon[12278]: Invalid response packet from host 192.168.1.32.

Jul 26 13:05:36 Tower kernel: mdcmd (168): spindown 0 (Routine)

Jul 26 13:05:37 Tower kernel: mdcmd (169): spindown 1 (Routine)

Jul 26 13:05:38 Tower kernel: mdcmd (170): spindown 6 (Routine)

Jul 26 13:05:38 Tower kernel: mdcmd (171): spindown 7 (Routine)

Jul 26 13:05:38 Tower kernel: mdcmd (172): spindown 8 (Routine)

Jul 26 13:05:38 Tower kernel: mdcmd (173): spindown 9 (Routine)

Jul 26 13:05:39 Tower kernel: mdcmd (174): spindown 10 (Routine)

Jul 26 13:05:39 Tower kernel: mdcmd (175): spindown 11 (Routine)

Jul 26 13:49:44 Tower kernel: mvsas 0000:02:00.0: Phy2 : No sig fis (Drive related)

Jul 26 13:49:50 Tower kernel: mvsas 0000:02:00.0: Phy2 : No sig fis (Drive related)

Jul 26 13:49:53 Tower kernel: sas: sas_form_port: phy2 belongs to port2 already(1)! (Drive related)

Jul 26 15:53:51 Tower kernel: mdcmd (176): spindown 3 (Routine)

Jul 26 16:54:01 Tower kernel: mdcmd (177): spindown 1 (Routine)

Jul 26 16:54:01 Tower kernel: mdcmd (178): spindown 6 (Routine)

Jul 26 16:54:01 Tower kernel: mdcmd (179): spindown 7 (Routine)

Jul 26 16:54:01 Tower kernel: mdcmd (180): spindown 8 (Routine)

Jul 26 16:54:02 Tower kernel: mdcmd (181): spindown 9 (Routine)

Jul 26 16:54:03 Tower kernel: mdcmd (182): spindown 10 (Routine)

Jul 26 16:54:03 Tower kernel: mdcmd (183): spindown 11 (Routine)

Jul 26 17:14:58 Tower kernel: mdcmd (184): spindown 3 (Routine)

Jul 26 17:34:51 Tower avahi-daemon[12278]: Invalid response packet from host 192.168.1.33.

Jul 26 19:18:39 Tower avahi-daemon[12278]: Invalid response packet from host 192.168.1.33.

Jul 26 19:55:01 Tower kernel: mdcmd (185): spindown 1 (Routine)

Jul 26 19:55:01 Tower kernel: mdcmd (186): spindown 6 (Routine)

Jul 26 19:55:01 Tower kernel: mdcmd (187): spindown 7 (Routine)

Jul 26 19:55:01 Tower kernel: mdcmd (188): spindown 8 (Routine)

Jul 26 19:55:02 Tower kernel: mdcmd (189): spindown 9 (Routine)

Jul 26 19:55:03 Tower kernel: mdcmd (190): spindown 10 (Routine)

Jul 26 19:55:03 Tower kernel: mdcmd (191): spindown 11 (Routine)

Jul 26 21:24:58 Tower avahi-daemon[12278]: Invalid response packet from host 192.168.1.32

 

root@Tower:/boot# ifconfig

eth0      Link encap:Ethernet  HWaddr 00:24:1d:82:a3:25

          inet addr:192.168.1.67  Bcast:192.168.1.255  Mask:255.255.255.0

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:36049503 errors:0 dropped:49278 overruns:0 frame:0

          TX packets:140154624 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3870129206 (3.6 GiB)  TX bytes:2431865073 (2.2 GiB)

          Interrupt:40 Base address:0xc000

 

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:13092 errors:0 dropped:0 overruns:0 frame:0

          TX packets:13092 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:0

          RX bytes:2048717 (1.9 MiB)  TX bytes:2048717 (1.9 MiB)

 

Server - 12 drives:  11 Data, 1 Parity

unRAID Server Pro version: 5.0.5