On Sat, Feb 11, 2023 at 09:29:16PM -0600, David Wright wrote: > My systems all have avahi-daemon and avahi-utils installed, and the > laptops have avahi-autoipd as well, but I never see 169.254.… > addresses in the output of ip a¹ or in the logs², or in the output > of avahi-browse -art³ (which shows a driverless printer, my > apt-cacher-ng, and a TV that's switched on by chance (AirPlay/spotify)). Thanks for your insights :-) > I've read that machines give themselves a 169.254.… address when they > boot up and can't find a DHCP server. That was my take too, yes. But I think there are other mechanisms which may set up an IPv4LL. > But I never see those addresses > when I boot up a machine, disconnected or connected. All I see is > localhost on 127.0.0.1, the machine's hostname on 127.0.1.1, and > if connected, the 192.168.1.NN address handed out by DHCP. I'm sure it can be configured out from Avahi. > So it's difficult to figure out why some are plagued by these > addresses, made worse when one gets used for the default route, eg > https://lists.debian.org/debian-user/2019/07/msg00208.html > So many of the "solutions" proferred seemed to involve "nuking" avahi. My reason for "nuking" Avahi wasn't the IPv4LL. ISTR that it misbehaved once, which made me aware of its existence. Then I read up on what it does and decided "no, I don't want this on my network". Cheers -- t
Attachment:
signature.asc
Description: PGP signature