![]() Future OpenVPN version will ignore -cipher for cipher negotiations. 10:51:07.973720 *Tunnelblick: openvpnstart starting OpenVPN 10:51:07.955288 *Tunnelblick: Attempting connection with CAR using shadow copy Set nameserver = 769 monitoring connection ⏎ EVENT: DISCONNECTED ⏎ Raw stats on disconnect: ⏎ EVENT: CONNECTION_TIMEOUT BYTES_IN : 23474 ⏎ EVENT: CONNECTING ⏎ Tunnel Options:V4,dev-type tun,link-mtu 1569,tun-mtu 1500,proto UDPv4,cipher AES-256-CBC,auth SHA256,keysize 256,key-method 2,tls-client ⏎ EVENT: WAIT ⏎ UnixCommandAgent: transmitting bypass route to /var/run/agent_ovpnconnect.sock ![]() ![]() ⏎ EVENT: RESOLVE ⏎ Contacting :1194 via UDP I am really puzzled why one client handles the VPN OK while another does not.Ĭan anyone give me any advice to help understand and fix the issue? I need this to work with OpenVPN connect as I have a couple of colleagues who use Windows, so Tunnelblick is not an option for them. Logs from TunnelBlick connection are also below. ovpn file in TunnelBlick on Mac, the TunnelBlick VPN connects immediately without any problems and remains rock solid stable for hours on end. When I try to connect with OpenVPN connect on MacOS, iPad or Windows the connection fails with a NEGOTIATION TIMEOUT error.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |