huntervast.blogg.se

Netshade freeze vpn connecting
Netshade freeze vpn connecting








Mon Feb 11 10:44:30 2019 VERIFY OK: depth=1, C=ES, ST=MAD, L=Madrid, O=Enimbos, OU=IT, CN=Enimbos CA, name=server, Feb 11 10:44:30 2019 VERIFY OK: nsCertType=SERVER Mon Feb 11 10:44:30 2019 WARNING: this configuration may cache passwords in memory - use the auth-nocache option to prevent this Mon Feb 11 10:44:30 2019 TCPv4_CLIENT link remote: SERVERPUBLICIP:443 Mon Feb 11 10:44:30 2019 TCP connection established with SERVERPUBLICIP:443 Mon Feb 11 10:44:29 2019 Attempting to establish TCP connection with SERVERPUBLICIP:443 Mon Feb 11 10:44:29 2019 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Mon Feb 11 10:44:29 2019 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Mon Feb 11 10:44:29 2019 Control Channel Authentication: tls-auth using INLINE static key file Mon Feb 11 10:44:11 2019 MANAGEMENT: CMD 'hold release'

netshade freeze vpn connecting

Mon Feb 11 10:44:11 2019 Need hold release from management interface, waiting. Plugin /usr/lib64/openvpn/plugins/openvpn-plugin-auth-pam.so openvpnĬode: Select all Mon Feb 11 10:44:11 2019 OpenVPN 2.3.8 i686-w64-mingw32 built on Jun 23 2017 #Provide DNS servers to the client, you can use goolge DNS #this line will redirect all traffic through our OpenVPN Server 192.168.# Maintain a record of client virtual IP address associations in this file. #Internal IP will get when already connect

netshade freeze vpn connecting

#See the size a dh key in /etc/openvpn/keys/ # "dev tun" will create a routed IP tunnel.










Netshade freeze vpn connecting