To download these tutorials for OFFLINE viewing or for archive purposes please (Click here to download)
(Clicking the “.zip” will open the Archive, un-zip the .mht files then use one of the plugins below to view them)
You can open .mht WebArchive files directly inside FireFox Or Google Chrome by installing a plugin
Recently I wanted to set up a remote desktop sharing session from home pc to my laptop.
While going through the set up guide I came across ssh tunneling. Even though there are many articles on the subject
still it took me a considerable amount of googling, experimenting and couple of Wireshark sessions to see what’s going on
Most of the guides were incomplete in terms of explaining the concept which left me desiring for a good article on the subject with some explanatory illustrations. So I decided to write it my self. So here goes…
A SSH tunnel consists of an encrypted tunnel created through a SSH protocol connection.
A SSH tunnel can be used to transfer unencrypted traffic over a network through an encrypted channel. For example we can use a ssh tunnel to securely transfer files between a FTP server and a client even though the FTP protocol itself is not encrypted. SSH tunnels also provide a means to bypass firewalls that prohibits or filter certain internet services.
For example an organization will block certain sites using their proxy filter.
But users may not wish to have their web traffic monitored or blocked by the organization proxy filter.
If users can connect to an external SSH server, they can create a SSH tunnel to forward a given port
on their local machine to port 80 on remote web-server via the external SSH server.
I will describe this scenario in detail in a little while.
To set up a SSH tunnel a given port of one machine needs to be forwarded (of which I am going to talk about in a little while) to a port in the other machine which will be the other end of the tunnel. Once the SSH tunnel has been established, the user can connect to earlier specified port at first machine to access the network service.
SSH tunnels can be created in several ways using different kinds of port forwarding mechanisms.
Ports can be forwarded in three ways as i will try to explain in this tutorial.
- Local port forwarding
- Remote port forwarding
- Dynamic port forwarding
Port What??? to explain this a quick trip to Wikipedia was all it took to explain it.
Port forwarding or port mapping is a name given to the combined technique of
- translating the address and/or port number of a packet to a new destination
- possibly accepting such packet(s) in a packet filter(firewall)
- forwarding the packet according to the routing table.
Tunnelling with Local port forwarding
Here the first technique will be used in creating an SSH tunnel. When a client application connects to the local port
(local endpoint) of the SSH tunnel and transfer data these data will be forwarded to the remote end by translating
the host and port values to that of the remote end of the channel.
So with that let’s see how SSH tunnels can be created using forwarded ports with working examples.
Let’s say that http://www.thepiratebay.sx is being blocked using a proxy filter in the University of Cali.
A SSH tunnel can be used to bypass this restriction. Let’s name my machine at the university as ‘work’ and my home machine as ‘home’. ‘home’ needs to have a public IP for this to work. And I am running a SSH server on my home machine.
The Following diagram illustrates the scenario.
To create the SSH tunnel execute following from ‘work’ machine.
ssh -L 9999:thepiratebay.sx:80 home
The ‘L’ switch indicates that a local port forward is need to be created. The switch syntax is as follows.
Now the SSH client at ‘work’ will connect to SSH server running at ‘home’ (usually running at port 22) binding port 9999 of ‘work’ to listen for local requests thus creating a SSH tunnel between ‘home’ and ’work’. At the ‘home’ end it will create a connection to ‘thepiratebay.sx’ at port 80. So ‘work’ doesn’t need to know how to connect to thepiratebay.sx Only ‘home’ needs to worry about that. The channel between ‘work’ and ‘home’ will be encrypted while the connection between ‘home’ and ‘thepiratebay.sx’ will be unencrypted.
Now it is possible to browse thepiratebay.sx by visiting http://localhost:9999 in the web browser at ‘work’ computer. The ‘home’ computer will act as a gateway which would accept requests from ‘work’ machine and fetch data and tunnelling it back. So the syntax of the full command would be as follows.
ssh -L <local-port-to-listen>:<remote-host>:<remote-port> <gateway>
The image below describes the scenario.
Here the ‘host’ to ‘thepiratebay.sx’ connection is only made when browser makes the request not at the tunnel setup time.
It is also possible to specify a port in the ‘home’ computer itself instead of connecting to an external host.
This is useful if I were to set up a VNC session between ‘work’ and ‘home’. Then the command line would be as follows.
ssh -L 5900:localhost:5900 home (Executed from ‘Work’)
So here what does localhost refer to? Is it the ‘work’ since the command line is executed from ‘work’? Turns out that it is not. As explained earlier is relative to the gateway (‘home’ in this case) , not the machine from where the tunnel is initiated. So this will make a connection to port 5900 of the ‘home’ computer where the VNC client would be listening in.
The created tunnel can be used to transfer all kinds of data not limited to web browsing sessions. We can also tunnel SSH sessions from this as well. Let’s assume there is another computer (‘banned’) to which we need to SSH from within University but the SSH access is being blocked. It is possible to tunnel a SSH session to this host using a local port forward.
The setup would look like this.
Now the transferred data between ‘work’ and ‘banned’ are encrypted end to end.
For this we need to create a local port forward as follows.
ssh -L 9999:banned:22 home
Now we need to create a SSH session to local port 9999 from where the session
will get tunneled to ‘banned’ via ‘home’ computer.
ssh -p 9999 localhost
With that let’s move on to next type of SSH tunnelling method, reverse tunnelling.
Reverse Tunnelling with remote port forwarding
Let’s say it is required to connect to an internal university website from home.
The university firewall is blocking all incoming traffic. How can we connect from ‘home’ to internal network so that we can browse the internal site? A VPN setup is a good candidate here. However for this example let’s assume we don’t have this facility.
Enter SSH reverse tunnelling..
As in the earlier case we will initiate the tunnel from ‘work’ computer behind the firewall. This is possible since only incoming traffic is blocking and outgoing traffic is allowed. However instead of the earlier case the client will now be at the ‘home’ computer.
Instead of -L option we now define -R which specifies a reverse tunnel need to be created.
ssh -R 9999:intra-site.com:80 home (Executed from ‘work’)
Once executed the SSH client at ‘work’ will connect to SSH server running at home creating a SSH channel.
Then the server will bind port 9999 on ‘home’ machine to listen for incoming requests which would subsequently
be routed through the created SSH channel between ‘home’ and ‘work’. Now it’s possible to browse the internal site
by visiting http://localhost:9999 in ‘home’ web browser. The ‘work’ will then create a connection to intra-site and relay
back the response to ‘home’ via the created SSH channel.
As nice all of these would be still you need to create another tunnel if you need to connect to another site in both cases.
Wouldn’t it be nice if it is possible to proxy traffic to any site using the SSH channel created?
That’s what dynamic port forwarding is all about.
Dynamic Port Forwarding
Dynamic port forwarding allows to configure one local port for tunnelling data to all remote destinations. However to utilize this the client application connecting to local port should send their traffic using the SOCKS protocol. At the client side of the tunnel a SOCKS proxy would be created and the application (eg. browser) uses the SOCKS protocol to specify where the traffic should be sent when it leaves the other end of the ssh tunnel.
ssh -D 9999 home (Executed from ‘work’)
Here SSH will create a SOCKS proxy listening in for connections at local port 9999 and upon receiving a request would route the traffic via SSH channel created between ‘work’ and ‘home’. For this it is required to configure the browser to point to the SOCKS proxy at port 9999 at localhost.