Thu Jul 30 17:02:53 2015 TUN/TAP device tun0 opened Thu Jul 30 17:02:53 2015 Incoming Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Thu Jul 30 17:02:53 2015 Outgoing Control Channel Authentication: Using 160 bit message hash 'SHA1' for HMAC authentication Thu Jul 30 17:02:53 2015 Control Channel Authentication: using '/etc/openvpn/ta.key' as a OpenVPN static key file Thu Jul 30 17:02:53 2015 Diffie-Hellman initialized with 2048 bit key Be aware that this might create routing conflicts if you connect to the VPN server from public locations such as internet cafes that use the same subnet. The output of openvpn /etc/openvpn/nf on the server: Thu Jul 30 17:02:53 2015 OpenVPN 2.3.6 x86_64-unknown-linux-gnu built on Dec 2 2014 I started the server first, then the client. Here are the outputs of running openvpn on the machines with the above configurations. etc/openvpn/nf (Non-comment lines only): client
etc/openvpn/nf (Non-comment lines only): port 1194 I created these according to the instructions on the Arch Wiki. Here are the configuration files on the server and client, respectively. Gateway: Port forwarding for port 1194 enabled, no firewall restrictions.
OPENVPN TUNNELBLICK NOT ROUTING NON VPN TRAFFIC WINDOWS 8.1
No iptables.Ĭlient: Arch Linux (up to date) virtual machine on VirtualBox 4.3.28r100309 Windows 8.1 host, bridged network adapter. Server: Arch Linux (up to date) connected directly to gateway via ethernet cable. See also my original question about securing SMB traffic over the Internet: ( Simple encryption for Samba shares)Ĭan anybody explain how I can solve this issue? The only deviations I have made from these instructions have been specifying my own computers' names and their corresponding key/certificate file names. I have been following the instructions at ( ) to set up OpenVPN and the instructions at ( ) to create the keys and certificates. In both instances, the required changes were made to both the client and server configurations. I also tried disabling the cipher and TLS authentication, but that caused the server to fail with Assertion failed at crypto_openssl.c:523. I quickly read ( OpenVPN on OpenVZ TLS Error: TLS handshake failed (google suggested solutions not helping)) and tried to switch from the default UDP to TCP, but that only caused the client to repeatedly report that the connection timed out. When I test the setup on one of my Linux virtual machine clients, I get the error: TLS Error: TLS handshake failed. I am configuring OpenVPN 2.3.6-1 on my Arch Linux server in order to encrypt SMB traffic over the public Internet.
0 kommentar(er)
