Okay, it was not as easy as just killing avahi-autoipd service when up (or any dhcp) event took place in dispatcher. This approach led to new ipv4ll address because, when avahi-autoipd re-started some other party reported "conflict" with that old address and avahi-autoipd selected new one. This was not what I wanted.
So, instead of killing avahi-autoipd, I just executed /etc/avahi/avahi-autoipd.action script with BIND mode provided that avahi-autoipd was found from ps list bound to valid address. Other-vice I restarted avahi-autoipd like the original plan was. -Matti 2016-04-15 20:33 GMT+03:00 matti kaasinen <[email protected]>: > > 2016-04-15 19:22 GMT+03:00 Thomas Haller <[email protected]>: > >> Also, "eth0:avahi" sounds more like an interface-alias. That is not a >> separate (real) interface, just one address that is show by ifconfig >> tool as a separate interface (but it isn't). See `ip addr show`. >> > > > Interface alias is goodenough for me as along as it responds to both > addresses as it does by my experience. >
_______________________________________________ networkmanager-list mailing list [email protected] https://mail.gnome.org/mailman/listinfo/networkmanager-list
