<div dir="ltr"><div><div><div><div><div>Update ::<br><br></div>Seems some issue at the level of ssh-tunneling itself.<br><br><br></div>On Machine-1, following works (as already stated) ::<br> wget localhost:9001/1.txt<br><br></div>but following does not ::<br></div> wget <a href="http://1.2.3.4:9001/1.txt">1.2.3.4:9001/1.txt</a><br><br><br><br></div><div>Also, doing netstat -an on Machine-1 shows the following ::<br><br>root@proxy:~# netstat -an | grep LISTEN<br>tcp 0 0 <a href="http://127.0.0.1:9001">127.0.0.1:9001</a> 0.0.0.0:* LISTEN <br>tcp 0 0 <a href="http://0.0.0.0:22">0.0.0.0:22</a> 0.0.0.0:* LISTEN <br>tcp6 0 0 ::1:9001 :::* LISTEN <br>tcp6 0 0 :::22 :::* LISTEN <br></div><div><br><br></div><div>Seems ssh-reverse-tunnelling just allows tunnelling on the localhost-loopback :(<br><br></div>Investigating ....<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Mar 25, 2017 at 6:53 PM, Ajay Garg <span dir="ltr"><<a href="mailto:ajaygargnsit@gmail.com" target="_blank">ajaygargnsit@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div><div><div><div><div><div>Thanks Eric for the help ... SSH (reverse-)tunnelling is indeed the way to go.<br></div>However, I am stuck at the last mile (at FIrefox level it seems).<br><br><br></div>Following is what I have done.<br><br></div>Architecture is<br><br></div> Machine-1 <==> Machine-2 <==> Machine-3.<br><br></div>* Let Machine-1 public-IP be 1.2.3.4<br></div>* Let Machine-3 local IP be 5.6.7.8<br></div>* Machine-1 and Machine-3 are both accessible from Machine-2.<br><br><br></div><div>a)<br></div><div>Machine-3 has a local http-server running, with a resource localhost/1.txt accessible.<br><br></div><div>b)<br></div>I did the following on Machine-2 ::<br><br></div> ssh -R 9001:<a href="http://5.6.7.8:80" target="_blank">5.6.7.8:80</a> 1.2.3.4<br><br></div>c)<br></div>Thereafter, following works perfect on Machine-1 ::<br><br></div> wget localhost:9001/1.txt<br><br></div>with the resource 1.txt being identical with the one in step a)<br><br><br><br></div>However, if I use a machine say Machine-4, and enter the URL ::<br><br></div><div> <a href="http://1.2.3.4:9001/1.txt" target="_blank">1.2.3.4:9001/1.txt</a><br><br></div><div>it says failed to connect.<br><br><br></div><div>I am guessing something needs to be done in about:config of firefox on Machine-4.<br></div><div>Am I correct? If yes, what exactly needs to be changed in the config?<br><br><br></div><div>Thanks already for your help, will be great to receive some advice on this last issue.<br><br><br></div><div>Thanks and Regards,<br></div><div>Ajay<br></div><div><br></div> <br><div><div><div><div><div><div><br></div></div></div></div></div></div></div><div class="gmail_extra"><div><div class="h5"><br><div class="gmail_quote">On Sat, Mar 25, 2017 at 3:22 AM, Eric Rescorla <span dir="ltr"><<a href="mailto:ekr@rtfm.com" target="_blank">ekr@rtfm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>To the best of my knowledge, there is no way to do this.</div><div><br></div><div>Generally, if you want to do something like this, you set up an SSH tunnel or the like.</div><div><br></div><div>-Ekr</div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="m_-7551856789150375572h5">On Fri, Mar 24, 2017 at 12:53 AM, Ajay Garg <span dir="ltr"><<a href="mailto:ajaygargnsit@gmail.com" target="_blank">ajaygargnsit@gmail.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="m_-7551856789150375572h5"><div dir="ltr"><div><div><div><div><div><div><div><div><div><div>Hi All.<br><br></div>I am wishing to communicate between Machine-1 and Machine-2.<br><br></div>Machine-1 has a public-IP, whereas Machine-2 does not.<br></div>Machine-1 is the client, while Machine-2 runs a web-server.<br><br></div>So, a normal <a href="http://Machine-2/path/to/stuff" target="_blank">http://Machine-2/path/to/stuff</a> cannot be used from a browser in Machine-1, because Machine-2 does not have a public-IP.<br></div>But, a normal TCP socket can be created *from* Machine-2, using Machine-1's public IP.<br><br></div>So, can this socket be somehow passed to firefox on Machine-1?<br></div>This way, firefox DOES NOT create the initiating TCP-connection (instead using the passed socket), and thereafter begins passing/receiving the HTTP requests/responses as usual.<br><br><br></div>Do I make sense in my query?<br></div>If yes, is it possible of what we desire?<br><br><br></div>Will be great to listen back from the experts !!<br clear="all"><div><div><div><div><div><div><div><div><div><div><div><br><br><div class="m_-7551856789150375572m_-3768664140994710326m_-5198180838075533986gmail_signature" data-smartmail="gmail_signature">Thanks and Regards,<br>Ajay<br></div>
</div></div></div></div></div></div></div></div></div></div></div></div>
<br></div></div>______________________________<wbr>_________________<br>
firefox-dev mailing list<br>
<a href="mailto:firefox-dev@mozilla.org" target="_blank">firefox-dev@mozilla.org</a><br>
<a href="https://mail.mozilla.org/listinfo/firefox-dev" rel="noreferrer" target="_blank">https://mail.mozilla.org/listi<wbr>nfo/firefox-dev</a><br>
<br></blockquote></div><br></div>
</blockquote></div><br><br clear="all"><br></div></div><span class="HOEnZb"><font color="#888888">-- <br><div class="m_-7551856789150375572gmail_signature" data-smartmail="gmail_signature">Regards,<br>Ajay<br></div>
</font></span></div>
</blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">Regards,<br>Ajay<br></div>
</div>