Sometimes it's very useful to directly connect tools (i.e. a database management tool) that runs on a developer or administrator PC, to a daemon on a server (i.e. mysql server) that is only available locally with the server for security reasons.
For the following tunnel examples we assume:
www.clazzes.org, runs a mysql server listening on
testdb, accessible for user
webadmin, and we have a ssh key allowed to connect to
email@example.com(or we have password based ssh access)
testdbthrough an ssh tunnel
mysql -h 127.0.0.1 -u dbtester --password=testsecret testdb
3333on our local system, we actually connect to mysql-server's port
DO NOT bother to try using those credentials, it might get your IP blocked!
OpenSSH is the default ssh implementation for most Linux distros, and even Microsoft has announced an agreement to include it in Windows.
I'm not sure how equal or similar other Unix ssh clients (like BSD, MacOS) are.
To create a tunnel that stays in foreground:
# stay in forground, may be put in background by pressing Ctrl-Z and the command bg ssh firstname.lastname@example.org -L 3333:127.0.0.1:3306 -N # go in background, a bit difficult to stop ssh -f email@example.com -L 3333:127.0.0.1:3306 -N # evtl. check that ssh listens on 3333 lsof -i -n |grep -i listen |grep 3333
Test connect to the database:
mysql -h 127.0.0.1 -P 3333 -u dbtester --password=testsecret testdb
To close the tunnel, abort or kill the according
ssh process (
ctrl-c, evtl. after
fg to get it back to the foreground).
Putty is the most common ssh client for Windows. Hints for setting up key-based ssh access with Putty can be found everywhere on the internet, we'll focus on tunneling here.
Just one hint anyway: With ssh keys, have
pageant running. Simply double-klick the
.ppk file or even put it in your autostart group.
To setup the tunnel:
webadmin, set one up and don't forget to save the session before (re)trying to connect.
Source port", enter
127.0.0.1:3306as shown in this screenshot (click to enlarge):
Category", click on "
Save", then "
Now a putty window should open, you should be on
webadmin., and the tunnel should be up.
To check if there's a tunnel, open a Command window and use netstat like this:
netstat -a -n |find "3333" # output should show something like TCP 0.0.0.0:3333 0.0.0.0:0 LISTENING
To close the tunnel, just close the according putty terminal, preferrably by entering