Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

domm (4030)

  (email not shown publicly)

Just in case you like to know, I'm currently full-time father of 2 kids, half-time Perl hacker, sort-of DJ, bicyclist, no longer dreadlocked and 33 years old

I'm also head of [], maintainer of the CPANTS [] project, member of the TPF Grants Commitee [] and the YAPC Europe Foundation [].

I've got stuff on CPAN [], held various talks [] and organised YAPC::Europe 2007 in Vienna [].

Journal of domm (4030)

Wednesday August 02, 2006
05:21 AM

howto setup an ssh tunnel

[ #30511 ]

As I constantly forget how to do this (and as our $work firewall doesn't allow access to my svn repo running at port 1000 (don't ask!), I (mis)use this to remind myself:

ssh -l domm -L 8888:TARGET_HOST:1000 TARGET_HOST

To connect to TARGET_HOST:1000 via localhost:8888

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • the ssh tunnels get even better if you have a local squid running at home. Then, you can set up a tunnel to your squid at home, point your browser at it, and get at all the private stuff on your home web...
      ssh -L 3128:localhost:3128 me@my.home.server


  • This is what shell aliases are for. I solved that problem once, then automated it away. :)

  • Along similar lines to chromatic's suggestion of using a shell alias, if you're running a GNOME desktop (and all the cool kids seem to be these days) then you could use my SSHMenu [] to define SSH connections using a GUI.

    Also, if you have SSH access to the box where the SVN repository lives, then you don't need to have an SVN server listening on a port and you don't need forwarding either. Just use svnserve over ssh [].