Still the same bug in Ubuntu 24.04.
I have confirmed a workaround if your Ubuntu box is on the same subnet
as the Airport device: Create a route for 169.254.0.0/16 packets to
reach the Airport device. For example, if your network adapter is eth0,
this command will add a route for the raop packets
Yes. This issue seems to be limited to Airport devices for me too. While
they are quite old now, any chance this incompatibility can be resolved
in Avahi? Correct resolution is helpful to access a Time Capsule's
network drive. Anything we can do to help debug and test? Thanks.
--
You received thi
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
I've just encountered this issue with Ubuntu 16.04 / avahi-daemon
0.6.32~rc+dfsg-1ubuntu2. I have an AirPort Time Capsule, however the
problem is the same - pinging Airport-Time-Capsule.local resolves to an
incorrect 169.254.x.x IP address. Now interestingly, none of my other
devices (Apple or Andr
This is still true for 14.04.
Even pinging it by hostname in a .local zone yields incorrect IP.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/896688
Title:
avahi provides incorrect IP address to pu
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: avahi (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/896688
Title:
avahi
