The TurboVNC documentation, which I wrote, explains how to use the product with an SSh tunnel, but that product was sold by Sun for 5 years, so we had plenty of opportunity to flesh out usability problems. TigerVNC is still a relatively new project.
On Mar 4, 2010, at 6:01 AM, ti...@piments.com wrote: > On 03/04/10 10:06, DRC wrote: >> ti...@piments.com wrote: >>> On 03/03/10 22:31, DRC wrote: >>>> ti...@piments.com wrote: >>>>> > VNC context: >>>>> > >>>>> > All tiger vnc software is run on the remote kubuntu box >>>>> via ssh >>>>> from >>>>> > local linux system. >>>>> > >>>>> > r...@local# ssh -C -X -L 5900:localhost:5900 remote.dyndns.info >>>>> > r...@remote:~# vncviewer localhost:0 >> >> Did you see the follow-up message indicating that you are running the >> vncviewer in the wrong place? I think that explains all of the >> problems >> you were having, including why the bandwidth was being mis- >> detected. In >> fact, it wasn't being mis-detected. It's simply that you're trying >> to >> run vncviewer on the same machine as the VNC server. You need to run >> vncviewer on "local", not "remote". >> > > Yes I did. That was indeed the problem. > > I posted thanks to Henry Wong but it was send from the wrong account > and got held back by the list. > > So what I said in my earlier post was correct. The fast transaction > was happening locally within the remote machine. Apparently you > misunderstood when I suggest this. > > Funny no-one spotted this before, I took trouble to indicated the > context in my posts. > > This is probably soooo obvious to those used to this sort of > development but needs documenting better. I read the man page it's > because I didn't know. After reading it I'm no wiser. > > from man xvnc > -localhost > Only allow connections from the same machine. Useful if > you use SSH and > want to stop non-SSH connections from any other hosts. > See the guide to > using VNC with SSH on the web site. > > > I don't know what web site that referred to historically but there's > nothing in the way of doc on the tigervnc web site. > > The man entry probably needs updating. > > It's unfortunate no one spotted this earlier, but a big thanks to > Henry for saving me wasting any more time struggling. > > Anyway , now all is working well (with the excpetion of the 1366 x > 1366 desktop) and the software is pretty efficient. So many thanks > to all who have contributed over the years. > > > best regards. > >> >>> Well there's about an order of magnitude speed difference if I >>> don't use >>> -C !! That's what led me to think it was coming raw down ssh link. >> >> Since you are running vncviewer on the server, not the client, what's >> coming over the SSh link are XPutImage() requests, which most >> definitely >> would benefit from SSh compression (but would still be very slow >> compared to VNC compression.) >> >> >>> yes, running ssh -C , jpeg quality can be seen to change and F8 >>> connection information shows "requested encoding" changes >>> according to >>> what I set on command line or via options dlg. >> >> Yes, because what is happening is that the VNC server (or module in >> this >> case) is compressing the images as JPEG, vncviewer (which is >> running on >> the same machine as the module) is decompressing the JPEG images and >> drawing them as uncompress X bitmaps. The uncompressed X stream is >> what >> you're passing through SSh. That is not what you want. >> >> > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
