I also have encountered this bug, and have posted details at https://github.com/avahi/avahi/issues/696
Outside Linux I have for more than 10 years reliably connected under Windows (7 through 10) via iTunes to 2 airport express units to stream audio to two different rooms. Also works without fail using iPhones. However, when attempting to do the same using shairport-sync, for one airport express (but not the other) avahi-browse -rt _raop._tcp reports the airport express as having address = [169.254.228.218] when the address assigned on my local network is 10.0.0.134. Also, avahi-resolve -4 -n Lounge-AirPort-Express.local returns Lounge-AirPort-Express.local 169.254.228.218 However, my local DHCP server assigns the airport express the IPv4 address 10.0.0.134, and ~$ nmap lounge-airport-express.local returns Starting Nmap 7.94SVN ( https://nmap.org ) at 2026-10-15 12:12 AEDT Nmap scan report for lounge-airport-express.local (10.0.0.134) Host is up (0.0026s latency). rDNS record for 10.0.0.134: lounge-airport-express.gateway Not shown: 997 closed tcp ports (conn-refused) PORT STATE SERVICE 5000/tcp open upnp 5009/tcp open airport-admin 10000/tcp open snet-sensor-mgmt Nmap done: 1 IP address (1 host up) scanned in 12.57 seconds Also when I boot under Win10 and use the airport utility it shows the airport express as having the 10.0.0.134 address and that it is set up to be assigned its address from the local DHCP server. And when I login to the local gateway, it shows the airport express as connected by wifi with an assigned IPv4 address of 10.0.0.134. Traceroute to 169.254.228.218 times out after max hops. Traceroute to 10.0.0.134 returns 1 lounge-airport-express.gateway (10.0.0.134) 2.398 ms 3.290 ms 4.518 ms I don't know where the 169.254.228.218 address comes from or how to get rid of it. This one airport express is the only device on my (very small) local network for which this happens. And as noted above, I have another airport express on my network for which this does not happen. It has the one IPv4 address as assigned by the local DHCP server (10.0.0.74), and that address is returned regardless of whether avahi or nmap or whatever, is used. I did try killing avahi-daemon to clear the cache, but the issue persists. There was an avahi-autoipd package installed on my system which is a tool that "implements IPv4LL, "Dynamic Configuration of IPv4 Link-Local Addresses" (IETF RFC3927), a protocol for automatic IP address configuration from the link-local 169.254.0.0/16 range without the need for a central server. It is primarily intended to be used in ad-hoc networks which lack a DHCP server." However I uninstalled that, so it cannot be re-assigning the 169.254 address to the airport express, yet that address persists. avahi-daemon is version 0.8 on my system. I have linked to a log file from the airport express over 2 and a half hours from a couple of days ago which shows it renewing its DHCP assigned address, with no mention of the 169 address. https://github.com/user-attachments/files/33519297/Lounge.AirPort.Express.Log.txt Excerpts of system info System: Kernel: 7.0.0-38-generic arch: x86_64 bits: 64 compiler: gcc v: 13.3.0 clocksource: tsc Desktop: Cinnamon v: 6.6.9 tk: GTK v: 3.24.41 wm: Muffin v: 6.6.3 vt: 7 dm: LightDM v: 1.30.0 Distro: Linux Mint 22.3 Zena base: Ubuntu 24.04 noble Audio: Device-1: Intel 6 Series/C200 Series Family High Definition Audio vendor: Hewlett-Packard 6 driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:1c20 class-ID: 0403 Device-2: NVIDIA GP107GL High Definition Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fb9 class-ID: 0403 API: ALSA v: k7.0.0-38-generic status: kernel-api Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin Network: Device-1: Ralink RT5392 PCIe Wireless Network Adapter driver: rt2800pci v: 2.3.0 pcie: speed: 2.5 GT/s lanes: 1 bus-ID: 03:00.0 chip-ID: 1814:5392 class-ID: 0280 IF: wlp3s0 state: down mac: <filter> Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet vendor: Hewlett-Packard RTL8111/8168/8411 driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1 port: d000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200 IF: enp5s0 state: up speed: 1000 Mbps duplex: full mac: <filter> ** Bug watch added: github.com/avahi/avahi/issues #696 https://github.com/avahi/avahi/issues/696 -- 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 pulseaudio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/896688/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
