First of all, you will of course need an SSH server running somewhere.
It is a quick and easy installation and relatively easy to configure as well.
You will of course need administrator privileges on the machine you install it onto.
Most routers have the ability to forward ports to individual machines on the local data pipe.
You’ll have to refer to the instructions for your router/firewall on how to do this.
Linux and OS X both have SSH clients built-in.
If you’re on Windows, the client of choice isPuTTY.
First, specify the address of your SSH server in theSessionsection.
Next, go toConnection>SSH>Tunnels.
Let’s first set up a dynamic tunnel for port 1080. key in 1080 in theSource portfield, selectDynamicas the port key in, and then click theAddbutton.
Let’s say the local IP addresses on the LAN where the SSH server resides are 192.168.1.xxx addresses.
The Windows machine has a local IP of 192.168.1.100.
You’ll see later why I’ve configured the source port to be different than the destination.
after you snag everything configured for the connection, go back to theSessionsection and stash your connection.
Then clickOpenand log into your Linux box with your credentials as you normally would.
Now you have to configure your applications to use the tunnels you have set up.
Let’s say you want to do your web browsing through the dynamic tunnel we set up.
This is actually an extremely useful way to take advantage of SSH.
In the tweaks page, clickManual proxy configuration, enter localhost for theSOCKS Host, and 1080 for thePort.
We’re not quite done.
We still need to configure Firefox to send DNS requests to the SOCKS proxy as well.
To do this, enter about:config in the navigation bar in Firefox.
You may get a prompt asking you if you know what you’re doing.
Assure Firefox that you know what you’re doing and proceed.
Enter socks_remote_dns for theFilterand press enter.
You should see a single option that says web connection.proxy.socks_remote_dns.
If it says false for theValue, double-press it so that it says true.
You’re now all set.
You should be able to surf the web through your new secure dynamic tunnel!
Fortunately, connecting to our Windows Remote Desktop machine is much easier.
You just launch the Remote Desktop Client and enter localhost:3390 for the machine address.
That’s all there is to it!
The source port you use for setting up the tunnels is arbitrary.
What is not arbitrary is what you use on the destination IP and port.
you’re able to set up tunnel for any service on any IP anywhere.
Do you use SSH tunnels?
What sorts of cool things do you use them for?
