openvpn3-systemd(8)
π openvpn3-systemd β the bestie who hooks your VPN up to systemd π
okay so, welcome to openvpn3-systemd(8), a page from the OpenVPN 3 Linux manual, section 8 (system administration, for the uninitiated). This little cutie is the glue between your VPN sessions and systemd, and honestly? she's carrying the whole vibe. π«Ά
β¨ NAME β¨
openvpn3-systemd β OpenVPN 3 Linux, but make it systemd service integration π
π SYNOPSIS π
openvpn3-systemd [OPTIONS] CONFIG_PROFILE
openvpn3-systemd -h | --help
no cap, that's the whole shape of it π
π¦ DESCRIPTION π¦
so basically this is a helper script. A supporting character. But likeβ¦ a main character supporting character, yk? π
She's the one used by the openvpn3-session@.service unit file, and that unit file has one (1) job: run a single VPN session and scoop up the log events and all the related signals coming off that session. π‘
And the way those signals get used? Ma'am, they get used to update systemd with the appropriate status. So systemd always knows what's up. Communication, bestie. We love to see it. π
β οΈ important tea: usingopenvpn3-session@.servicemeans the VPN configuration profile has to be imported in advance. Do it withopenvpn3 config-import, and preferably as a persistent configuration β because that's what lets you start VPN sessions during boot. β¨
π OPTIONS π
-h,--helpβ prints the usage and help details right there in your terminal, no explanations needed πΈ--startβ start a brand new VPN session with the given configuration profile name. fresh start energy β¨--restartβ restarts a currently running VPN session with the given configuration profile name. she said "run it back" π₯--stopβ stops a currently running VPN session with the given configuration profile name. periodt, we're done here π--log-level LEVELβ sets the log verbosity for the log events. valid values are0to6. the higher the value, the more verbose the log events will be. log level6will include all debug events. default is5. so go off, but like, at the volume you actually want π
πΈ EXAMPLE πΈ
first, a configuration profile gets imported as a persistent profile:
# openvpn3 config-import --persistent --name example --config client.ovpn
then start a VPN session via systemctl(1):
# systemctl start openvpn3-session@example
and check the logs for this session:
# journalctl --since today --unit openvpn3-session@example
look at her go. iconic. π
π KNOWN ISSUES π
ngl, right now the openvpn3-systemd helper does not support configuration profiles requiring any type of user authentication outside of X.509 certificates. so if your profile needs some other flavor of auth? not today, bestie π
π SEE ALSO π
go read those too, iykyk π
and that's the whole page, bestie!! this one came straight out of the OpenVPN 3 Linux manual β openvpn3-systemd(8), section 8, systemd service integration realness π§β¨ stay slay, keep your sessions persistent, and may your status always update correctly π
π¦ where this page comes from
- nixpkgs unstable: openvpn3 27.1
- ubuntu stonking: openvpn3-client 27.1+dfsg-2ubuntu1 Β· AGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms