Gateway: Difference between revisions

From 44Net Wiki
Jump to navigation Jump to search
No edit summary
(Suggestions from KC8QBA re AMPRGW, and light edits for formatting and grammar)
 
(7 intermediate revisions by 4 users not shown)
Line 1: Line 1:
A lot of the 44/8 address space is interconnected via [[gateway|gateways]]. These are IPIP encapsulated [[tunnel|tunnels]] that carry the 44/8 address space allocated to a particular region or end user. There exists a database of all the gateways public IP addresses and the subnets they service on the [[portal]]. This database is used to dynamically generate gateway information via modified [[RIP]] advertisements. This database also generates a file called [[encap.txt]] which is basically a routing table that specifies which subnets can be reached via which gateway.  
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. 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.


Learn how to [[Setting up a gateway on Linux|setup a Linux 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).


Learn how to [[Setting up a gateway on OpenWRT|setup an OpenWRT gateway]]
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.


In order to keep this database up to date, everyone that operates a gateway must register on the [[portal]] and have their gateway assigned to their account.
Learn how to [[Setting up a gateway on Cisco Routers|set up a  Cisco Router gateway]]


As the portal only went live recently, we are in a transition phase, where all the old gateway entries that existed have been copied into the new database and are awaiting their "owners" to claim them. After a suitable period of time has elapsed, about a year, any unclaimed gateways will be removed from the system, thus ensuring that the database is as up to date and as accurate as possible. It is therefore important to register and claim your gateway asap!
Learn how to [[Setting up a gateway on Linux|set up a Linux gateway]]
 
Learn how to [[setting up a gateway on MikroTik Routers|set up a gateway on MikroTik Routers]]
 
Learn how to [[Setting up a gateway on OpenBSD|set up an OpenBSD gateway]]
 
Learn how to [[Setting up a gateway on OpenWRT|set up an OpenWRT gateway]]

Latest revision as of 12:02, 4 May 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. 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

Retrieved from "https://wiki.ampr.org/w/index.php?title=Gateway&oldid=1107"