Hi,

I've read through tons of docs, ....

I'm trying to configure a linux box to handle multiple requests for vnc-ssh 
connections to multiple sites.
And I'm hoping to write a process that handles the requests, to automate it.  

NT1(vncviewer)--->port# Linux1(ssh client)--->Internet--->Linux2(ssh 
server)--->NT2(vncserver)

It works well manually--I set up the ssh forward on Linux1 like this:
                             ssh  -L  port#: NT2 :5900  Linux2

Then I go over to NT1 and tell vncviewer to connect to Linux1 on port#.  Voila, NT2's 
desktop is mine.

What I was hoping to do was write a process to listen on Linux1's port#, spawn off a 
process that invokes the ssh forward command line.  Then I could have each vncviewer 
NT box send Linux1 the ip (site) that it wants to connect to.  

But it appears that ssh needs to be the listener on port# on Linux1, and that we can't 
just have ssh do the forward, and accept data from another process that actually does 
the listening.  
Does anyone have any more information on the -L switch or on a way to have ssh let 
another process do the listening and hand it the data?

I want to be able to execute the forward without having that Linux1 port# in the way.  

The only other idea we've come up with is that we could force each different vncviewer 
to use it's own Linux1 port#, and then kick off the ssh forward using that port# when 
the home-written process hears a connection on a range of specific ports.  ugh.  

Thanks,
Tamara





Reply via email to