[twill] twill Digest, Vol 8, Issue 14
johnbmudd at gmail.com
Mon Mar 20 14:54:37 PST 2006
Thanks! VNC works much better than ssh alone.
The only stumbling block is that the remote Linux box has all but port
22 (ssh) blocked. So running vncviewer at home couldn't access the
port (5901) published by the remote vncserver. But it's easy to
forward the remote port home with the following command.
ssh -2 -n -R 2024:localhost:5901 -N <my home IP addr>
I chose port 2024 arbitrarily. Now I can connect from home using the following.
It works great. This remote Linux box only gives me about 30 KB/sec
net access but now that I'm using VNC I have a Linux desktop that
works well. Now I can try Firefox and Seleniun-IDE.
On 3/20/06, twill-request at lists.idyll.org <twill-request at lists.idyll.org> wrote:
> Message: 1
> Date: Mon, 20 Mar 2006 08:15:59 +1100
> From: James Cameron <james.cameron at hp.com>
> Subject: Re: [twill] twill & spidermonkey?
> To: twill at lists.idyll.org
> Message-ID: <20060319211559.GA3841 at hp.com>
> Content-Type: text/plain; charset=us-ascii
> On Fri, Mar 17, 2006 at 05:35:20PM -0500, John Mudd wrote:
> > Using ssh causes the browser to appear on my home Linux system but
> > requires a lot of net traffic which slows testing.
> Methods to reduce this net traffic ...
> 1. install a VNC server on the remote system and use a VNC client on
> your home Linux system,
> 2. install a VNC server on another remote system, use a VNC client on
> your home Linux system, and then within that run "ssh -X" to the remote
> With the VNC protocol, you can close the client, thus stopping screen
> updates (net traffic), and then reconnect the client later to see the
> result. With some VNC programs you can also restrict the update rate.
> VNC makes periodic updates to the screen. But using ssh every update is
> passed across the net. An automated web browser would generate a lot of
> screen updates, and so the difference between VNC and ssh would be more
> James Cameron
More information about the twill