The issue is still around with avahi 0.7+ and an Airport Express (1st Gen) even if pinging the device resolves the Airport-IP correctly. No streaming possible because Pulseaudio tries to use the wrong IP (169... rather than 192...)
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/896688 Title: avahi provides incorrect IP address to pulseaudio Status in avahi package in Ubuntu: Confirmed Bug description: Ubuntu 10.04 Packages avahi-daemon 0.6.25-1ubuntu6.2 I'm using an airport express with pulse audio and I believe avahi- daemon is providing/resolving the wrong IP address to pulse audio. Using the following command, avahi-browse -r _raop._tcp I get: + eth1 IPv4 00254B09A042@Base Station 09a043 AirTunes Remote Audio local = eth1 IPv4 00254B09A042@Base Station 09a043 AirTunes Remote Audio local hostname = [Base-Station-09a043.local] address = [169.254.135.173] port = [5000] txt = ["sf=0x5" "fv=74200.9" "am=AirPort4,107" "vs=101.9" "tp=TCP,UDP" "vn=65537" "pw=false" "ss=16" "sr=44100" "da=true" "sv=false" "et=0,1" "ek=1" "cn=0,1" "ch=2" "txtvers=1"] where the address (169.254.135.173) is incorrect. It should be a 192.168.1.X address which is already assigned to the APEX from the router using DHCP. I've had to specify the correct IP address to pulseaudio when I manually load the module_raop_sink module in order for it to properly stream music to it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/896688/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
