<p>TightVNC has a '-via' option that allows using a gateway through the client and the VNC server.</p>
<p>TightVNC with this option can use a 'host in the middle' (gateway) to access another host. The VNC_VIA_CMD defines the ssh options to access the gateway.</p>
<p>Example:</p>
<pre class="literal-block">
host A access host C through host B. A and B have a public IP, but C is behind B.
A can access B with ssh.
export VNC_VIA_CMD='/usr/bin/ssh -2 -x -p <B sshd port> -l <B user> -f -L %L:%H:%R %G sleep 20'
vncviewer -via <B host ip> <C host IP from B>
</pre>
<p>true life example:</p>
<pre class="literal-block">
foo --> gateway.bar.com --> 192.168.1.36
foo> export VNC_VIA_CMD='/usr/bin/ssh -2 -x -p 55 -l foo -f -L %L:%H:%R %G sleep 20'
foo> vncviewer -via gateway.bar.com 192.168.1.36
</pre>
<dl>
<dt>links :</dt>
<dd><ul class="first last simple">
<li><a class="reference" href="http://www.vanemery.com/Linux/VNC/vnc-over-ssh.html">http://www.vanemery.com/Linux/VNC/vnc-over-ssh.html</a></li>
</ul>
</dd>
<dt>charcode test:</dt>
<dd><ul class="first last simple">
<li>&</li>
<li>&amp;</li>
<li>&#38;</li>
</ul>
</dd>
</dl>
http://home.zyrianes.net/blog/Articles/149/
Comments on article "TightVNC and VNC_VIA_CMD"2005-05-26T00:08:27.000003+02:00ludo on TightVNC and VNC_VIA_CMD
http://home.zyrianes.net/blog/Comments/20/
ludo
<p>I push the limit, I didn't feel good switching to the VPN installation and management.</p>
<p>With this solution I didn't need a VPN server on the host having the vnc server, just ssh access to the gateway :-)</p>
2005-05-18T12:50:51.000002+02:00Jkx on TightVNC and VNC_VIA_CMD
http://home.zyrianes.net/blog/Comments/17/
Jkx
Hum .. perhaps it's time to switch to a real VPN solution not a tcp tunneling ? The best part is that you will have some better performance without the gateway overhead.