Openvpn: how to start at login?

[Timothy Murphy]

Marko Vojinovic wrote:

>> But surely there should be a way of enabling this service,
>> as there used to be?
>> Wouldn't it be much simpler just to default to client,
>> which I imagine is what 99% of users want?
>> Why can't openvpn run like every other service?
> 
> In what sense openvpn *doesn't* run like every other service?
> 
> I have openvpn set up and running here on my laptop. The client is
> basically always active and retries periodically to reconnect to the
> remote server until success (laptop might not always have a connection to
> the Internet). I never hibernate the machine, but suspending to RAM and
> back is completely transparent, openvpn stays active all the time.
> 
> I'm on F16 here, but there should be no difference to F17 AFAIK, since
> both use systemd.
> 
> All I did to set up openvpn with systemd was to follow instructions on the
> Fedora wiki:
> 
>   http://fedoraproject.org/wiki/Openvpn#Working_with_systemd
> 
> What exactly is the problem in your case?

This document is concerned with setting up an openvpn server
(which I have running on a CentOS machine without problem).
I was talking about running an openvpn _client_ on a Fedora machine.
The only advice in the document about this is
----------------------------------
to start a connection, run systemctl start openvpn at foo.service, where the 
connection is defined in /etc/openvpn/foo.conf
----------------------------------
which is exactly what my script above does (with client for foo).

Actually, openvpn sometimes stays active when I hibernate,
but more often it does not.






-- 
Timothy Murphy  
e-mail: gayleard /at/ eircom.net
tel: +353-86-2336090, +353-1-2842366
s-mail: School of Mathematics, Trinity College Dublin