You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Go to file
Igor Gnatenko 5fd6cc84e4
Fix systemd executions/requirements
7 years ago
.gitignore Update to upstream openvpn-2.4.4 7 years ago
.rpmlint More clean-ups 8 years ago
0001-Change-the-default-cipher-to-AES-256-GCM-for-server-.patch Change default cipher for server configurations to AES-GCM 8 years ago
README.systemd Cleaning up 8 years ago
gpgkey-F554A3687412CFFEBDEFE0A312F5F7B42F2B01E7.gpg Add missing gpg key used to verify the source signature 8 years ago
openvpn-2.1.1-init.patch - Fix init script *.sh sourcing, BZ 498348. 15 years ago
openvpn-2.1.1-initinfo.patch - Fix init script *.sh sourcing, BZ 498348. 15 years ago
openvpn-init.patch New upstream. 14 years ago
openvpn-script-security.patch Added script_security initialisation in initscript (#458594 #c20) 15 years ago
openvpn.spec Fix systemd executions/requirements 7 years ago
roadwarrior-client.conf auto-import openvpn-2.0-1 on branch devel from openvpn-2.0-1.src.rpm 20 years ago
roadwarrior-server.conf Update to 2.0.2. 20 years ago
sources Update to upstream openvpn-2.4.4 7 years ago

README.systemd

OpenVPN and systemd
===================

As of OpenVPN v2.4, upstream is shipping systemd unit files to provide a
fine grained control of each OpenVPN configuration as well as trying to
restrict the capabilities the OpenVPN process have on a system.


Configuration profile types
---------------------------
These new unit files separates between client and server profiles.  The
configuration files are kept in separate directories, to provide clarity
of the profile they run under.

Typically the client profile cannot bind to any ports below port 1024
and the client configuration is always started with --nobind.

The server profile is allowed to bind to any ports.  In addition it enables
a client status file, usually found in the /run/openvpn-server directory.
The status format is set to version 2 by default.  These settings may be
overridden by adding --status and/or --status-version in the OpenVPN
configuration file.

Neither of these profiles makes use of PID files, but OpenVPN reports back to
systemd its PID once it has initialized.

For configuration using a peer-to-peer mode (not using --mode server on one
of the sides) it is recommended to use the client profile.


Configuration files
-------------------
These new unit files expects client configuration files to be made available
in /etc/openvpn/client.  Similar for the server configurations, it is expected
to be found in /etc/openvpn/server.  The configuration files must have a .conf
file extension.


Managing VPN tunnels
--------------------
Use the normal systemctl tool to start, stop VPN tunnels, as well as enable
and disable tunnels at boot time.  The syntax is:

 - client configurations:
    # systemctl $OPER openvpn-client@$CONFIGNAME

 - server configurations:
    # systemctl $OPER openvpn-server@$CONFIGNAME

Similarly, to view the OpenVPN journal log use a similar syntax:

   # journalctl -u openvpn-client@$CONFIGNAME
 or
   # journalctl -u openvpn-server@$CONFIGNAME

* Examples
  Say your server configuration is /etc/openvpn/server/tun0.conf, you
  start this VPN service like this:

    # systemctl start openvpn-server@tun0

  A client configuration file in /etc/openvpn/client/corpvpn.conf is
  started like this:

    # systemctl start openvpn-client@corpvpn

  To view the server configuration's journal only listing entries from
  yesterday and until today:

    # journalctl --since yesterday -u openvpn-server@tun0