I would like to access the ssh port of my office linux host from home. Unfortunately the host is located behind a NAT router. So, the IP address is not publicly available. There is however access to another internet host (Server) which is unfortunately only non-root access. After a while of searching I do not find a suitable solution.

Following setup:

  • Office PC (linux, root access) behind NAT (IP not public) but full Internet access.
  • Server PC (linux, no root access) static and public IP and full Internet access.
  • Home PC (linux, root access) behind NAT (IP not public) but full Internet access.

Possible connections: Office PC --> Server <-- Home PC

Not possible: Office PC <-X- Server -X-> Home PC

Neither the Home PC, nor the Server can initiate access to the Office PC. But both the Office PC and the Home PC can initiate connections to the Server.

Reverse SSH tunnel not possible: I tried a method called reverse ssh-tunnel. Unfortunately this requires GatewayPorts on Server set to "yes" in /etc/ssh/sshd_config, where I have no root access.

In principle it should be possible:

0) On the Server I start a userspace program which listens on 2 ports (1 incoming, 1 outgoing)

1) On my office PC I run a another program which keeps a TCP connection open to the outgoing port on the server.

2) From home I connect to Server's incoming port.

There should be a standard solution for this out there.

What is the quickest and cleanest solution to solve this?


migrated from stackoverflow.com Apr 29 '11 at 22:03

This question came from our site for professional and enthusiast programmers.

up vote 26 down vote accepted
youatwork@officepc$ autossh -R 12345:localhost:22 notroot@serverpc


you@homepc$ autossh -L 23456:localhost:12345 notroot@serverpc

you@homepc$ ssh youatwork@localhost -p 23456

What you could do is this: in step 1 forward a remote port from the office PC to the server (12345 is used as an example, any port >1024 should do). Now connecting to 12345 on the server should connect you to port 22 on officepc.

In step 2, forward the port 23456 from your home machine to 12345 on the server (whence it gets forwarded to officepc:22, as set up in step 1)

In step 3, you connect to the local port 23456 with your office PC login. This is forwarded by step 2 to port 12345 on your server, and by step 1 to your office PC.

Note that I'm using autossh for the forwardings, as it's a ssh wrapper which automatically reconnects the tunnel should it be disconnected; however normal ssh would work as well, as long as the connection doesn't drop.

