The tunnel , starting for vnc1 on port 4000 on the outside interface of the firewall has it's other end at their_server's_internal_ip:4000 , they will never see your server that way, because your vnc2 is on port 4001 on the outside interface, the other end points to your_servers's internal_ip_address:4000 . Let the fact that you are using ssh to create the tunnels not disturb into the tunnelling. You could use any other tunnelling protocol/application. vnc1:4000|___Tunnel____server1:4000 vnc2:4001|___Tunnel____server2:4000
and you might want to have a look a squid. I can do stuff like, if domain-name=AAAA then forword the request to ip1:port else if domain-name=BBBB the forword request to ip2:port , check the squid. Then of course you need to make sure, that all port:80 requests go to the squid, say at port:81 or 8080, by tunnelling, and let the squid do the job and forget about the redirect. Cheers Szemir On September 25, 2004 01:18, Shawn wrote: > I kinda understand what you're saying, but don't know how to make this > happen. Also, if I tunnel VNC through SSH, does that mean I can't have both > an SSH session to MY server, and a VNC session to the remote server at the > same time? The clients in this case shouldn't have access to my servers at > all - just their own... > > Thanks for the feedback. > > Shawn > > On Friday 24 September 2004 23:35, Neil Bower wrote: > > What may be best is to set up SSH forwarded ports, then tunnel to the VNC > > through the SSH. > > _______________________________________________ > clug-talk mailing list > [EMAIL PROTECTED] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca _______________________________________________ clug-talk mailing list [EMAIL PROTECTED] http://clug.ca/mailman/listinfo/clug-talk_clug.ca
