2

I want to run my openvpn as systemd service. This tutorial tells me to use openvpn@.service template for that:

https://fedoraproject.org/wiki/Openvpn#Setting_up_a_Linux_OpenVPN_client

 ln -s /lib/systemd/system/openvpn@.service /etc/systemd/system/openvpn@MyClient.service

I can do that but before trying I wonder that in the same folder there is also an openvpn-client@.service file, which is not even mentioned in the tutorial. I looked into both but my knowledge of systemd is limited. From what I can see, both would work running an openvpn client, just openvpn-cliemt@.service would start it with --daemon ovpn-%i. Wouldn't it be better to have it running as a daemon? Is the tutorial just outdated and not covering this .service file?

user6329530
  • 340

1 Answers1

4

From 2.4.0, configuration moved to subdirectories: /etc/openvpn/{client,server} and the corresponding systemd units were changed from the generic openvpn@.service to openvpn-client@.service and openvpn-server@.service.

As the changelog describes it:

OpenVPN now ships with more up-to-date systemd unit files which take advantage of the improved service management as well as some hardening steps. The configuration files are picked up from the /etc/openvpn/server/ and /etc/openvpn/client/ directories (depending on unit file). This also avoids these new unit files and how they work to collide with older pre-existing unit files.

So it appears the Fedora wiki is out-of-date.

jasonwryan
  • 73,126