On 03.08.2012 18:06, Adam wrote: > Hi Michael, > > May I ask why it's not possible to connect to VPN on start-up? With the > increased usage of VPN's these days, it seems like a basic requirement > for many people. > > Over at launchpad, a couple of people have posted some fixes, it would > be great if you could take a look: > https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/280571 > > Someone also posted about a VPNautoconnect: > http://sourceforge.net/projects/vpnautoconnect/, so maybe this could be > integrated? > > If this cant be fixed, I think the autoconnect button should at least be > removed as it's very confusing to users, 61 people have reported it at > launchpad.
As I already wrote, autoconnect does not work and the relevant option should probably be greyed out. Instead of VPNautoconnect, I would suggest a small dispatcher script, which triggers the start of the VPN tunnel as soon as a connection has been established. The Ubuntu bug report afaics has such a dispatcher script [1]. That particular script needs manual modification before it is useful, i.e. you need to setup the VPN connection ID and then name of the connection that needs to be active before this VPN connection is activated. I'm a bit undecided if such a dispatcher script would make sense installed at /etc/NetworkManager/dispatcher.d if it is not useful out-of-the-box. I could ship it as examples file in /usr/share/doc and add a small section to README.Debian how to setup such an auto-activated VPN connection? Does that sound like a compromise until this is fixed proper upstream? Michael [1] https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/280571/comments/31 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature