![tunnelblick viscosity tunnelblick viscosity](https://insmac.org/uploads/posts/2019-07/1563707285_tunnelblick_03.jpg)
Tunnelblick viscosity mac#
This is the log I see including one reattempt (with addresses changed): 12:39:35: Viscosity Mac 1.9.3 (1571) It goes from connecting to authenticating and over again.
![tunnelblick viscosity tunnelblick viscosity](https://miro.medium.com/max/1400/1*Nesc8-2yVuiMo0Hd0SsFNA.png)
![tunnelblick viscosity tunnelblick viscosity](https://airvpn.org/external_image/?url=http%3A%2F%2Fwww.anony.ws%2Fi%2F2014%2F06%2F08%2F8qeHf.png)
These are valid as by mistyping I get an authentication error :-)īut the connection is never established. When I try to connect I have to provide my user/pwd login - and the VPN password. If I edit it again it just shows "ca.crt", "cert.crt" and "key.key" - but I guess this is Viscosity's way of hiding what I have selected? I have also manually edited the imported connection configuration and selected the CA, Cert and Key certificates (originally created on the MikroTik box - see below). When I set up Viscosity it suggests to import connections from Tunnelblick (nice!) - so I did -) Today I'm using Tunnelblick against our MikroTik router - and it works fine (apart from the VM issues). I'm trying to connect to our company VPN (that I have set up) using Viscosity VPN to try and solve an issue where VMs running on VMware Fusion 12 on MacOS 11.5 don't work any more (Viscosity has been a solution for others according to this discussion). Not sure if this is the right place to ask this question? clientip:port MULTI: Learn: MAC_ADDR ->. clientip:port PUSH: Received control message: 'PUSH_REQUEST' Wed Apr 28 20:38:42 2010 clientip:port Peer Connection Initiated with clientip:port Wed Apr 28 20:38:42 2010 clientip:port Control Channel: TLSv1, cipher TLSv1/SSLv3 DHE-RSA-AES256-SHA, 1024 bit RSA
![tunnelblick viscosity tunnelblick viscosity](https://ghostpath.com/blog/wp-content/uploads/2021/02/tunnelblick.png)
Wed Apr 28 20:38:40 2010 clientip:port Data Channel Decrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Apr 28 20:38:40 2010 clientip:port Data Channel Decrypt: Cipher 'BF-CBC' initialized with 128 bit key Wed Apr 28 20:38:40 2010 clientip:port Data Channel Encrypt: Using 160 bit message hash 'SHA1' for HMAC authentication Wed Apr 28 20:38:40 2010 clientip:port Data Channel Encrypt: Cipher 'BF-CBC' initialized with 128 bit key Wed Apr 28 20:38:36 2010 clientip:port VERIFY OK: depth=1, /O=Root_CA/L=DefaultCity/ST=NW/C=RU Wed Apr 28 20:38:21 2010 clientip:port TLS: Initial packet from clientip:port, sid=5b67e8f1 fb9ed0f5 Wed Apr 28 20:38:19 2010 TCPv4_SERVER link remote: clientip:port Wed Apr 28 19:09:31 2010 Data Channel MTU parms Wed Apr 28 19:09:31 2010 Control Channel MTU parms Wed Apr 28 19:09:31 2010 LZO compression initialized Wed Apr 28 19:09:31 2010 MULTI: multi_create_instance called Wed Apr 28 19:09:30 2010 клиент SIGUSR1 received, client-instance restarting Wed Apr 28 19:09:30 2010 клиент TLS Error: incoming packet authentication failed from клиент Wed Apr 28 19:09:30 2010 клиент Authenticate/Decrypt packet error: packet HMAC authentication failed