Network Address Translation (NAT) is the process where a network device, usually a firewall, assigns a public address to a computer (or group of computers) inside a private network. The main use of NAT is to limit the number of public IP addresses an organization or company must use, for both economy and security purposes.

The most common form of network translation involves a large private network using addresses in a private range (10.0.0.0 to 10.255.255.255, 172.16.0.0 to 172.31.255.255, or 192.168.0 0 to 192.168.255.255). The private addressing scheme works well for computers that only have to access resources inside the network, like workstations needing access to file servers and printers.
Routers inside the private network can route traffic between private addresses with no trouble. However, to access resources outside the network, like the Internet, these computers have to have a public address in order for responses to their requests to return to them. This is where NAT comes into play.

There are many ways how to traverse NAT and if you are interested, here is the link to provide you with the explanation: 


OriginTrail nodes are using Diglet reverse HTTPS tunneling.
Diglet is an fully encrypted reverse HTTPS tunnel server and client. It
enables you to securely make any HTTP(S) server running behind a restrictive
NAT or firewall accessible from the internet. 

We have setup our Diglet to help you overcome the NAT issue easier but you can always set up your own. Here is the link where you can find the explanation on how to do it: 

Please keep in mind that OriginTrail development team is not providing support with any NAT / Diglet - related issues. The Diglet(s) made available by the team are provided as is, for convenience and should not be counted upon in production environments.




Did this answer your question?