Re: NM-vpn no vpn secrets
On Thu, 2010-01-21 at 10:26 +0100, Ferry Toth wrote: > Yes, the X.509 Certificates method is used. The Certificate requires a > key, the Key file has no password. The results is that about once in 5 > tries the connection gets established, possibly depending on the time > between retries. > > The workaround just switches to X.509 with password, changes no other > settings, and I fill in a bogus username and password as Anton > suggests. Now the connection always is established in one try. Yeah, this is obviously sub-optimal for two reasons; (1) your private key is not encrypted and thus is vulnerable, and (2) the UI doesn't detect an unencrypted private key and handle it properly. Dan > > --- > Ferry Toth > Oranjeplantage 34 > 2611 TK Delft > Nederland > Tel: +31(15)2133191 > > > On wo, 2010-01-20 at 15:05 -0800, Dan Williams wrote: > > On Wed, 2010-01-20 at 23:36 +0100, Ferry Toth wrote: > > > Dan, > > > > > > Yes I deleted that. What was before were the messages that you get > > > when successfully establishing a VPN connection. SIGTERM[hard,] > > > happens because I manually close the vpn at that point. I assumed > > > those log before were not that interesting. > > > > > > BTW Anton Lindström found a work around the problem > > > Anton Lindström wrote on 2009-12-04: #97 > > > (https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/453807), > > > transcription follows: > > > > > > Just want to comment that I have found a workaround for > > > network-manager-openvpn: Instead of selecting authentication type > > > "Certificate (TLS)" (I'm translating this to English so it might not > > > be exactly the same) I select "Password with certificate (TLS)". Then > > > I fill in a bogus username and password. > > > > Ok, I assume that you are using a TLS connection and the private key is > > *not* protected iwth a password? > > > > Dan > > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
Yes, the X.509 Certificates method is used. The Certificate requires a key, the Key file has no password. The results is that about once in 5 tries the connection gets established, possibly depending on the time between retries. The workaround just switches to X.509 with password, changes no other settings, and I fill in a bogus username and password as Anton suggests. Now the connection always is established in one try. --- Ferry Toth Oranjeplantage 34 2611 TK Delft Nederland Tel: +31(15)2133191 On wo, 2010-01-20 at 15:05 -0800, Dan Williams wrote: > On Wed, 2010-01-20 at 23:36 +0100, Ferry Toth wrote: > > Dan, > > > > Yes I deleted that. What was before were the messages that you get > > when successfully establishing a VPN connection. SIGTERM[hard,] > > happens because I manually close the vpn at that point. I assumed > > those log before were not that interesting. > > > > BTW Anton Lindström found a work around the problem > > Anton Lindström wrote on 2009-12-04: #97 > > (https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/453807), > > transcription follows: > > > > Just want to comment that I have found a workaround for > > network-manager-openvpn: Instead of selecting authentication type > > "Certificate (TLS)" (I'm translating this to English so it might not > > be exactly the same) I select "Password with certificate (TLS)". Then > > I fill in a bogus username and password. > > Ok, I assume that you are using a TLS connection and the private key is > *not* protected iwth a password? > > Dan > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
On Wed, 2010-01-20 at 23:36 +0100, Ferry Toth wrote: > Dan, > > Yes I deleted that. What was before were the messages that you get > when successfully establishing a VPN connection. SIGTERM[hard,] > happens because I manually close the vpn at that point. I assumed > those log before were not that interesting. > > BTW Anton Lindström found a work around the problem > Anton Lindström wrote on 2009-12-04: #97 > (https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/453807), > transcription follows: > > Just want to comment that I have found a workaround for > network-manager-openvpn: Instead of selecting authentication type > "Certificate (TLS)" (I'm translating this to English so it might not > be exactly the same) I select "Password with certificate (TLS)". Then > I fill in a bogus username and password. Ok, I assume that you are using a TLS connection and the private key is *not* protected iwth a password? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
Dan, Yes I deleted that. What was before were the messages that you get when successfully establishing a VPN connection. SIGTERM[hard,] happens because I manually close the vpn at that point. I assumed those log before were not that interesting. BTW Anton Lindström found a work around the problem Anton Lindström wrote on 2009-12-04: #97 (https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/453807), transcription follows: Just want to comment that I have found a workaround for network-manager-openvpn: Instead of selecting authentication type "Certificate (TLS)" (I'm translating this to English so it might not be exactly the same) I select "Password with certificate (TLS)". Then I fill in a bogus username and password. This works for me for now. --- Ferry Toth Oranjeplantage 35 2611 TK Delft Nederland Tel: +31(15)2133191 -Oorspronkelijke bericht- Van: Dan Williams Aan: Ferry Toth Cc: networkmanager-list@gnome.org Onderwerp: Re: NM-vpn no vpn secrets Datum: Wed, 20 Jan 2010 13:00:04 -0800 On Fri, 2009-12-18 at 09:09 +0100, Ferry Toth wrote: > Hello Dan > > Doing as you told (killing and starting the service as sudo) i have the > following results: > > The error message from nm-applet is that the vpn-service can not b e > started. When this happens there are no messages in the terminal. > > When I retry this a few times then hundreds of messages appear and the > vpn connection is setup normally. I think this will not be to > interresting. > > Finally closing vpn and then try to reopen gives the following: > > > Fri Dec 18 09:04:09 2009 us=69544 SIGTERM[hard,] received, process > exiting > Fri Dec 18 09:04:09 2009 us=70616 PKCS#11: pkcs11_terminate - entered > Fri Dec 18 09:04:09 2009 us=70716 PKCS#11: pkcs11h_terminate entry > Fri Dec 18 09:04:09 2009 us=70758 PKCS#11: Removing providers > Fri Dec 18 09:04:09 2009 us=70795 PKCS#11: Releasing sessions > Fri Dec 18 09:04:09 2009 us=70829 PKCS#11: Terminating slotevent > Fri Dec 18 09:04:09 2009 us=70864 PKCS#11: _pkcs11h_slotevent_terminate > entry > Fri Dec 18 09:04:09 2009 us=70899 PKCS#11: _pkcs11h_slotevent_terminate > return > Fri Dec 18 09:04:09 2009 us=70933 PKCS#11: Marking as uninitialized > Fri Dec 18 09:04:09 2009 us=70983 PKCS#11: pkcs11_terminate - return > ** Message: Connect timer expired, disconnecting. Do you get anything from openvpn *before* the SIGTERM[hard,] bits? We're more interested in what happens before that. Dan > ** (process:20896): WARNING **: connect_timer_expired(): > Disconnect failed: Could not process the request because no VPN > connection was active. > > ** Message: Connect timer expired, disconnecting. > Op donderdag 17-12-2009 om 14:54 uur [tijdzone -0800], schreef Dan > Williams: > > /usr/lib/network-manager-openvpn/nm-openvpn-service > > > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
On Fri, 2009-12-18 at 09:09 +0100, Ferry Toth wrote: > Hello Dan > > Doing as you told (killing and starting the service as sudo) i have the > following results: > > The error message from nm-applet is that the vpn-service can not b e > started. When this happens there are no messages in the terminal. > > When I retry this a few times then hundreds of messages appear and the > vpn connection is setup normally. I think this will not be to > interresting. > > Finally closing vpn and then try to reopen gives the following: > > > Fri Dec 18 09:04:09 2009 us=69544 SIGTERM[hard,] received, process > exiting > Fri Dec 18 09:04:09 2009 us=70616 PKCS#11: pkcs11_terminate - entered > Fri Dec 18 09:04:09 2009 us=70716 PKCS#11: pkcs11h_terminate entry > Fri Dec 18 09:04:09 2009 us=70758 PKCS#11: Removing providers > Fri Dec 18 09:04:09 2009 us=70795 PKCS#11: Releasing sessions > Fri Dec 18 09:04:09 2009 us=70829 PKCS#11: Terminating slotevent > Fri Dec 18 09:04:09 2009 us=70864 PKCS#11: _pkcs11h_slotevent_terminate > entry > Fri Dec 18 09:04:09 2009 us=70899 PKCS#11: _pkcs11h_slotevent_terminate > return > Fri Dec 18 09:04:09 2009 us=70933 PKCS#11: Marking as uninitialized > Fri Dec 18 09:04:09 2009 us=70983 PKCS#11: pkcs11_terminate - return > ** Message: Connect timer expired, disconnecting. Do you get anything from openvpn *before* the SIGTERM[hard,] bits? We're more interested in what happens before that. Dan > ** (process:20896): WARNING **: connect_timer_expired(): > Disconnect failed: Could not process the request because no VPN > connection was active. > > ** Message: Connect timer expired, disconnecting. > Op donderdag 17-12-2009 om 14:54 uur [tijdzone -0800], schreef Dan > Williams: > > /usr/lib/network-manager-openvpn/nm-openvpn-service > > > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
Hello Dan Doing as you told (killing and starting the service as sudo) i have the following results: The error message from nm-applet is that the vpn-service can not b e started. When this happens there are no messages in the terminal. When I retry this a few times then hundreds of messages appear and the vpn connection is setup normally. I think this will not be to interresting. Finally closing vpn and then try to reopen gives the following: Fri Dec 18 09:04:09 2009 us=69544 SIGTERM[hard,] received, process exiting Fri Dec 18 09:04:09 2009 us=70616 PKCS#11: pkcs11_terminate - entered Fri Dec 18 09:04:09 2009 us=70716 PKCS#11: pkcs11h_terminate entry Fri Dec 18 09:04:09 2009 us=70758 PKCS#11: Removing providers Fri Dec 18 09:04:09 2009 us=70795 PKCS#11: Releasing sessions Fri Dec 18 09:04:09 2009 us=70829 PKCS#11: Terminating slotevent Fri Dec 18 09:04:09 2009 us=70864 PKCS#11: _pkcs11h_slotevent_terminate entry Fri Dec 18 09:04:09 2009 us=70899 PKCS#11: _pkcs11h_slotevent_terminate return Fri Dec 18 09:04:09 2009 us=70933 PKCS#11: Marking as uninitialized Fri Dec 18 09:04:09 2009 us=70983 PKCS#11: pkcs11_terminate - return ** Message: Connect timer expired, disconnecting. ** (process:20896): WARNING **: connect_timer_expired(): Disconnect failed: Could not process the request because no VPN connection was active. ** Message: Connect timer expired, disconnecting. Op donderdag 17-12-2009 om 14:54 uur [tijdzone -0800], schreef Dan Williams: > /usr/lib/network-manager-openvpn/nm-openvpn-service > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
On Thu, 2009-12-17 at 09:21 +0100, Ferry Toth wrote: > I am on Karmic. > > Actually if a try multiple times to connect after 3 attempts (or so) it > will connect. > > Tried the suggestion below, but Karmic also does not use libexec. I have > no idea how to start up the service on Karmic. Any suggestions? /usr/lib/network-manager-openvpn/nm-openvpn-service or on 64-bit systems I assume it is: /usr/lib64/network-manager-openvpn/nm-openvpn-service use those with OPENVPN_DEBUG=1 for the detailed logs. Dan > Ferry > > Op woensdag 16-12-2009 om 17:27 uur [tijdzone -0800], schreef Dan > Williams: > > On Sun, 2009-12-06 at 22:55 +0100, Ferry Toth wrote: > > > I confirm this issue. > > > > > > However in my sometimes NM connects to the vpn (openvpn) without > > > problems and sometimes is doesn't. This does not depend on the openvpn > > > server as other machines work fine,as well a previous version of > > > nm-applet. > > > > > > I my case I have a CA cert, a certificate and a key cert (which does > > > not need a password). > > > > > > It may be a problem with the state machine of the networkwork manager? > > > > If you want more information about the problem, you can (as root): > > > > 1) killall -TERM nm-openvpn-service > > 2) OPENVPN_DEBUG=1 /usr/libexec/nm-openvpn-service > >(or wherever it's at on your system, Debian doesn't use libexec) > > > > and then try to connect. It'll spew out a load of debugging information > > which is necessary to figure out what's going wrong. > > > > Dan > > > > > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
I am on Karmic. Actually if a try multiple times to connect after 3 attempts (or so) it will connect. Tried the suggestion below, but Karmic also does not use libexec. I have no idea how to start up the service on Karmic. Any suggestions? Ferry Op woensdag 16-12-2009 om 17:27 uur [tijdzone -0800], schreef Dan Williams: > On Sun, 2009-12-06 at 22:55 +0100, Ferry Toth wrote: > > I confirm this issue. > > > > However in my sometimes NM connects to the vpn (openvpn) without > > problems and sometimes is doesn't. This does not depend on the openvpn > > server as other machines work fine,as well a previous version of > > nm-applet. > > > > I my case I have a CA cert, a certificate and a key cert (which does > > not need a password). > > > > It may be a problem with the state machine of the networkwork manager? > > If you want more information about the problem, you can (as root): > > 1) killall -TERM nm-openvpn-service > 2) OPENVPN_DEBUG=1 /usr/libexec/nm-openvpn-service >(or wherever it's at on your system, Debian doesn't use libexec) > > and then try to connect. It'll spew out a load of debugging information > which is necessary to figure out what's going wrong. > > Dan > > ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
On Sun, 2009-12-06 at 22:55 +0100, Ferry Toth wrote: > I confirm this issue. > > However in my sometimes NM connects to the vpn (openvpn) without > problems and sometimes is doesn't. This does not depend on the openvpn > server as other machines work fine,as well a previous version of > nm-applet. > > I my case I have a CA cert, a certificate and a key cert (which does > not need a password). > > It may be a problem with the state machine of the networkwork manager? If you want more information about the problem, you can (as root): 1) killall -TERM nm-openvpn-service 2) OPENVPN_DEBUG=1 /usr/libexec/nm-openvpn-service (or wherever it's at on your system, Debian doesn't use libexec) and then try to connect. It'll spew out a load of debugging information which is necessary to figure out what's going wrong. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
I confirm this issue. However in my sometimes NM connects to the vpn (openvpn) without problems and sometimes is doesn't. This does not depend on the openvpn server as other machines work fine,as well a previous version of nm-applet. I my case I have a CA cert, a certificate and a key cert (which does not need a password). It may be a problem with the state machine of the networkwork manager? -- Ferry Toth -Oorspronkelijke bericht- Van: Dan Williams Aan: Alexander Sack Cc: Neal Becker , networkmanager-list@gnome.org Onderwerp: Re: NM-vpn no vpn secrets Datum: Fri, 04 Dec 2009 12:24:13 -0800 Nieuwsgroepen: gmane.linux.network.networkmanager.devel On Thu, 2009-12-03 at 12:34 +0100, Alexander Sack wrote: > On Wed, Dec 02, 2009 at 07:17:46PM -0500, Neal Becker wrote: > > On Wednesday 02 December 2009, Dan Williams wrote: > > > What appears to be the issue here is that you haven't set any secrets in > > > the connection editor the VPN. That means passwords, shared keys, etc. > > > Or that the secrets didn't pass validation. When you open the > > > connection editor, are your passwords still there? If you're not > > > entering any, are you asked for a password when you connect? > > > > > > Dan > > > > > > > I entered the certificates. Same as I use to start openvpn manually. No > > password is needed, and none is entered into 'Private key password' field > > (if > > that's what you mean). > > > > I don't know if it's a permission issue. The private key can only be read > > as > > root (but of course, that's normal). > > I remember that there was a bug about not being able to configure VPNs > that have no password. maybe thats the case here? Maybe just an overly > strict settings verify? NetworkManager in general does not support unencrypted private keys because these configurations are not secure. You'll want to encrypt your private key using openssl and provide a private key password. Your private key password is stored securely in the keyring. I've recently added some UI to nm-applet/nm-connection-editor that warn you if the private key is not encrypted, and we should probably add that same UI to nm-openvpn. In any case, nm-openvpn should not enable the Apply button unless a private key is entered, which doesn't seem to be the case. I'll fix that. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
On Thu, 2009-12-03 at 12:34 +0100, Alexander Sack wrote: > On Wed, Dec 02, 2009 at 07:17:46PM -0500, Neal Becker wrote: > > On Wednesday 02 December 2009, Dan Williams wrote: > > > What appears to be the issue here is that you haven't set any secrets in > > > the connection editor the VPN. That means passwords, shared keys, etc. > > > Or that the secrets didn't pass validation. When you open the > > > connection editor, are your passwords still there? If you're not > > > entering any, are you asked for a password when you connect? > > > > > > Dan > > > > > > > I entered the certificates. Same as I use to start openvpn manually. No > > password is needed, and none is entered into 'Private key password' field > > (if > > that's what you mean). > > > > I don't know if it's a permission issue. The private key can only be read > > as > > root (but of course, that's normal). > > I remember that there was a bug about not being able to configure VPNs > that have no password. maybe thats the case here? Maybe just an overly > strict settings verify? NetworkManager in general does not support unencrypted private keys because these configurations are not secure. You'll want to encrypt your private key using openssl and provide a private key password. Your private key password is stored securely in the keyring. I've recently added some UI to nm-applet/nm-connection-editor that warn you if the private key is not encrypted, and we should probably add that same UI to nm-openvpn. In any case, nm-openvpn should not enable the Apply button unless a private key is entered, which doesn't seem to be the case. I'll fix that. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
On Wed, Dec 02, 2009 at 07:17:46PM -0500, Neal Becker wrote: > On Wednesday 02 December 2009, Dan Williams wrote: > > What appears to be the issue here is that you haven't set any secrets in > > the connection editor the VPN. That means passwords, shared keys, etc. > > Or that the secrets didn't pass validation. When you open the > > connection editor, are your passwords still there? If you're not > > entering any, are you asked for a password when you connect? > > > > Dan > > > > I entered the certificates. Same as I use to start openvpn manually. No > password is needed, and none is entered into 'Private key password' field (if > that's what you mean). > > I don't know if it's a permission issue. The private key can only be read as > root (but of course, that's normal). I remember that there was a bug about not being able to configure VPNs that have no password. maybe thats the case here? Maybe just an overly strict settings verify? - Alexander ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
On Wednesday 02 December 2009, Dan Williams wrote: > On Mon, 2009-11-30 at 08:17 -0500, Neal Becker wrote: > > Fedora F12 > > > > I can start vpn fine using service openvpn start. But using nm- > > applet, > > it doesn't work. > > Any ideas what I need to do here? All the debugging I can find is > > this: > > > > Nov 29 09:36:48 localhost NetworkManager: Starting VPN > > service > > 'org.freedesktop.NetworkManager.openvpn'... > > Nov 29 09:36:48 localhost NetworkManager: VPN service > > 'org.freedesktop.NetworkManager.openvpn' started > > (org.freedesktop.NetworkManager.openvpn), PID 14227 > > Nov 29 09:36:48 localhost NetworkManager: VPN service > > 'org.freedesktop.NetworkManager.openvpn' just appeared, activating > > connections > > Nov 29 09:36:48 localhost NetworkManager: VPN plugin state > > changed: 3 > > Nov 29 09:36:48 localhost NetworkManager: VPN connection > > 'nbecker' (Connect) reply received. > > Nov 29 09:36:48 localhost NetworkManager: > > nm_vpn_connection_connect_cb(): VPN connection 'nbecker' failed to > > connect: 'No VPN secrets!'. > > What appears to be the issue here is that you haven't set any secrets in > the connection editor the VPN. That means passwords, shared keys, etc. > Or that the secrets didn't pass validation. When you open the > connection editor, are your passwords still there? If you're not > entering any, are you asked for a password when you connect? > > Dan > I entered the certificates. Same as I use to start openvpn manually. No password is needed, and none is entered into 'Private key password' field (if that's what you mean). I don't know if it's a permission issue. The private key can only be read as root (but of course, that's normal). ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
On Mon, 2009-11-30 at 08:17 -0500, Neal Becker wrote: > Fedora F12 > > I can start vpn fine using service openvpn start. But using nm- > applet, > it doesn't work. > Any ideas what I need to do here? All the debugging I can find is > this: > > Nov 29 09:36:48 localhost NetworkManager: Starting VPN > service > 'org.freedesktop.NetworkManager.openvpn'... > Nov 29 09:36:48 localhost NetworkManager: VPN service > 'org.freedesktop.NetworkManager.openvpn' started > (org.freedesktop.NetworkManager.openvpn), PID 14227 > Nov 29 09:36:48 localhost NetworkManager: VPN service > 'org.freedesktop.NetworkManager.openvpn' just appeared, activating > connections > Nov 29 09:36:48 localhost NetworkManager: VPN plugin state > changed: 3 > Nov 29 09:36:48 localhost NetworkManager: VPN connection > 'nbecker' (Connect) reply received. > Nov 29 09:36:48 localhost NetworkManager: > nm_vpn_connection_connect_cb(): VPN connection 'nbecker' failed to > connect: 'No VPN secrets!'. What appears to be the issue here is that you haven't set any secrets in the connection editor the VPN. That means passwords, shared keys, etc. Or that the secrets didn't pass validation. When you open the connection editor, are your passwords still there? If you're not entering any, are you asked for a password when you connect? Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
On Mon, 2009-11-30 at 13:21 +, Timothy Murphy wrote: > Neal Becker wrote: > > > I can start vpn fine using service openvpn start. But using nm- > > applet, > > it doesn't work. > > Any ideas what I need to do here? > > What exactly is the point of NM-vpn? > > I am running NM on my laptops, which are also OpenVPN clients, > and this appears to work perfectly well. > How does NM-vpn improve on this? It allows NM to manage the network connections and routes based on the VPN's responses and user overrides. It also provides a sane graphical UI over the most common VPN configuration options. It also allows generic scripts to plug into the NM event system and perform custom actions when certain VPN connections go up or down. There's a bit of work to do to get more of the common options handled however. Even right now you could have your application only connect to your corporate IRC server or email server *only* when your VPN is active for example. That's a lot harder with the ad-hoc mechanisms that most VPN clients currently use. Dan ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NM-vpn no vpn secrets
Neal Becker wrote: > I can start vpn fine using service openvpn start. But using nm- > applet, > it doesn't work. > Any ideas what I need to do here? What exactly is the point of NM-vpn? I am running NM on my laptops, which are also OpenVPN clients, and this appears to work perfectly well. How does NM-vpn improve on this? -- Timothy Murphy e-mail: gayleard /at/ eircom.net tel: +353-86-2336090, +353-1-2842366 s-mail: School of Mathematics, Trinity College, Dublin 2, Ireland ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
