This bug has been raised with Avahi as http://avahi.org/ticket/352 but there doesn't seem to have been any action on this in 4 years.
I'm going to contact them. I've got tcpdump's of the packets.
I'm seeing these apparently bad packets come from a Windows 10 pre-release build 10240 machine. I guess I'm going to see a lot more with Windows 10 being offically released on 29/7/2015.
These messages are appearing in syslog for my machines:
Ubuntu 12.04 avahi-daemon 0.6.30-5ubuntu2
Ubuntu 14.04 avahi-daemon 0.6.31-4ubuntu1
This bug has been raised with Avahi as http:// avahi.org/ ticket/ 352 but there doesn't seem to have been any action on this in 4 years.
I'm going to contact them. I've got tcpdump's of the packets.
I'm seeing these apparently bad packets come from a Windows 10 pre-release build 10240 machine. I guess I'm going to see a lot more with Windows 10 being offically released on 29/7/2015.
These messages are appearing in syslog for my machines:
Ubuntu 12.04 avahi-daemon 0.6.30-5ubuntu2
Ubuntu 14.04 avahi-daemon 0.6.31-4ubuntu1
Looks like server.c code used in Ubuntu Wily 15.04 has not had the patch above applied. bazaar. launchpad. net/~ubuntu- branches/ ubuntu/ wily/avahi/ wily/view/ head:/avahi- core/server. c
See http://
Vivid 14.10 + Wily 15.04 both use 0.6.31-4ubuntu4.
Turning off IPv6 (leaving IPv4 on), on the Windows 10 machine stops the messages.