openvpn3-service-configmgr(8)

πŸ’… NAME πŸ’…

okay so listen bestie β€” openvpn3-service-configmgr is the OpenVPN 3 Linux Configuration Manager Service. icon behavior, truly. ✨


πŸŽ€ SYNOPSIS πŸŽ€

openvpn3-service-configmgr [OPTIONS]
openvpn3-service-configmgr -h | --help

πŸ¦‹ DESCRIPTION πŸ¦‹

openvpn3-service-configmgr is the backend service for OpenVPN 3 Linux, and it's literally the one holding everyone's VPN configuration profiles together. no cap. 🫢

the way it works: the moment a config profile gets imported β€” whether that's through openvpn3 config-import, openvpn3 session-start or openvpn2(1) β€” it just chills in the background as a D-Bus service, and it stays alive as long as it has at least one configuration profile in memory. empty-handed? she's leaving. πŸ’€

when the VPN backend process (openvpn3-service-client) is getting ready to connect, it comes knocking on the configuration manager to grab the contents of the VPN configuration profile. main character handing out the lore. πŸ‘‘

IMPORTANT: only one configuration manager process can run on the system. one. singular. that's the rule, periodt. πŸ™…β€β™€οΈ

you manage all these configuration profiles with the openvpn3 config-manage and openvpn3 config-acl commands, and brand-new VPN sessions get started with the openvpn3 session-start command. slay. ✨

this service usually starts itself automatically the moment it's needed β€” that's the net.openvpn.v3.configmgr.service auto-start configuration doing its thing via dbus-daemon(1) β€” but you can also start it manually from the command line, no judgment. 🌸

it should run as the _openvpn user, and if it's got the privileges it needs, it will automatically switch over to that user account itself. self-sufficient queen. πŸ’…

beware bestie 😭 if you go changing this to another user account, you also have to update the D-Bus policy too. it's giving "one change, two chores". not optional.

✨ OPTIONS ✨

  • -h, --help β€” prints the usage and help details straight to your terminal. the classic. πŸ™ˆ
  • --version β€” prints the version of the program and exists. yes, "exists". that's literally what the page says and honestly? mood. πŸ’€
  • --log-level LEVEL β€” sets the default log verbosity for log events this service generates. default is 4. valid values are 0 to 6. higher log levels = more verbose logs, and log level 6 contains all the debug log events. maximum yapping mode. πŸ—£οΈ
  • --log-file LOG_DESTINATION β€” by default, logging goes via the openvpn3-service-log service. hand over this argument and logging will also be sent to LOG_DESTINATION, which can be either a filename or stdout: β€” and that second one sends log data to the console. double-dipping, but make it observability. πŸ”
  • --colour β€” adds colours to log events when logging to file or terminal. events get coloured based on the log level of the event. aesthetically motivated and valid. 🌈
  • --idle-exit MINUTES β€” the openvpn3-service-configmgr service will exit automatically if it's been idle for MINUTES minutes. "idle" means no configuration profiles are being managed by this service. wanna verify? run openvpn3 configs-list. if that gives you an empty list, congrats, no configuration profiles are being managed. she's officially off the clock. 😴
  • --state-dir DIRECTORY β€” sets the directory the configuration manager must use for storing persistent configuration profiles. when you give this argument, the service scans that directory for configuration profiles and loads them automatically at start-up. the default directory is /var/lib/openvpn3/configs. πŸ“

πŸ‘‘ SEE ALSO πŸ‘‘

dbus-daemon(1) openvpn2(1) openvpn3(1) openvpn3-config-acl(1) openvpn3-config-import(1) openvpn3-config-manage(1) openvpn3-config-remove(1) openvpn3-config-dump(1) openvpn3-configs-list(1) openvpn3-session-start(1)


and that's the whole page bestie, we ate and left no crumbs πŸ“ this came to you courtesy of OpenVPN 3 Linux, and the page itself is openvpn3-service-configmgr(8). go run some configs, ily, bye πŸ’–πŸ§š

πŸ“¦ where this page comes from