Greetings,
Is there a simple way of disabling the automatic process restart which happens after the maximum number of connection retries is reached? in the Windows client?
This is my client config:
dev tun
tls-client
tls-auth ta.key 1
remote-cert-tls server
cipher AES-256-CBC
auth SHA512
remote xxx.xxx.xxx.xxx 443
resolv-retry 3
connect-retry-max 3
pull
proto tcp-client
dh dh4096.pem
ca ca.crt
cert test.crt
key test.key
comp-lzo
reneg-sec 0
auth-user-pass test.conf
auth-nocache
And the log file of the Windows client:
Wed Mar 04 14:32:41 2015 OpenVPN 2.3.6 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [PKCS11] [IPv6] built on Dec 1 2014
Wed Mar 04 14:32:41 2015 library versions: OpenSSL 1.0.1j 15 Oct 2014, LZO 2.08
Wed Mar 04 14:32:42 2015 Control Channel Authentication: using 'ta.key' as a OpenVPN static key file
Wed Mar 04 14:32:42 2015 Attempting to establish TCP connection with [AF_INET]xxx.xxx.xxx.xxx:443 [nonblock]
Wed Mar 04 14:32:52 2015 TCP: connect to [AF_INET]xxx.xxx.xxx.xxx:443 failed, will try again in 5 seconds: The system tried to join a drive to a directory on a joined drive.
Wed Mar 04 14:33:07 2015 TCP: connect to [AF_INET]xxx.xxx.xxx.xxx:443 failed, will try again in 5 seconds: The system tried to join a drive to a directory on a joined drive.
Wed Mar 04 14:33:22 2015 TCP: connect to [AF_INET]xxx.xxx.xxx.xxx:443 failed, will try again in 5 seconds: The system tried to join a drive to a directory on a joined drive.
Wed Mar 04 14:33:22 2015 SIGUSR1[soft,init_instance] received, process restarting
If it's possible I would really like to avoid getting into infinite connection retry loops and simply put the client in a disconnected state after a certain timeout is reached.
Any help would be appreciated,
rKr.
