You're posting this to turbovnc-users. Did you mean to post to virtualgl-users instead? I'm struggling to figure out how TurboVNC is involved, since you're using vglconnect. Also note that vncconnect and vglconnect are not the same thing. I'm going to assume that you meant vglconnect, even though you said "vncconnect" in the title of the post.
That particular SSH command line is forwarding outbound port 3435 on the client to inbound port 22 on atest-coamps, so that means you need to make subsequent SSH connections using localhost:3435. Does 'vglconnect -s saverino@localhost -p 3435' not work? DRC On 6/16/17 4:50 PM, Michael A. Saverino wrote: > > OK, I have to get to a vgl system that sits on the other side of an ssh > firewall. The ssh command to get through the firewall is as follows: > > sudo -E ssh -v -o IdentitiesOnly=yes -i ~/.ssh/id_dsa -N -C -l saverino > [email protected] -L 3435:atest-coamps:22 > > I need to get to machine atest-coamps which has VirtualGL and my > application. vglconnect -s won't get me through with this > configuration. Any suggestions? I am not shy about modifying the > vglconnect script if I have to. > > Many Thanks, > > Mike... ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
