Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Dec 2003 10:26:35 +0100 (MET)
From:      Helge Oldach <helge.oldach@atosorigin.com>
To:        molter@tin.it (Marco Molteni)
Cc:        freebsd-net@freebsd.org
Subject:   Re: ssh tunnels and Xvnc - (yes, I know... What? not again!?)
Message-ID:  <200312120926.KAA06641@galaxy.hbg.de.ao-srv.com>
In-Reply-To: <20031212080131.GB962@cobweb.example.org> from Marco Molteni at "Dec 12, 2003  9: 1:31 am"

next in thread | previous in thread | raw e-mail | index | archive | help
Marco Molteni:
>> I have a situation that has not been fully addressed by the excellent 
>> documentation on getting ssh tunnels and remote X-windows display managers
>
>> (like VNC) running. And my feeble brain is too damaged by the dreaded
>lurgy 
>> to make heads or tails of it.
>> 
>> home machine (home) ---- ISP --- internet --- work firewall --- work
>machine1 
>> (additional firewall?) (work1) --- work machine 2 (desktop) (work2).
>> 
>> I can ssh from home to the work1 and ssh from there to work2.
>> home runs windows 2k and I have (full) admin access 
>> work1 and 2 run FreeBSD
>> I have root access on work2 but not work 1
>
>you should be able to do it in one step, no need to log into work1,
>no need to run the listener... you just need your ssh public keys
>in work1 and work2

Yep.

>from home you double tunnel:
>LOCALPORT=6333
>REMOTEPORT=5901
>ssh -t -L $LOCALPORT:localhost:12945 work1 \
>    ssh -L 12945:localhost:$REMOTEPORT work2

As home is a W2k box, ssh won't probably work exactly like this...

Putty supports a "don't allocate a pseudo-terminal" option to achieve
the effect of ssh's "-t" option. (Required, otherwise work1 will bark.)

Helge



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312120926.KAA06641>