Automatic connect not engaging for openvpn

[Joe Baker]

Binary package hint: network-manager-openvpn

Jaunty beta updated to Release Candidate
While Network-manager allows an openvpn profile to be marked as "automaticly connect" the vpn must be started manually.

I am running a wireless network.and the wireless profile is auto connecting.

I would expect the vpn to connect shortly after the wireless connection connects.

[Felix (apoapo)]

This is still a problem in Lucid amd64. VPN connections are not established automatically.

[Igor Wojnicki (wojnicki)]

Same here, it's quite annoying to be forced to enable vpn every time I log in.

[Unnilennium (tests-pialasse)]

Same here really anoying as i have some VOIP application that need the VPn to connect to the VOIP server, if i forgot to open this connexion i am not able to recieve call.

On the other hand i do not want other user to be able to connect to this network so i can't add the connexion directly to the deamon. Would it be possible to make this option to work ?

[Fionn (fbe)]

This bug is valid for all releases at least up to maverick!

Moreover, when working in an insecure enviroment it may be pretty dangerous to use NM with openvpn since NM immediately flags any unencrypted connection as valid without starting openVPN as desired.

This may result in applications like evolution and firefox beginning to run unencrypted data transfers immediately which not only is a security risk but also slows down or even completely inhibits the user from being able to establish the VPN manually (see also: bug #420411 ).