Am 24.01.25 um 18:49 schrieb Michael Biebl:
Am 24.01.25 um 18:20 schrieb Martin-Éric Racine:
It has been ages since I resorted to purging avahi-autoipd as a solution, but of what I recall a 169.254.0.0 route kept on appearing regardless of whether we had acquired an outside IP or not. As soon as I purged it, dhcpcd handled the whole process itself without interference.Could you elaborate how this route entry interferes with dhcpcd or what exactly you mean by interference?I'd first like to understand, why adding this route entry is problematic in case dhcpcd handles an interface.
This route entry, that is added by /etc/network/if-up.d/avahi-autoipd is completely benign if an IP has successfully been acquired via DHCP.
If dhcpcd fails to acquire an IP address via DHCP, it will add a 169.254.0.0 route entry itself. This is done before the if-up.d hooks are called.
As a result, the avahi-autoipd hook will be a NOP: "ip route show | grep -q '^169.254.0.0/16[[:space:]]' && exit 0"So I'm still trying to understand, where exactly avahi-autoipd interferes with dhcpcd and it would help, if you can provide more details.
Michael
OpenPGP_signature.asc
Description: OpenPGP digital signature
