Port 22 will be selected which can be left alone unless you run the SSH service on a different port. Note: If on the remote networkвЂ™s subnet is same as your home networkвЂ™s subnet then you might run into IP conflicts.ДЎ) On the remote system, open putty enter the IP address or dynamic DNS (DDNS) name in the host name field. You can make any number of connections to all your home machines by just repeating steps (3) and (4).

Since we are using a proxy it will resolve the local subnetвЂ™s IP address properly. SSH connect to any machine at home using the local subnet IP address.Open another putty session and configure it use the previous putty session as proxy.From this session connect to your default SSH server at home.Open a putty session and configure it to act as a tunnel.

Then using this connection as a tunnel we can connect to any machines at home by addressing them with local sub-network address (such as .x). The basic idea to get this working is that we make one initial SSH connection to our home machine.

On the router, port forwarding is enabled for SSH service to at least one of these machines.

One/more Linux/Windows machine(s) to which direct SSH access is required.

Home routerвЂ™s internet accessible IP address or dynamic DNS (DDNS) address.

Remote machine with Putty installed in it.

But now I found a cooler way to get SSH access to all my machines at home without setting up port forwarding or remembering any port numbers and most importantly, I can address my home machines with local subnet IP address, no matter wherever I connect from the internet. It was also difficult to remember port number forwarded for a particular machine.

It was a tedious process of enabling port forwarding and then disabling it after use. Previously, when I needed SSH access to these machines I used to setup port forwarding on my router to each of these machines. I have multiple Linux machines at my home. Create your own Virtual Private Network for SSH with Putty

Putty ssh settings