Auto-Establishing SSH Tunnels

Standard

SSH Tunnels – Auto-Establishing

I have a cron job which connects manually replicates a database over an SSH tunnel for those ‘Oh Sh!t’ moments. Sometimes that SSH tunnel will drop or fail to establish. Within the cron job I needed a way to make sure that didn’t happen.

The Code

The code below is the first part of the bash file executed by cron.

We run netstat -a and grep for the port the tunnel is supposed to be established on, and if it is less than 2, it will execute and create the tunnel.

[bash]
#!/bin/bash
REMOTEHOST=10.1.1.1
TUNNEL=$(netstat -a | grep -c 3307)

if [ $TUNNEL -lt 2 ]; then
ssh -f root@$REMOTEHOST -L 3307:localhost:3306 -N
fi
[/bash]

After the above snippet, you can continue whatever script or application which needed the SSH tunnel to be established.
Enjoy!

Create an SSH Tunnel

Standard

Background: The Need For A Tunnel

For hundreds of years, our civilization has been building tunnels to circumvent blocks. In the technical world, the need it still there. When a device sites behind a firewall with specific ports blocked, you can proxy your traffic through a server/host on the outside to reach your destination. Below, you can find some example scenarios and the commands used to accomplish the task.

Note: From a security perspective, the firewall ports and/or networks are blocked for a reason, so you should only do this if you understand the risks and know what you are doing.

Creating The Tunnel

There was a situation where a client wanted to get to a website, let’s use www.highonphp.com as an example, but the network was blocked by a firewall. An exception was submitted to their security team, but due to their policy deployment schedule, would have taken 30 days for the change to take effect. They had an external server which could reach the destination, and decided to use that as their proxy.

Blocked Port 80/Destination Network
The following command will forward all traffic typed as http://localhost:8080 to highonphp.com port 80.
[bash]
ssh -f user@remoteserver.com -L 8080:highonphp.com:80 -N
[/bash]
Note: If you are redirecting traffic to port 80, and the local port is not 80 or 443, then you may need to specify the ‘http://’ in your URL so the browser knows what protocol to talk.

Tunnel Traffic To The Middle Man
If an SSH connection can be established to a remote host, but other ports are blocked, you can specific localhost in the command to have traffic stay on the remote system. For example, if you can SSH to a box and need MySQL access but cannot reach port 3306, the following command will tunnel your MySQL traffic:
[bash]
ssh -f user@remoteserver -L 3307:localhost:3306 -N
[/bash]

Then, within your script or application such as or Querious, use host ‘localhost’ and port ’3307′.

Tunnel With PuTTy

PuTTy is one of the best SSH client applications that has ever existed. One of the benefits of PuTTy, is the ability to tunnel traffic from a Windows machine to another remote system. To set up the tunnel, enter the normal connection details and follow the steps below.

To tunnel traffic from localhost:8080 to remotehost:80, use the following:

  1. Expand Connection
  2. Expand SSH
  3. Expand Tunnels
  4. In Source Port, enter the port you want your local system to use, 8080
  5. In Destination, enter the remote system and port, remotehost:80
  6. Click Add

Enjoy.