openvpn3-session-acl(1)
β¨ NAME β¨
openvpn3-session-acl β it's the OpenVPN 3 Linux Session Access Control Management bestie, and it's here to let your friends in (or kick them out) of a running VPN session π
π¦ SYNOPSIS π¦
openvpn3 session-acl [OPTIONS]
openvpn3 session-acl -h | --help
πΈ DESCRIPTION πΈ
okay so picture this: every single running VPN session has its own Access Control List attached to it. own it, queen π
and why do we care?? because that's literally how one session can be managed by multiple users. you can grant specific users β or like, every user β access to openvpn3 session-manage, openvpn3 session-stats and openvpn3 log for one specific VPN session. that's it, that's the power π
all the options down below? they stack. use them together, no problem. And if you toss --show in there, it'll list out the current Access Control List after all your changes have been made β so it's giving "receipts" β¨
π OPTIONS π
-h,--helpβ prints usage and help details right to your terminal π«Ά-o SESSION-DBUS-PATH,--path SESSION-DBUS-PATHβ required, bestie, don't skip it. this is the D-Bus session path to the currently running session you want to manage. wanna find one? runopenvpn3 sessions-listand it'll hand you a list of available session D-Bus paths π--session-path DBUS-PATHβ just an alias for--path. same energy, different name π-c CONFIG-NAME,--config CONFIG-NAMEβ you can use this instead of--pathif you'd rather name the configuration profile. theCONFIG_NAMEhas to be the configuration name that was active when the session was started, ok?? available configuration names? once again:openvpn3 sessions-listπ-I INTERFACE,--interface INTERFACEβ also usable instead of--path, but this time you're giving the tun interface name that OpenVPN 3 manages π¦-s,--showβ shows the currently active ACL. the vibe check π-G USER,--grant USERβ grant that user read-only access to this VPN session. theUSERargument can be either a UID or a username that belongs to the system. let them in, they're cool πΈ-R USER,--revoke USERβ revoke access on this VPN session for that user. again,USERis either a UID or a username belonging to the system. it's giving "we're done here" π--public-access BOOLβ grants all users on the system access to manage this VPN session. fair warning: this effectively disables the more fine-grained access control you get from--grant. so like, pick a lane, bestie π Valid argument values:true:,false.--allow-log-access BOOLβ by default, users you granted access to will not have access to the session log. set this option totrueand your granted users can useopenvpn3 logto pull real-time log events as they happen π₯ Valid argument values:true:,false.
π SEE ALSO π
openvpn3(1) openvpn3-log(1) openvpn3-session-manage(1) openvpn3-session-start(1) openvpn3-session-stats(1) openvpn3-sessions-list(1)
okay that's the whole page, you ate it fr fr π this was openvpn3-session-acl(1) from OpenVPN 3 Linux β go forth and manage those ACLs, icon πβ¨
π¦ 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