SSH Tunnels

I need to access a remote C-Gate over SSH. I've set up tunnelling for ports 20023-24 and 20123 using PuTTY, which basically means that once I connect via SSH those ports are open on localhost but tunnelled through the connection to the remote C-Gate. And it all seems to work.

However, Toolkit won't let me set up a remote connection to localhost, so I have to set up the connection then connect locally in Toolkit, which on finding the relevant ports open then doesn't try to start C-Gate locally.

My question is this: will this cause me any problems? Eg does Toolkit make any assumptions about a local connection (eg it being faster) that will make it unreliable over a slower connection?

Also, it would be nice if I could create a "remote" connection to a port other than 20123 so that I could leave the tunnel open but still be able to switch to the real local C-Gate if necessary without having to drop the connection and start C-Gate. Is there a way to do this?

 

In our case we have a Linux server running C-Gate amongst other things. SSH gives us secure access via public/private key pairs which site have accepted, and we can tunnel everything else through it. Although C-Gate traffic is encrypted from Toolkit, opening the port would not restrict who was able to use it. But also we're tunnelling more than just C-Gate so one size fits all.

 

This is very true! Tunnelling over SSH is easier to set up and just "works" though. SSH was already in use on the server so it didn't require anything additional at that end.

Bus OpenVPN would be an equally good solution.