First note that special port numbers must be used. I don't give them explicitly here for security reasons, but when you know the first 3 digits, it goes like this:
xxx3 is crater xxx2 is dorado xxx8 is "linuxpilot"In general, you probably only want a VNC session to crater.
Due to a Fedora bug, we cannot set up user pilot to use VNC without losing the ability to login at the console. This may be solved someday, but for the time being, the following is a workaround. VNC sets up a session for the user "vncpilot" which causes no conflict with the console. This does cause some limitations. The VNC session for "vncpilot" is a read-only session that only allows the oven to be observed. In general this is a good thing, but sometimes it is desired to actually change things remotely. There are two ways to do that:
su - pilot ovenThe "su" command will change your identity (in that window only) from vncpilot to pilot and that will allow you to run oven without being forced into readonly mode.
This brings up the issue of using iraf/oven versus plain oven. The above has you start the native oven rather than the original oven that must run inside of an IRAF cl session. They are identical with one exception. The native oven cannot launch the donut graphic cursor on the ximtool display. If you need that, use oven run under cl in the green window.
ssh -p 1776 -f -L 38999:localhost:5901 clamdigger.org sleep 20 vncviewer localhost::38999
The expert I consult with recommends "RealVNC".
This was recommended, but I was not satisfied. Both a server and client are available for download and not clearly labeled. I ended up downloading the server package by mistake and then it kept popping up until I went into my Downloads directory, found it and deleted it.
The viewer package seems to just be a bare .exe, not an installer and required me to enter an admin password whenever I want to run it, so I find this pretty obnoxious.
Use RealVNC or TightVNC.
Here is a process for bouncing the VNC connection through Putty (the typical Windows ssh client).
I did this first to a linux machine that simply runs ssh on port 22 (the normal default).
You can make the actual ssh connection, then a right mouse click on the title bar will give you the menu that includes "Change Settings". Given that menu, navigating to "Connection--SSH--Tunnels" is easy enough.
Note that when you set up putty as an ssh tunnel, it continue running the ssh session also.
I fire up RealVNC viewer, enter localhost:1 into the entry field and voila, it asks me for my VNC password and away I go.
If you get the following message from RealVNC, it means your VNC server is not running.
The connection closed unexpectedly.If the VNC server is not running and you try TightVNC, you will immediately get the "Connection gracefully closed" message.
Tom's home page / email@example.com