Hi,
Are you saying that the interactive service also doubles as a Windows system
service? If so, can it be configured to autostart selected openvpn
connections on boot and restart them if they crash/stop?
No, and I do not think that the service should take care of that. That's
rather things that can be handled by the GUI.
What about persistent connections, especially on Windows servers?
I've already done a proof of concept "openvpnserv.exe" replacement using
NSSM:
<https://community.openvpn.net/openvpn/wiki/IntegratingOpenvpnWithNssm>
I also started writing a small C# program that can manage OpenVPN
connections in NSSM in a user-friendly fashion, because the standard
NSSM GUI is way too complex and generic for our well-specified use-case.
Now, can anyone provide proof that having a Windows team would actually
_hurt_ the project? If not, what does it matter if it fails? We could just
scrap the idea retroactively.
Hehe nice turn demanding proof, that'll shut up ppl. =)
Yes, that was the idea, because I know you guys don't have any proof. It
seemed to have worked fine :).
That said, I don't have any proof either, but I think we all can agree
that the situation with Windows in OpenVPN is not optimal, and that we
should try to do something about it.
Best regards,
--
Samuli Seppänen
Community Manager
OpenVPN Technologies, Inc
irc freenode net: mattock
