Re: [Openvpn-users] OpenVPN on Xenial in AWS Issues

[Scott C. <sco...@gm...>]

Gert,

Thanks for the solution, I didn't see your email until I got it working.
The `systemd` script located at `/lib/systemd/system/openvpn@.service` is
missing a very important line in the *[Unit]* section:

[Unit]
Description=OpenVPN connection to %i
PartOf=openvpn.service
ReloadPropagatedFrom=openvpn.service
Before=systemd-user-sessions.service
After=network.target network-online.target # THIS IS NEEDED TO ENSURE
ROUTES COME UP AFTER MAIN NETWORKING
Documentation=man:openvpn(8)
Documentation=https://community.openvpn.net/openvpn/wiki/Openvpn23ManPage
Documentation=https://community.openvpn.net/openvpn/wiki/HOWTO

That "After" line is required. Not sure how patches are reported to Ubuntu,
but that should be fixed.

On Tue, May 10, 2016 at 1:36 PM, Gert Doering <ge...@gr...> wrote:

> Hi,
>
> On Tue, May 10, 2016 at 01:26:27PM -0700, Scott Crooks wrote:
> > Is there a way to delay starting up OpenVPN?
>
> I don't know enough about systemd to say whether you could just add
> a "sleep 120" in the openvpn start script...
>
> It might also work to try adding
>
>   up "sleep 120"
>
> to the openvpn config - if I read the docs right, the "up script" will
> be executed after tun open, but before routing setup.  If that doesn't
> work, try
>
>   route-delay 120
>
> (so the VPN will come up, but not install any routing until 2 minutes
> later - and I assume the VPN routes are getting in the way)
>
> gert
>
> --
> USENET is *not* the non-clickable part of WWW!
>                                                            //
> www.muc.de/~gert/
> Gert Doering - Munich, Germany
> ge...@gr...
> fax: +49-89-35655025
> ge...@ne...
>



-- 
Scott Crooks (王虎)
LinkedIn: http://www.linkedin.com/in/jshcrooks