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"
ospfd.service - remove the "Before=network.target" and change to
"After=zebra.service openvpn-server@<my-vpn>.service"
Note - I previously enabled the network-online.target (it solves so many
problems I don't know why it isn't the default!).
--
Daniel
_______________________________________________
Openvpn-users mailing list
Openvpn-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-users
