From owner-freebsd-net@FreeBSD.ORG Fri Dec 12 12:28:53 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D91416A4CE for ; Fri, 12 Dec 2003 12:28:53 -0800 (PST) Received: from mail.vineyard.net (k1.vineyard.net [204.17.195.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id E172343D2D for ; Fri, 12 Dec 2003 12:28:50 -0800 (PST) (envelope-from ericx_lists@vineyard.net) Received: from localhost (loopback [127.0.0.1]) by mail.vineyard.net (Postfix) with ESMTP id D079593CAC; Fri, 12 Dec 2003 15:28:49 -0500 (EST) Received: from mail.vineyard.net ([127.0.0.1]) by localhost (king1.vineyard.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99711-10; Fri, 12 Dec 2003 15:28:49 -0500 (EST) Received: from vineyard.net (loopback [127.0.0.1]) by mail.vineyard.net (Postfix) with ESMTP id 8014C933C4; Fri, 12 Dec 2003 15:28:49 -0500 (EST) Message-ID: <3FDA24BC.5040406@vineyard.net> Date: Fri, 12 Dec 2003 15:27:40 -0500 From: "Eric W. Bates" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 X-Accept-Language: en-us, en MIME-Version: 1.0 To: paul van den bergen References: <200312121233.43680.pvandenbergen@swin.edu.au> In-Reply-To: <200312121233.43680.pvandenbergen@swin.edu.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS at Vineyard.NET cc: freebsd-net@freebsd.org Subject: Re: ssh tunnels and Xvnc - (yes, I know... What? not again!?) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Dec 2003 20:28:53 -0000 paul van den bergen wrote: > Hi all, > > 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. VNC probably isn't what you want to run. VNC is very useful and interesting; but unlike Windoze, you don't need to take over the console of your machines at work in order to use the FreeBSD machines. I run an X Server on my Win2k machine and tunnel X back from the remote machines. The ssh tunnels will daisy chain nicely from work1 to work2. The X Server we use is decent (copy/paste can be a pain). It cost us $45/copy from labtam-finland. I use VNC when I want to run a Windoze machine inside the firewall. I run the VNC server on the Windoze machine I need to control from home. The firewall is configured to block VNC. I ssh from home into a unix box at work, and run the VNC client app on the unix box and connect to the Windoze box. The VNC client is an X client; so it's window is tunneled back thru the ssh to my display at home. It can be a bit sluggish; but it works... > 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 > > I guess I have to: > > run Xvncserver on work2 > ssh tunnel (tunnel1-2) from work 2 to work 1 > ssh tunnel (tunnelh-2) inside tunnel1-2 > run vnclistener on home. > > any suggestions as to what is actually needed? can someone hold my hand though > this? > > >