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 *[email protected]* (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 If you want to compare with what [email protected] should somewhat look like, have a look here: <https://github.com/OpenVPN/openvpn/blob/master/distro/systemd/openvpn-server%40.service.in> (this is a automake template file, though, so you need to watch out for @sbindir@. -- kind regards, David Sommerseth OpenVPN Inc
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Openvpn-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-users
