You can also start it as a service or on reboot.įirst, install autossh. The good news is there’s a program that will set this up for you and keep it connected. What happens if this disconnects after you leave? Well, you can no longer access the reverse tunnel you’ve setup. -R 8081:localhost:9991 = We bind local port 8081 on the remote host, and again specify 9991 as our initial connecting port that where SSH listens.-p 9991 = We connect to SSH listening on the remote host (homeserver01) on TCP/9991.On remote machine homeserver01 you can now connect back to the original machine on port 8081 where you have bound a local port. You connect from to homeserver01 via SSH on port 9991 ~]# ssh homeserver01 -p 9991 -R 8081:localhost:9991 homeserver = a system you control that can accept inbound SSH connections.remoteserver = a remote system you cannot SSH to, but can initiate outbound SSH connections.From the remote host you can access the originating machine via the local port.Specify the -R option to open up a reverse tunnel on a local port on the remote host.SSH reverse proxies work very much like the following illustration: Luckily you can use reverse SSH tunneling and AutoSSH (automated tunnel persistence) and carry on. I recently needed to establish a persistent connection to a new Raspberry Pi setup remotely where the ISP did not allow proper port forwards. Those things might be behind an unbudging firewall with no way to forward proper ports for remote access, or perhaps you just want it setup access to resources this way. Sometimes you just need to get to things remotely.

Reverse ssh port forwarding