Gateway

Much of the AMPRNet address space is interconnected via gateways that implement IPENCAP (IP Protocol Number 4) encapsulated tunnels. These tunnels provide endpoints for the AMPRNet address space allocated to a particular region or end user, effectively forming a mesh network of interconnected tunnels between AMPR subnets. There is a database of all the gateways, their public IP addresses, and the subnets they serve on the portal that is used to dynamically generate routing information that is distributed to the set of all gateways via modified RIP advertisements. This database is also regularly copied into a text file called encap.txt which is basically a routing table describing what subnets can be reached via which gateway.

In order to keep this database up to date, everyone that operates a gateway must register on the portal and have their gateway(s) assigned to their account and associated with their allocation(s).

In addition to the gateways operated by users who connect via IPENCAP tunnels, traffic exchanged between the ARMPNet mesh and the public Internet is routed via the Amprgw – please see the Amprgw page for important details on passing traffic between the public Internet and the IPENCAP tunnel mesh.

Learn how to set up a Cisco Router gateway

Learn how to set up a Linux gateway

Learn how to set up a gateway on MikroTik Routers

Learn how to set up an OpenBSD gateway

Learn how to set up an OpenWRT gateway