On Wed, 22 Sep 2021 09:41:43 -0400, Selva Nair <selva.n...@gmail.com> wrote:
>You can also go to the settings menu of the GUI, set silent connection to >on. It will be remembered when you start the GUI next time from the command >line. But that is exactly what I do NOT want... I don't want this to be a system-wide setting, just for the specific connection used by my client software. My whole purpose of asking for On-Demand is that I am creating a client application for a server that is unreachable in normal cases. It sits behind a network which has a non-public Internet facing IP address, so I cannot use some port forward setting to reach it. Instead the remote server software runs on a Linux box which uses openvpn to connect a dead-end tunnel on our main OpenVPN server 24/7. Now the client software on Windows needs the client to also connect VPN to the same dead-end tunnel in order to then be able to communiucate with the remote server. So I want to have the ability in the client software to do an on-demand vpn connection to the tunnel when the user commands a connection to the server itself, and then I do not want the extraneous status dialog popping up. But when the Windows user is running his PC *not* using the remote server client I do not want to block his ability to see progress when he connects to some other unrelated OpenVPN server using the OpenVPN-GUI application. I am myself such a user... I have maybe 10 different OpenVPN servers I use regularly for other purposes. So what can I do? Maybe during the connection sequence: - send a silent_connection 1 command - then send the actual connection command - then send a silent_connection 0 command I assume the connection will still be maintained since it is not managed as such by openvpn-gui, right? -- Bo Berglund Developer in Sweden _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
