Differences

This shows you the differences between two versions of the page.

--- admin:reverse_ssh_tunneling [2015/06/28 10:57] – add tags ryan
+++ admin:reverse_ssh_tunneling [2015/06/30 03:42] (current) – [Solution] benishor
@@ Line 1: / Line 1: @@
+===== Reverse SSH tunneling =====
 ==== Problem ====
 Say we are working on a server product which we want to expose to the internet but our current networking set-up does not grant us an external IP address.
@@ Line 16: / Line 18: @@
 ''ssh -N -T -R *:8080:192.168.50.4:8081 benny@demoscene.ro''
-This roughly translates to: __I want sshd on demoscene.ro to listen on all interfaces on port 8080 and route all traffic that it receives to 192.168.50.4:8081 as seen from my local machine__.
+The above command roughly translates to: __I want sshd on demoscene.ro to listen on all interfaces on port 8080 and route all traffic that it receives to 192.168.50.4:8081 as seen from my local machine__.
 The extra flags have the following meaning:
@@ Line 32: / Line 34: @@
 ''sshd_config'' must be edited to contain ''GatewayPorts yes'' in order for sshd to be able to listen on interfaces other than loopback. Depending on your distribution, this entry may or may be not enabled by default.
-{{tag>reverse ssh tunnel}}
+Sometimes the connection might stall or drop. This is a great opportunity to try [[http://www.harding.motd.ca/autossh/|autossh]]
+{{tag>reverse ssh tunnel nix}}