Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Private IP address ranges like 10.x.y.z are, by their very nature, private. You can't do any meaningful resolution unless each node in between the endpoints has rules in place to translate these.</p> <p>Translation is tricky, all the main tools you would use cater for static translation (port forwarding, e.g. where a particular port is forwarded to a particular IP). This is one avenue, but it is a hacky one (it requires you to open lots of ports, procedurally update your router and probably have some sort of broker server to maintain mappings).</p> <p>Alternatively, you could run the isolated networks over a VPN, which would give your endpoints mutual private IPs which you can use to connect to eachother. It would simply be a case of binding to this new address and communicating across the VPN. This would also potentially encrypt your communication over the internet.</p> <p>Other possibilities are to use NAT/TCP punchthrough techniques which can allow traversal, but these are really a patch to a broken network topology (Read up on IPv6 to see how this can be alleviated).</p> <p>Alternatively, you could route all the connections over a proxy, but this will complicate matters compared to a VPN.</p> <hr> <p>To answer the question about hardcoding a rule, port forwarding is the solution here. It will obviously depend on your router configuration for the peer accepting the connection, but this client should have the port target port forwarded to the machine. This will obviously not scale very well and is really shifting to a server/client architecture for one connection! </p> <p>Depending on your hardware, you may be able to forward a range of ports (if a single port cannot be established) and limit the port forwarding to certain incoming connections (the external IPs).</p> <p>Information on port forwarding can be found at <a href="http://portforward.com/" rel="nofollow">http://portforward.com/</a></p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload