VNC and Firewalls, a story.

[William L. (Bill) Barth]

>>>>> "BJ" == BJ Blanchard <blabj "at" dainty.ca> writes:

    BJ> In order to avoid the multiple nested ssh's, use a port
    BJ> redirector (eg. redir).  On my firewall, I redirect port 24 to
    BJ> port 22 on my Solaris box, so from home I do: ssh -p 24 ...

I assume that you mean that on firewall at work I should redirect a
port through to a specific machine. This is not really an
option. Besides the double ssh (i.e ssh -t work_firewall ssh
work_machine blah blah...) syntax allows me to select the internal
machine to connect to at runtime.

    BJ> This should increase your performance, as well as simplify
    BJ> your command line.

I don't think that there's any performance loss here. Xvnc doesn't
send any data through the double ssh and the third ssh in the line
creates a separate connection back to my home machine. So only things
started on by the double ssh that send data through the third ssh
(i.e. things I type into the shell that is opened on the home machine)
actually go through three ssh's. That's something I can deal with.

Bill.

-- 
Bill Barth                   |   Home: (512) 797-3045
bbarth "at" cfdlab.ae.utexas.edu  |   Work: (512) 471-4069
Office: WRW 111              |   Fax:  (512) 232-3357
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to majordomo "at" uk.research.att.com
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------