Reconnect after ISP disconnect at main office
Posted: Wed Mar 25, 2020 7:25 am
Generally Viscosity works great, connects to our main office without issue. But occasionally after a network connectivity drop on either side it seems to go down, and just repeats this handshake error a few times, then sits in the "authenticating" state until I happen to remote in and see that it's hung. Is their a change I can make to allow Viscosity to regain connection after a network outage?
Code: Select all
Mar 19 12:18:22 PM: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Mar 19 12:18:22 PM: TLS Error: TLS handshake failed
Mar 19 12:19:36 PM: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Mar 19 12:19:36 PM: TLS Error: TLS handshake failed
Mar 19 12:20:52 PM: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Mar 19 12:20:52 PM: TLS Error: TLS handshake failed
Mar 19 12:22:07 PM: TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity)
Mar 19 12:22:07 PM: TLS Error: TLS handshake failed
Mar 19 12:22:29 PM: State changed to Authenticating
Code: Select all
I also had persist-tun until now, but saw in some research to disable that. But haven't been able to confirm if that does the trick.#-- Config Auto Generated By Viscosity --#
#viscosity name client2
#viscosity autoreconnect true
#viscosity dns automatic
#viscosity usepeerdns true
#viscosity manageadapter true
#viscosity startonopen true
remote edgerouter.mainlocationwebsite.domain 1194 udp
pull
tls-client
dev tun
redirect-gateway def1
nobind
persist-key
ca cacert.pem
cert client2.pem
key client2-nopass.key
compress lzo
cipher AES-256-CBC
auth SHA256
resolv-retry infinite
comp-lzo yes
dev-node {B954547C-62DE-47B7-9145-5415598A5D1C}
route-delay 5
mute 20