<https://forums.hak5.org/topic/33456-cant-ssh-in-a-external-network/#comment-249666>
<http://schema.org/text>
"Woah, woah, WOAH! Hoooold on there tiger. \nDon't go running around with all sorts of options for port forwarding and what not. From what you're saying you don't have an SSH connection so -R can't even come into play just yet (this tunnels over the existing connection. No connection -&gt; no tunnel). Let's start with the basics: Making sure you can access the server remotely. \n1. Get your sshd to listen on a port you want to access (the default of 22 or https port 443 are common ones). Verify correct operation by connecting using the LAN IP address. \n2. Get your router to NAT incoming connections on a port you want to access (22/443/other) to your ssh machine on the port that it's listening. Verify correct operation by connecting using your current internet IP address. \n3. Using a device that you know to have full access to the internet (so no proxy, no nothing), try to access your sshd on your current home internet IP address on the port set in the router. \nAt this stage you should be set to connect to the ssh server from anywhere. Any problems in doing so should now be attributed to the *other* network blocking you access to your home router at the given port. An example of that is my current workspace, where the local proxy only allows outbound traffic to http and https, which is why my home sshd is running on port 443.  "
<https://forums.hak5.org/topic/33456-cant-ssh-in-a-external-network/>