(At this point, mt-daapd is registered but not on the Ethernet link.)
6) /etc/init.d/networking start
I was then hoping that avahi-daemon would register the new interface but that the DAAP service would not be visible on the network. This wasn't the case, however, and mt-daapd appeared in a client machine's media player as soon as Avahi had done its thing. mt-daapd didn't need to disconnect or reregister.
When I take my laptop home on Saturday I will try and reproduce this with a wireless connection. It's an Intel PRO/Wireless interface, so not a perfect match to your ath9k NIC, but it might exhibit similar problems. Without a reproduce this would be quite hard to fix, unfortunately.
The bad news is I wasn't able to reproduce this last night.
To simulate the problem, I did:
1) /etc/init. d/mt-daapd stop d/avahi- daemon stop d/networking stop
2) /etc/init.
3) /etc/init.
4) /etc/init. d/avahi- daemon start d/mt-daapd start
5) /etc/init.
(At this point, mt-daapd is registered but not on the Ethernet link.)
6) /etc/init. d/networking start
I was then hoping that avahi-daemon would register the new interface but that the DAAP service would not be visible on the network. This wasn't the case, however, and mt-daapd appeared in a client machine's media player as soon as Avahi had done its thing. mt-daapd didn't need to disconnect or reregister.
When I take my laptop home on Saturday I will try and reproduce this with a wireless connection. It's an Intel PRO/Wireless interface, so not a perfect match to your ath9k NIC, but it might exhibit similar problems. Without a reproduce this would be quite hard to fix, unfortunately.