TU VPN

Perma-Link

Configure SSH2 Tunnel

To configure an SSH2 VPN we first have to download MyENTunnel, which we will use to establish an SSH2 Tunnel from our desktop to the desired TUVPN server:

• Download MyEnTunnel from here.
• Extract this zip file and save to a directory of your choice. No install is necessary. You execute the application directly from the directory where you unzip.
• Double click on MyEnTunnel icon to open the application. You will see a window as shown here:

Configure SSH2 Tunnel

Configure SSH2 Tunnel

Now we set the following parameters in the Settings tab:

• Server: vpn.tuvpn.com (for connection to a random VPN server)  or specify any of the available servers on TUVPN network
• Port: change it to 61
• Username: This should be your TuVPN VPN username
• Passphrase: This should be your TuVPN VPN password
• Check Enable Compression
• Be sure to check Enable Dynamics SOCKS. This will activate the port field with a default value of 7070. This will be required later on when we configure the application that we want to protect.

Configure SSH Tunnel

Activate SSH2 Tunnel

Once the above settings are properly set, you are ready to connect.

Just click on Connect to establish an SSH2 session with the selected TUVPN server.

NOTE: As soon as you click on Connect, MyEnTunnel will automatically save the configured settings in the same directory where you previously extracted the MyEnTunnel files. MyEnTunnel will use these settings for future connection (they can be changed if needed).

Activate SSH2 Tunnel

Connected

To confirm that you are connected successfully, go to the Status tab.

Here, on successful connection, you will read: Connection Stable.

Up to now we have established an SSH2 Tunnel from our computer to the desired TUVPN VPN Server but no data will be transmitted over it until we properly configure the applications that that will use the SSH2 Tunnel (the application(s) whose data we want protected).

Don't worry, it is very easy!

Connected

Configure Applications To Use the SSH2 Tunnel

Up to now, we have just setup an SSH2 Tunnel. What we have achieved is to have a local port in our computer (by default 7070) listening for connections. ANY connection to this local port, will be sent over the encrypted SSH2 tunnel to the remote TUVPN server.

So, what do we have to do? Simply configure any application that we want to use the tunnel to connect to this local port. That's it! 

In this example we will be configuring  Firefox to send all its data over the SSH2 Tunnel.

Remember that you can use this same concept on ANY OTHER APPLICATION that supports SOCKS v5 proxies. Firefox is just an example here.

To configure Firefox to use our newly created SSH2 Tunnel, go to Firefox --> Menu --> Options --> Options

Configure Applications To Use the SSH2 Tunnel

Configure Applications To Use the SSH2 Tunnel

Now click on Advanced tab, then Network tab and click on Settings.

Configure Applications To Use the SSH2 Tunnel

Configure Applications To Use the SSH2 Tunnel

Now set the network settings as defined here:

• Select Manual Proxy configuration.
• Be sure to uncheck Use this Proxy Server for all protocols.
• Enter SOCKS Host as: 127.0.0.1. Input 7070 as Port value. Here we are basically telling Firefox to use the SSH2 Tunnel we created previously with MyEnTunnel.
  
• Check SOCKS v5 radio button under SOCKS Host.
• Click OK to save these settings.

Configure Applications To Use the SSH2 Tunnel

Confirmation of Successful Connection

Now Firefox is set to transmit all data over our SSH2 Tunnel. You can confirm it by opening an IP identification site (e.g. www.whatismyipaddress.com ) where you can see that your IP is now a TUVPN VPN server in an entirely new location....and possibly a new country!

Notice here one of the advantages of the SSH2 Tunnels. If for any reason the SSH2 Tunnel goes down, NO TRAFFIC from Firefox will ever reach the Internet through your normal Internet connection. As you have instructed Firefox to use a local port linked to the SSH2 Tunnel, if the tunnel is down, Firefox simply can't work. This will apply of course to ANY other application that you can configure the same way (that has Socks v5 support).

Confirmation of Successful Connection