On 2/3/2019 8:36 AM, David Sommerseth wrote:
On 01/02/2019 01:35, Daniel Miller via Openvpn-users wrote:
I may open a bug with Ubuntu (my server is on Bionic) but a recent re-boot
after some config changes may have exposed something. This isn't an OpenVPN
bug - rather known OpenVPN behavior that may catch others so I'm sharing.
Having installed packages quagga-ospfd & quagga-core I setup some basic OSPF
rules to communicate with my router. After re-booting yesterday I found that
my VPN wouldn't start up. Further investigation found the TUN devices wasn't
being created - and the error was the dreaded "RTNETLINK answers: File
exists". Stopping the ospfd & zebra services then allowed openvpn to
initialize without issue.
Accordingly, I modified my systemd units:
openvpn.service - change to "After=network-online.target"
zebra.service - remove the "Before=network.target" and change to
"After=openvpn-server@<my-vpn>.service"
Just some potential confusion .... you say you modify *openvpn.service* (which
you should forget all about, but that's a different story) but you actually do
use *openvpn-server@.service* (which is what you should use). This latter one
should have (if your package contains the latest upstream changes) these two
lines:
After=syslog.target network-online.target
Wants=network-online.target
Quite right - I made the change to openvpn-server@.service as well. And
if we need a different thread for the different story...
The "openvpn.service" seems to basically be null. Was this intended for
some future purpose?
--
Daniel
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
