Re: Approaching NetworkManager 1.2
- From: Dan Williams <dcbw redhat com>
- To: Olaf Hering <olaf aepfle de>
- Cc: NetworkManager Discussions <networkmanager-list gnome org>
- Subject: Re: Approaching NetworkManager 1.2
- Date: Mon, 23 Nov 2015 08:52:05 -0600
On Sat, 2015-11-21 at 10:02 +0100, Olaf Hering wrote:
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?
Yeah, it should be. When you see the issue again, lets see what the
logs from the file are like.
Dan
#!/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
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]