From e55f174bd3a7ae82fb24afd43443d0b55d5536cf Mon Sep 17 00:00:00 2001 From: Miroslav Lichvar Date: Mon, 7 Feb 2022 13:27:48 +0100 Subject: [PATCH] examples: handle more actions in NM dispatcher script Run the chronyc onoffline command also when the connectivity-change and dhcp6-change actions are reported by the NetworkManager dispatcher. The latter should not be necessary, but there currently doesn't seem to be any action for IPv6 becoming routable after duplicate address detection, so at least in networks using DHCPv6, IPv6 NTP servers should not be stuck in the offline state from a previously reported action. --- examples/chrony.nm-dispatcher.onoffline | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/examples/chrony.nm-dispatcher.onoffline b/examples/chrony.nm-dispatcher.onoffline index 34cfa0d..01e6fdb 100644 --- a/examples/chrony.nm-dispatcher.onoffline +++ b/examples/chrony.nm-dispatcher.onoffline @@ -7,8 +7,18 @@ export LC_ALL=C chronyc=/usr/bin/chronyc -# For NetworkManager consider only up/down events -[ $# -ge 2 ] && [ "$2" != "up" ] && [ "$2" != "down" ] && exit 0 +# For NetworkManager consider only selected events +if [ $# -ge 2 ]; then + case "$2" in + up|down|connectivity-change) + ;; + dhcp6-change) + # No other action is reported for routable IPv6 + ;; + *) + exit 0;; + esac +fi # Note: for networkd-dispatcher routable.d ~= on and off.d ~= off