Re: NetworkManager script dispatcher
- From: Pavel Simerda <psimerda redhat com>
- To: Paolo Bolzoni <paolo bolzoni brown gmail com>
- Cc: networkmanager-list gnome org
- Subject: Re: NetworkManager script dispatcher
- Date: Tue, 17 Dec 2013 04:51:10 -0500 (EST)
----- Original Message -----
From: "Paolo Bolzoni" <paolo bolzoni brown gmail com>
To: "Pavel Simerda" <psimerda redhat com>
Cc: networkmanager-list gnome org
Sent: Tuesday, December 17, 2013 10:43:04 AM
Subject: Re: NetworkManager script dispatcher
It wouldn't be easier add a third parameter to the network dispatcher
calls that with the cause?
In this specific case, maybe. But nmcli mostly proves to be better at least with the git master version.
Cheers,
Pavel
On Tue, Dec 17, 2013 at 9:54 AM, Pavel Simerda <psimerda redhat com> wrote:
----- Original Message -----
From: "Paolo Bolzoni" <paolo bolzoni brown gmail com>
To: networkmanager-list gnome org
Sent: Friday, December 13, 2013 5:38:57 PM
Subject: NetworkManager script dispatcher
Dear list,
I am using a vpn and I setup a script that
connects automatically when I plug a usb
external ethernet device, the script also
reconnect if the vpn connection falls down.
Now, I have some problems. The script
reconnects also if I manually disconnect
(using nm-applet or nmcli) and it messes
up if I disconnect the cable.
Is there a way to "know more" in the script
what happened? Why the vpn falls down, if
the cable is still connected...
I think the best way is to use nmcli and file individual bugs for
information not available through nmcli.
Cheers,
Pavel
Thanks,
Paolo
_______________________________________________
networkmanager-list mailing list
networkmanager-list gnome org
https://mail.gnome.org/mailman/listinfo/networkmanager-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]