On Fri, Nov 13, Dan Williams wrote:
> Again, if you can get dispatcher debugging that would be great. Slaves
> should never have IP information *unless it's been added externally to
> NM* by something, since they are slaves.
I think the VPN route error happend with gsm. This week the reconnect
did not even trigger the scripts.
Not sure why the eth got an address. Perhaps GNOME was messing around
with the onboard card?
I'm have this in place as a dispatcher script. Is this similar to what
the nm-dispatcher command would log?
#!/usr/bin/env bash
dnsmasq_dyn_dir="/dev/shm/dnsmasq.d"
dnsmasq_dyn_env="${dnsmasq_dyn_dir}/nm_dispatcher.env.txt"
_x() {
rm -f "${dnsmasq_dyn_env}.$$"
}
trap _x EXIT
#
mkdir -vp "${dnsmasq_dyn_dir}"
{
date -u
cat /proc/uptime
echo "$0 $*"
env | sort
} > "${dnsmasq_dyn_env}.$$"
cat "${dnsmasq_dyn_env}.$$" >> "${dnsmasq_dyn_env}"
#
Olaf
_______________________________________________
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
