Hi, Lots of discussion on this - awesome to see! Perhaps a dumb question, but I can see a few different ways to go on this, as I see comments about services, applications, etc. ... so a couple thoughts, - is the intention to run a service (like NSSM?) that keeps openvpn.exe "alive" (restarting it as necessary), so it's always up and running? I admit, I somewhat like this approach, one running application for each config file. Then control it through the management interface. Or, - do folks prefer to have "control application" bring openvpn.exe up and down? I have tried this, and it's a bit messy, but it is functional also.
Thoughts? I do believe there may also be TAP related stability issues, but that may be an artifact of openvpn.exe crashing - I guess the first step is to get openvpn.exe stable? Thanks, ... Russell -----Original Message----- From: Christian Rank [mailto:christian.r...@uni-passau.de] Sent: Wednesday, October 21, 2015 1:47 AM To: openvpn-devel@lists.sourceforge.net Subject: Re: [Openvpn-devel] Creating a Windows team for OpenVPN? On 21.10.2015 00:39, openvpn-devel-requ...@lists.sourceforge.net wrote: > From: ValdikSS <i...@valdikss.org.ru> > > By the way, there is an open-source SecurePoint VPN client > (https://sourceforge.net/projects/securepoint/) which handles current > versions of Windows very well. Hi, it seems that the current version of Securepoint's VPN client is no longer open source. The repo at > https://github.com/Securepoint/openvpn-client has the source for version 1.0.3 (last commit 2 years ago), whereas the current version (binaries) on sf.net is 2.0.10. Securepoint's website http://www.securepoint.cc/products-vpn-clients.html says "The Securepoint OpenVPN client is free of charge" - the term "open source" is not mentioned. Regards, Christian -- Dr. Christian Rank Rechenzentrum Universität Passau Bereich Netzwerk und Telekommunikation IT-Sicherheitsbeauftragter der Universität Innstr. 33 D-94032 Passau GERMANY
