Opened 13 years ago
Closed 8 years ago
#129 closed Feature Wish (fixed)
openvpnserv.exe should restart missing openvpn.exe processes
| Reported by: | bwess | Owned by: | Samuli Seppänen |
|---|---|---|---|
| Priority: | minor | Milestone: | release 2.4 |
| Component: | Generic / unclassified | Version: | OpenVPN git master branch (Community Ed) |
| Severity: | Not set (select this one, unless your'e a OpenVPN developer) | Keywords: | windows openvpnserv |
| Cc: | Heiko Hund |
Description
GUIs for the OpenVPN client increasingly use the management interface. On Windows, in setups where users are unprivileged and OpenVPN processes are started by the service wrapper GUIs have to rely on the OpenVPN processes not exiting to control and continue reusing them for many connections, but this can happen in certain cases.
The OpenVPN service wrapper should either e.g. check for the presence of management/management-hold in configuration files or have e.g. a registry entry to have it restart the missing OpenVPN processes or even let this be the default behavior (is there a case where the current behavior makes sense?).
Change History (7)
comment:1 Changed 13 years ago by
comment:2 Changed 11 years ago by
| Keywords: | windows openvpnserv added |
|---|---|
| Version: | 2.2.0 → git master branch |
No changes have been made to openvpnserv.exe code in ages, so this issue persists.
comment:3 Changed 10 years ago by
| Type: | Bug / Defect → Feature Wish |
|---|
Unless someone provides an actual patch for openvpnserv to do that, I think this will not be changed.
2.4 will have the new interactive service, which is MUCH better suited for working together with the Gui process (and also more secure because openvpn.exe will not need to run with admin or system privileges).
comment:4 Changed 10 years ago by
| Cc: | Heiko Hund added |
|---|---|
| Milestone: | → release 2.4 |
milestone set, so we can come back here at 2.4 release and verify that the interactive service is in, the documentation is clear enough, and then close it.
comment:5 Changed 9 years ago by
| Owner: | set to Samuli Seppänen |
|---|---|
| Status: | new → assigned |
NSSM, for non-interactive use with restarting, and iservice otherwise?
comment:6 Changed 9 years ago by
NSSM looks like a reasonable replacement for openvpnserv.exe, based on my non-extensive tests. What is needed is a way to configure NSSM easily or automatically as new VPN connections are added.
comment:7 Changed 8 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
This is handled by openvpnserv2, already merged into latest openvpn-build-generated snapshot installers. Closing.
This could make the behavior discussed in https://community.openvpn.net/openvpn/ticket/110 unnecessary or could fall back to it if there is only one configuration file (relying on Windows to do service auto-restart-after-crash does seem like an ugly hack to achieve what the service wrapper should do itself).