Gateway: Difference between revisions
Suggestions from KC8QBA re AMPRGW, and light edits for formatting and grammar |
No edit summary |
||
| Line 1: | Line 1: | ||
Much of the AMPRNet address space is interconnected via [[gateway|gateways]] that implement IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) encapsulated [[tunnel|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. | Much of the AMPRNet address space is interconnected via [[gateway|gateways]] that implement IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) encapsulated [[tunnel|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. | ||
The [[portal]] maintains a database of all the gateways, their public IP addresses, and the subnets they serve. | |||
This routing information is distributed via modified [[RIP]] advertisements. | |||
A complete list of gateways can be downloaded from the [[API|portal API]]. | |||
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 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). | ||
Latest revision as of 04:16, 15 October 2024
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. The portal maintains a database of all the gateways, their public IP addresses, and the subnets they serve. This routing information is distributed via modified RIP advertisements. A complete list of gateways can be downloaded from the portal API.
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