Bug 492149 - Make OpenVPN's `inactive` setting usable in the UI
Summary: Make OpenVPN's `inactive` setting usable in the UI
Status: REPORTED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_networkmanagement (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-08-24 23:34 UTC by Alex Cruise
Modified: 2024-12-23 18:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Cruise 2024-08-24 23:34:25 UTC
SUMMARY

OpenVPN has an `inactive` setting that can be used to automatically shut down the VPN based on idle time and/or a lack of traffic. It'd be great if this could be made available in the plasma-nm-openvpn UI. :)

STEPS TO REPRODUCE
1. Create OpenVPN connection, perhaps by importing a .ovpn profile from a file
2. Go to the Advanced dialog of the connection configuration page

OBSERVED RESULT
There's no widget for the `inactive` setting

EXPECTED RESULT
It'd be nice to have widgets for the `inactive` setting ;)



SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 40, plasma-nm-openvpn 6.1.4-1.fc40, openvpn 2.6.12-1.fc40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

Here's the relevant section from the OpenVPN docs... sadly there are no anchors on the page:

--inactive args
Causes OpenVPN to exit after n seconds of inactivity on the TUN/TAP device. The time length of inactivity is measured since the last incoming or outgoing tunnel packet. The default value is 0 seconds, which disables this feature.

Valid syntaxes:

inactive n
inactive n bytes
If the optional bytes parameter is included, exit if less than bytes of combined in/out traffic are produced on the tun/tap device in n seconds.

In any case, OpenVPN's internal ping packets (which are just keepalives) and TLS control packets are not considered "activity", nor are they counted as traffic, as they are used internally by OpenVPN and are not an indication of actual user activity.