A hack to make dbclient to tcp forwarding netcat style. eg ./dbclient -i testkey -L 1234:remotehost:remoteport tunnelhost will ssh to tunnelhost (using testkey, there's no way to ask for a password) and then tcpfwd to remotehost:remoteport on stdin/stdout. There's no way to give a cmdline password, so -i for a keyfile will have to do. Yet another reason for agent forwarding. The 1234 is a dummy var, I think it has to be a valid portnumber though.

480        87
960       111
1440       135
1920       159
2400       200
2880       224
3360       248
3840       272
4320       296
4800       320
5280       344
5760       368
6240       392
6720       416
7200       440
7680       464