Reverse ssh tunnel Part 2: Going through Windows


We did a post about reverse ssh tunneling post, which is in spanish (we might redo it in english… or not), so this is part 2.

The main idea of the Part 1 was to make a reverse ssh tunnel to access remotely a server in a private network and the network staff won’t allow us to access it directly.

The issue

Let’s say we have a remote server we want to access (http or ssh) but this server is in a local network and doesn’t have internet access, we will call it Server_1 and its local IP is Then we have our local PC, called Local_PC, which has internet connection and our public IP is If we want to access directly to Server_1 we won’t be allowed since it doesn’t have internet connection.

Tunneling through anything

Then when we need to access the server, the client in the remote network provides us with a Teamviewer connection though a Laptop running windows, what can we do to access directly from our Local_PC running our beloved Linux?

Principle of least effort
The solution


Yes, we can use Putty to make a reverse ssh tunnel from Server_1 to Local_PC, but how do we do so?

You open up Putty in the laptop and go to Connection -> SSH -> Tunnels then you have to input the Source Port which will be Local_Pc:<remote_port> (be sure not to use an already occupied port). Then in Destination we input for ssh or for http or whatever port you need. Change the checkbox from Local to Remote, since we are doing a reverse tunnel, and simply click Add. Finally go back to the Session section and connect to Local_PC via ssh and voilá!

Putty <3 (Note the “Remote” checkbox)

You will be able to access Server_1 from Local_PC simply doing:

ssh user@localhost -p <remote_port>

It is possible to Add more tunnels with a single connection, so you can tunnel an ssh connection and a http one.

13 Reasons Why… Vim

Hello, do you have a moment to talk about Vim?
Today we bring to you THE ultimate text editor: Vim

Before Vim our life was sad, really sad, then we found it, and our life was sad and complicated :(, but then, we learnt how to use it, and now, we are ridiculously happy!!( except for the designer, he uses Windows and can’t use Vim like us, so he is still sad)
So, why would you want to use it?? Let’ s see:

1 – If you don’t have money to buy a mouse, don’t worry, you don’t need one!.
2 – It´s doesn’t consume 130% of RAM like other editors.
3 – It´s stable, Vim just … never gonna give you up, never gonna let you down .. really, no crashing.
4 – You will find Vi ( Vim´s father) included in just about any unix derived system.
5 – Ideal when you are ssh-ing into a linux-running server or something, where don’t even need an X.
6 – Works fine even using a poor ssh or network connection.
7 – It’s customizable and extensible, you can personalize it as you see fit.
8 – It´s free!
9 – Wherever you go, you can take with you your vim configuration easily.
10 – Very nice documentation, just need to use “:help”.
11 – Vim is really powerfull and incredibly fast once you get past the initial learning curve (which is really steep, don’t give up halfway!).
12 – It has regex!
13 – Vim is awesome! (yes, that’s a reason).



Join the Vim side of the Force …