On Wed, 22 Sep 2021 18:53:08 +0200, Gert Doering <g...@greenie.muc.de> wrote:
>> - send a silent_connection 1 command >> - Wait a while for the command to be executed >> - then send the actual connection command >> - Wait until we have a connection > >@selva: how complicated would it be to create a "hey, gui, please make >this call *blocking* until all pending VPN client connections are >established (or have given up)" command? > >openvpn-gui --command wait > >(I have no idea how complex this would be, I just go out and ask for >things) As described earlier in this thread openvpn-gui has an API of sorts but it works by sending windows messages across to another application (openvpn service?) and it returns when that message has been deposited with Windows. It has no way of knowing what the recipient does with the message... So I have worked around this by having checks on connect waiting until there is an adapter with the expected network IP, it usually takes about 6-8 seconds in my tests. Once that is present there is a VPN tunnel connection. -- Bo Berglund Developer in Sweden _______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
