As a long-term update, this method of attempting to open dozens of potentially unreliable OpenVPN config files from VPNGATE has been working for me for months, so I appreciate all the customization advice given in this thread, all of which works fine.
The ONLY problem remaining is that sometimes (once ever couple of days), the VPN connection summarily drops, and only one of two things happens:
a. The openvpn daemon will say the connection is faltering, in the last lines of the openVPN daemon log file, or,
b. The openvpn daemon just dies WITHOUT ANY WARNING WHATSOEVER and no window remains.
Either one of these is bad because:
a. In the case of the log file remaining active, you have to check it every minute to ensure that the openVPN connection is working, and,
b. In the case of the log file disappearing, you're no longer protected but you have to notice that openVPN just died without any notice.
I think every user has this problem of openVPN disappearing without notice, so, I asked in the general area how to NOTIFY THE USER with a very obvious method but other than that one issue, this method described in this thread has been working perfectly.
* What can we do to ensure that OpenVPN NOTIFIES the user with a CLEAR WARNING when the connection drops?
Thanks for all your help because this helps mostly users who are using free public VPN services, which require multiple openvpn files, some of which work and some of which don't work upon first connection.
Tutorial to set up Windows 10 OpenVPN client to work on HUNDREDS of sometimes unreliable freely available openvpn config
This forum is for general conversation and user-user networking.
- OpenVPN User
- Posts: 37
- Joined: Sun Jun 04, 2017 1:59 am