avahi-daemon drops connections when interface is added

[Jamie Strandboge]

Binary package hint: avahi-daemon

When a new interface is added, avahi-daemon registers the new addresses for that interface. However, in the process it causes avahi aware applications to drop their connections.

For example, when using rhythmbox to listen to a daap server, if I start up a kvm guest (which brings up a vnet* interface), rhythmbox loses its connection to the daap server.

[Jamie Strandboge (jdstrand)]

Reproducer:

1. apt-get install libvirt-bin
2. start rhythmbox and listen to a daap share
3. /etc/init.d/libvirt-bin stop
4. /etc/init.d/libvirt-bin start

Rhythmbox stops playing.

Here are the syslog messages:
Apr 2 09:33:38 severus libvirtd: Shutting down on signal 15
Apr 2 09:33:38 severus dnsmasq[11961]: exiting on receipt of SIGTERM
Apr 2 09:33:38 severus avahi-daemon[5884]: Interface vnet0.IPv4 no longer relevant for mDNS.
Apr 2 09:33:38 severus avahi-daemon[5884]: Leaving mDNS multicast group on interface vnet0.IPv4 with address 192.168.122.1.
Apr 2 09:33:38 severus avahi-daemon[5884]: Withdrawing address record for fe80::c8ef:52ff:fe7b:7004 on vnet0.
Apr 2 09:33:38 severus avahi-daemon[5884]: Withdrawing address record for 192.168.122.1 on vnet0.
Apr 2 09:33:40 severus kernel: [49186.956005] vnet0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.
Apr 2 09:33:40 severus kernel: [49186.958592] vnet0: starting userspace STP failed, starting kernel STP
Apr 2 09:33:40 severus avahi-daemon[5884]: Joining mDNS multicast group on interface vnet0.IPv4 with address 192.168.122.1.
Apr 2 09:33:40 severus avahi-daemon[5884]: New relevant interface vnet0.IPv4 for mDNS.
Apr 2 09:33:40 severus avahi-daemon[5884]: Registering new address record for 192.168.122.1 on vnet0.IPv4.
Apr 2 09:33:40 severus dnsmasq[12120]: started, version 2.41 cachesize 150
Apr 2 09:33:40 severus dnsmasq[12120]: compile time options: IPv6 GNU-getopt no-ISC-leasefile DBus I18N TFTP
Apr 2 09:33:40 severus dnsmasq[12120]: DHCP, IP range 192.168.122.67 -- 192.168.122.254, lease time 1h
Apr 2 09:33:40 severus dnsmasq[12120]: reading /etc/resolv.conf
Apr 2 09:33:40 severus dnsmasq[12120]: using nameserver 170.215.255.114#53
Apr 2 09:33:40 severus dnsmasq[12120]: using nameserver 66.133.170.2#53
Apr 2 09:33:40 severus dnsmasq[12120]: using nameserver 192.168.3.2#53
Apr 2 09:33:40 severus dnsmasq[12120]: read /etc/hosts - 23 addresses
Apr 2 09:33:41 severus avahi-daemon[5884]: Registering new address record for fe80::d486:aff:fe21:1016 on vnet0.*.
Apr 2 09:33:50 severus kernel: [49197.390730] vnet0: no IPv6 routers present

[Jamie Strandboge (jdstrand)]

I should mention this is on an up to date Hardy/amd64

[James Westby (james-w)]

Hi,

Thanks for taking the time to report this issue. I have forwarded
the problem upstream.

Thanks,

James

[James Westby (james-w)]

Hi,

The upstream author says that this has nothing to do
with avahi.

Thanks,

James

[James Westby (james-w)]

Hi Jamie,

Have you observed this behaviour with anything other than rhythmbox?

Thanks,

James

[James Westby (james-w)]

I've added a rhythmbox task, as that is the most likely candidate
for this problem.

What could be happening is that the announcement of the new interface
by avahi makes the rhythmbox plugin forget the current connection.

Thanks,

James

[Jamie Strandboge (jdstrand)]

I am marking this as 'Fix Released' because I don't see this anymore on an up to date Hardy system.