c48ad644c0
Newer NetworkManager versions will run the dispatcher scripts when new unknown interfaces show up, including 'clat'. That will cause a clatd restart right after startup, and we'll never get to fully initialise. So ensure the dispatcher script does nothing if the device in question is our own 'clat' to prevent this.
32 lines
1.1 KiB
Bash
32 lines
1.1 KiB
Bash
#!/bin/sh
|
|
#
|
|
# clatd dispatcher script for NetworkManager
|
|
#
|
|
# Install it to: /etc/NetworkManager/dispatcher.d/50-clatd
|
|
#
|
|
# Written by Tore Anderson <tore@fud.no>
|
|
#
|
|
|
|
# Newer NetworkManager versions will run the dispatcher scripts once
|
|
# a new unmanaged interface shows up, including the 'clat' interface
|
|
# created by clatd/TAYGA. So if we're being called due to our own
|
|
# interface showing up, do nothing, otherwise we will end up
|
|
# committing suicide from the restarts below
|
|
[ "$DEVICE_IFACE" = "clat" ] && exit 0
|
|
|
|
# We simply restart clatd in all situations, as no matter if an interface
|
|
# goes up or down, it may mean that the PLAT device changes, it may mean
|
|
# native IPv4 appearing or disappearing, or it may mean that DNS64 became
|
|
# available or unavailable...it's far easier to simply restart always and
|
|
# start from scratch than to figure out if a restart is truly necessary
|
|
|
|
# systemd-based distros
|
|
if test -x /usr/bin/systemctl; then
|
|
/usr/bin/systemctl restart clatd.service
|
|
fi
|
|
|
|
# upstart-based distros
|
|
if test -x /sbin/initctl; then
|
|
/sbin/initctl restart clatd
|
|
fi
|