SSH TUNNEL WITH PUTTY FREE

When SSH session is established, we should be able to reach port 3100 on the remote server via 127.0.0.1:3100. Save the configurations to session, and click Open to establish the SSH connection. Again note the 4L at the beginning of the configuration, which correspond with Ipv4 and Local. (Local and IPv4 should be selected)Ĭlick on Add, and you will get below.

Note the configurations with the radio button in two rows.

SSH TUNNEL WITH PUTTY FREE

While most SSH clients support local port forwarding, we are using PuTTY, which is a free and popular SSH client software.Īssuming you already have the server IP address configured in PuTTY, go to Connection -> SSH -> Tunnels, and add following configuration. But, the SSH client in our laptop requires some configurations. Since the traffic to destination port 3100 is encapulated, our firewall will sess only traffic to port 22.įor local port forwarding to work, there are no specific configurations to be done at the server. In local port forwarding, traffic destined to a port (3100 in this case) on the local server is forwarded to the remote server via the SSH tunnel. (While it is possible to get the 3100 port opened from firewall, in a typical organization it is a cumbersome process.) The corporate IT firewall, sitting between the laptop and the server, is allowing only SSH traffic to pass through. Our laptop is running Windows OS, and the Linux server is running a web application over port 3100. Let’s see the typical scenario, where this would come in handy. This post focus on local port forwarding when the client is not a Linux machine. There are two types of port forwarding local, and remote.

SSH port forwarding is a mechanism to send arbitrary traffic over an encrpted SSH tunnel. SSH port forwarding is a versatile feature.

Ssh tunnel with putty