Note for IE users: Be careful of leaking DNS information. IE wants to resolve things with the local resolver. And encrypted tunnel always going to hide that fact that you left the 'All-Hands' company meeting and started surfing hotjobs.com.
One thing to remember with SSH tunnels is that the VNC client is likely to decide that the server is local and use RAW encoding, so remember to specify the encoding you want to use.
Also, your choice of programs is going to matter a lot. I use VNC over an ssh connection from a machine behind a (over-loaded) T1 to connect to a server on DSL. The connection is tunneled over SSH. I have found that FSF Emacs and XTerm are quick, gnome-terminal is tolerable if you are carefull about options, and XChat is unuseable.
Basicly, any program that draws it's entire windows using MIT-SHM and always copies the entire window even if only one pixel has changed isn't going to work very well. So watch out for programs that have theme-able backgrounds, checkboxes, pop-up ducky calanders, etc.
(Cough *GNOME* Cough *KDE* Cough)
These programs aren't going to be usefull. Also, avoid programs that are going to reduce performance to just raw copying large memory blocks. Image Viewers and such like fall into this catagory.
Use a simple-to-draw window manager and use click-to-focus mode. If you use focus-follows-mouse, then everytime you drag the mouse over a window, the WM is going to resend all the window decorations in the "focus" color.
There are some CPU/Bandwidth tradeoffs you can make as well. It's worth experimenting a bit to see what works for you. I have a P233 on a 128K (up) DSL connection, and I have found that the spending CPU to reduce bandwidth is almost always the right choice.
When I am on the LAN (FE), then I can run almost anything without problem. For remote work, I can use emacs and xterm, which is mostly what I use for work anyway.
Slashdot Mirror
Note for IE users: Be careful of leaking DNS information. IE wants to resolve things with the local resolver. And encrypted tunnel always going to hide that fact that you left the 'All-Hands' company meeting and started surfing hotjobs.com.
I suspect that rather than Canada getting the concept from US law, both the US and Canada inherited the concept from English law.
One thing to remember with SSH tunnels is that the VNC client is likely to decide that the server is local and use RAW encoding, so remember to specify the encoding you want to use.
Also, your choice of programs is going to matter a lot. I use VNC over an ssh connection from a machine behind a (over-loaded) T1 to connect to a server on DSL. The connection is tunneled over SSH. I have found that FSF Emacs and XTerm are quick, gnome-terminal is tolerable if you are carefull about options, and XChat is unuseable.
Basicly, any program that draws it's entire windows using MIT-SHM and always copies the entire window even if only one pixel has changed isn't going to work very well. So watch out for programs that have theme-able backgrounds, checkboxes, pop-up ducky calanders, etc.
(Cough *GNOME* Cough *KDE* Cough)
These programs aren't going to be usefull. Also, avoid programs that are going to reduce performance to just raw copying large memory blocks. Image Viewers and such like fall into this catagory.
Use a simple-to-draw window manager and use click-to-focus mode. If you use focus-follows-mouse, then everytime you drag the mouse over a window, the WM is going to resend all the window decorations in the "focus" color.
There are some CPU/Bandwidth tradeoffs you can make as well. It's worth experimenting a bit to see what works for you. I have a P233 on a 128K (up) DSL connection, and I have found that the spending CPU to reduce bandwidth is almost always the right choice.
When I am on the LAN (FE), then I can run almost anything without problem. For remote work, I can use emacs and xterm, which is mostly what I use for work anyway.
Epmos
I'm a /. user who used KA9Q. A hint for the rest of you--KA9Q is a HAM Radio Operator's call sign.