[Thinlinc-technical] Support for tunneling using ssh tunnels localhost -> remote

Peter Astrand astrand at cendio.se
Wed Apr 25 08:04:15 CEST 2018

Hi. Yes, this is correct: After communicating with the master (VSM 
Server), the client will establish a new SSH connection to the selected 
VSM agent machine. The connection will use the configured 
"agent_hostname". If you need to do special things such as use an existing 
tunnel, you can use the client side parameter HOST_ALIASES (see 


If you have a cluster or many machines, you need to setup tunnels and 
define aliases for all of them.

Wrt ProxyCommand, we have bug covering that:



On Tue, 24 Apr 2018, harty at ironwolve.com wrote:

> I sit behind a firewall with a squid proxy, I can ssh over the squid proxy, so setting up local ssh tunnels works for most of my linux/windows apps. Using web
> client now, but cutting and pasting is annoying with the toolbar in the middle.
> Using ssh tunnels with thinlinc doesn't seem to work.   Normally I'd just setup a localhost:2222 port to remotehost:22 and tell the app using ssh to connect to
> localhost:2222 and its good to go.   
> Thinlinc appears to setup more ssh tunnels and gets confused, I see it tries to connect to the remote host and ignore the local tunnel. 
> VNC can tunnel over ssh tunnels, so not sure if there is an option to maybe connect directly to the thinlinc vnc client, maybe?
> Also, if any way to support the local ssh config for proxycommand programs like proxytunnel or corkscrew would also be a nice addition for tunneling. Proxytunnel
> works on windows for putty, so that's a good option for windows users using a proxy.
> Thanks,
> -Brook

Peter Astrand
Cendio AB		https://cendio.com
Teknikringen 8		https://twitter.com/ThinLinc
583 30 Linkoping	https://facebook.com/ThinLinc
Phone: +46-13-214600	https://google.com/+CendioThinLinc

More information about the Thinlinc-technical mailing list