<div dir="ltr">Hi,<br><br><div class="gmail_quote">On Tue, Dec 8, 2009 at 17:24, Constantine Shulyupin <span dir="ltr"><<a href="mailto:const@linuxdriver.co.il">const@linuxdriver.co.il</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi colleagues,<br>
<br>
I have: servers (HTTP, FTP, RTSP and other) behind firewall and a<br>
client PC. The client wishes to connect to severer. But firewall<br>
doesn't allows him to connect to server.<br>
<br>
The server knows the clients IP and can open a connection.<br>
Unfortunately I can't set up tunneling/VPN on client because of system<br>
administration limitation.<br>
<br>
Theoretically, I can rewrite inetd to make connection to client and<br>
rewrite FTP client to listen for connection from server or code custom<br>
protocol.<br></blockquote><div><br>for simple protocols (http, scp) you can use reverse port forwarding feature of ssh: <br></div><div>Run on the server following:<br>ssh -R 9922:<a href="http://127.0.0.1:22">127.0.0.1:22</a> <a href="mailto:arie@client.somecompany.com">arie@client.somecompany.com</a><br>
<br>Causes ssh to login into <a href="mailto:arie@client.somecompany.com">arie@client.somecompany.com</a>, listen for connections on <br>port 9922 on the remote machine and forward them to <a href="http://127.0.0.1:22">127.0.0.1:22</a> (back <br>
to the server)<br><br>Then you will be able to ssh into the server from the client by ssh'ing into port 9922 on the client.<br><br>--<br>Arie<br><br></div></div></div>