There is a possible vulnerability: anyone who can connect to localhost:12345 on serverpc can now connect to officepc:22, and try to hack into it. (Note that if you're running a SSH server, you should anyway secure it above the basic protections which are on by default; I recommend at least disabling root login and disabling password authentication - see e.g. this)

Edit: I have verified this with the same config, and it works. GatewayPorts no only affects the ports that are open to the world at large, not local tunnels. This is what the forwarded ports are:

  outgoing ssh to serverpc:22
  listening localhost:23456 forwarded through ssh tunnel
  listening ssh at *:22
  incoming localhost ssh tunnel (from homepc) forwarded to localhost:12345
  listening localhost ssh tunnel (from officepc) forwarded from localhost:12345
  outgoing ssh to serverpc:22
  incoming localhost through ssh tunnel (from serverpc) forwarded to localhost:22

So, as far as the network stack is concerned, it's all local traffic on the respective loopback interfaces (plus ssh connections to serverpc); therefore, GatewayPorts is not checked at all.

There is, however, the directive AllowTcpForwarding: if that is no, this setup will fail as no forwarding is allowed at all, not even across the loopback interface.

  • I belive this method you are supposing is called "reverse ssh-tunnel". Unfortunately this requires GatewayPorts on Server set to "yes" in /etc/ssh/sshd_config. This server has no gateway ports enables and I have no root access there. – Frank Apr 29 '11 at 16:07
  • 3
    @Frank: Actually, I don't think so: GatewayPorts no restricts the opened ports to be only accessible on the loopback interface; note that in step 2 you're forwarding on the loopback interface (in fact, both the forwards are "localhost only"), so this might work (AllowTcpForwarding no in the sshd config would break this). – Piskvor Apr 29 '11 at 16:22
  • 3
    @Frank: Yup, confirmed. This works even with GatewayPorts no; edited the answer. Note that there are other directives (such as PermitOpen and AllowTcpForwarding) that can break this setup: manpagez.com/man/5/sshd_config – Piskvor Apr 29 '11 at 16:47
  • Excellent answer! It works, you saved my weekend! Many thanks!! – Frank Apr 29 '11 at 18:49

If you can ssh to the internal server from home and from the internal server to your office Linux machine, then from home you can use the ssh ProxyCommand to bounce silently through the server to the internal machine via nc (netcat)

# ~/.ssh/config on your home machine:
Host internalpc 
   ForwardAgent yes 
   ProxyCommand ssh user@server.example.com exec nc internal.pc.example.com %p

Then you just ssh user@internalpc and you are silently forwarded through the server machine, no opening of ports or tunnels required on either end.

  • 1
    Thanks for your answer. Unfortunately, neither the Home PC, nor the Server can initiate access to the Office PC. But both the Office PC and the Home PC can initiate connections to the Server. – Frank Apr 29 '11 at 16:05

Install Robo-TiTO in the computer that you want to access SSH remotely.

  • This will allow you to access SSH using from Google Talk Client Apps anywhere.
  • There is no need for a public IP address or special setting.
  • It's Free and Open Source, Not Paying any application services anymore.
  • No need to open SSH port (keep your computer safe).
  • No need to open any tunneling (e.g., VPN or something like that)

The following installation instructions are obsolete, as the site has moved. The new URL is https://github.com/formigarafa/robotito

I made a script (tested on my Raspbian OS in Raspberry Pi) so you can easily install Robo-TiTO on Raspberry Pi, Debian or Ubuntu Box (Debian package distribution). this is the steps to get your Linux box remoteable:

  1. Open Shell Command or you can call it Terminal, go to your home folder, Download installer script by command:

    $ wget https://opengateway.googlecode.com/files/robotito
  2. after that run the script by entering command:

    $ sudo ./robotito
  3. and then you can edit file credentials.rb from the config folder of Robo-TiTO using your GTalk account and save it by pressing Ctrl+X and Y.  Default is using nano editor.

  4. running the Robo-TiTO from Robo-TiTO folder by command

    $ cd robotito
    $ ./jabbershd start
  5. Now that this is done you can use SSH from any Google talk client.  Don't forget to add the Robo-TiTO GTalk account to your Google talk account and test it with chatting each other before using the account.

  • 4
    I have a serious problem with "No need to open SSH port (keep your computer save)" - the shell-over-jabber bot which you propose is secured with, quote, CLIENT_PASSPHRASE = "logmein", in plaintext. That is literally zero security - you're making a truck-sized hole for anyone to enter. Contrast to SSH public key authentication: I'm authenticating over a secure channel, using credentials which never even cross the wire. Who's keeping their computer safe now? – Piskvor Apr 7 '14 at 16:11
  • @Piskvor, robotito will only run commands from whitelisted contacts. github.com/formigarafa/robotito/blob/master/config/… – formigarafa Feb 17 '16 at 22:06
  • I never run into any trouble because of the whitelist based authentication. If I am not wrong, the message transfer is encrypted when using with GTalk. One way or another, I changed it recently and now it uses a One Time Password from a tool like Google Authenticator or similar to allow access. – formigarafa Jul 2 '17 at 1:59
  • @formigarafa: (1) If you are or have been involved in the development of this product, you must say so, explicitly.  Using the same name is not enough; most people won’t notice that.  (You may mention it in your profile.)  (2) When you edit a post, you should fix it as much as you can.  For example, try to catch typos like “I’ts”.  And, if a link has gone down, don’t just label it as a dead link; put the new URL into the post.  People shouldn’t have to dig through the comments to find the correct information. – G-Man Jul 2 '17 at 6:02
  • @G-Man, The original answer and edit were not mine. And I never had the intention to make it look as mine. I noticed a dead link on the answer, I did not create the link either. I was actually keen to see its content and tried to follow it. Unfortunately I couldn't find the resource. I marked as a dead link on the hope that whoever wrote the answer would be notified by the change and try to fix it. – formigarafa Jul 9 '17 at 2:19

Piskvor's solution works and is nice. However, it keeps terminals dangling open with login shells hanging. Not very cool.

I've always used this little script I wrote to connect to a server and keep it connected by running it in cron:


#Check that we have an active connection to the remote system
ACTIVE_PROCESS=`ps -ef | \
    grep -v grep | \
    wc -l`
if [ $ACTIVE_PROCESS -lt 1 ]; then
    echo "`date` : establishing connection to $TARGET_HOST on port $TARGET_PORT"
    screen -m -d ssh $TARGET_HOST -l $T_USER -R $TARGET_PORT:$TUNNEL_PORT > /dev/null

I bet we could fix Piskvor's solution using the more elegant autossh alongside maybe a detached screen or use the -NT ssh arguments to just keep the connection up in the background.

  • Thank you for the compliments :) For my use cases, I regularly need the shell access, as well as the forwardings; plus, I have tried to show the minimal case here (it is possible to simplify the above into two commands with transparent SSH host hopping, but that would require additional configuration on the homepc computer). – Piskvor Apr 7 '14 at 16:02

To me , it sounds like, instead of a SSH tunnel, you should try a VPN: the kind that works by using a server on the outside to proxy through, such as Hamachi . There are other free softwares like this one, but Hamachi is my fav.

  • Now that the network actually has public IPv4 addresses assigned, Hamachi is in trouble (if Hamachi is running, you can not access a somewhat-random part of the internet). Also, Hamachi is no longer free-to-use. – Piskvor Aug 14 '14 at 12:26

Your Answer


By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.