Gateway - Revision history

KI5QKX: mw push

2026-04-30T18:52:39Z

mw push

← Older revision		Revision as of 18:52, 30 April 2026
Line 17:		Line 17:

	Learn how to [[Setting up a gateway on OpenWRT\|set up an OpenWRT gateway]]		Learn how to [[Setting up a gateway on OpenWRT\|set up an OpenWRT gateway]]


	[[Category:Reference]]		[[Category:Reference]]
	[[Category:Infrastructure]]		[[Category:Infrastructure]]
	[[Category:Gateways]]		[[Category:Gateways]]

KI5QKX: mw push

2026-03-01T00:14:36Z

mw push

← Older revision		Revision as of 00:14, 1 March 2026
Line 20:		Line 20:

	[[Category:Reference]]		[[Category:Reference]]
			[[Category:Infrastructure]]
			[[Category:Gateways]]

KI5QKX: mw push

2026-02-28T23:20:22Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
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.		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.		This routing information is distributed via modified [[RIP]] advertisements.
	A complete list of gateways can be downloaded from the [[API\|~~portal~~ API]].		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).

	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 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.

KI5QKX at 20:28, 12 December 2024

2024-12-12T20:28:25Z

← Older revision		Revision as of 20:28, 12 December 2024
Line 17:		Line 17:

	Learn how to [[Setting up a gateway on OpenWRT\|set up an OpenWRT gateway]]		Learn how to [[Setting up a gateway on OpenWRT\|set up an OpenWRT gateway]]


			[[Category:Reference]]

W6JMK at 04:16, 15 October 2024

2024-10-15T04:16:22Z

← Older revision		Revision as of 04:16, 15 October 2024
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. ~~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~~.		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).

Cross: Suggestions from KC8QBA re AMPRGW, and light edits for formatting and grammar

2024-05-04T12:02:04Z

Suggestions from KC8QBA re AMPRGW, and light edits for formatting and grammar

← Older revision		Revision as of 12:02, 4 May 2024
Line 1:		Line 1:
	~~A lot~~ of the AMPRNet address space is interconnected via [[gateway\|gateways]]~~. These are~~ IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) encapsulated [[tunnel\|tunnels]] ~~that carry~~ the AMPRNet 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 MikroTik Routers\|setting up a gateway on MikroTik Routers~~]]		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 [[Setting up a gateway on ~~OpenWRT~~\|~~setup an OpenWRT~~ gateway]]		Learn how to [[Setting up a gateway on Cisco Routers\|set up a Cisco Router gateway]]

	Learn how to [[Setting up a gateway on ~~Cisco Routers~~\|~~setup~~ a ~~Cisco Router~~ gateway]]		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]]

	~~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 OpenWRT\|set up an OpenWRT gateway]]

W9OQI at 19:53, 8 November 2023

2023-11-08T19:53:29Z

← Older revision		Revision as of 19:53, 8 November 2023
Line 2:		Line 2:

	Learn how to [[Setting up a gateway on Linux\|setup a Linux gateway]]		Learn how to [[Setting up a gateway on Linux\|setup a Linux gateway]]

			Learn how to [[setting up a gateway on MikroTik Routers\|setting up a gateway on MikroTik Routers]]

	Learn how to [[Setting up a gateway on OpenWRT\|setup an OpenWRT gateway]]		Learn how to [[Setting up a gateway on OpenWRT\|setup an OpenWRT gateway]]
Line 7:		Line 9:
	Learn how to [[Setting up a gateway on Cisco Routers\|setup a Cisco Router gateway]]		Learn how to [[Setting up a gateway on Cisco Routers\|setup a Cisco Router gateway]]

	~~Learn how to [[setting up a gateway on MikroTik Routers\|setting up a gateway on MikroTik Routers]]~~

	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.		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.

WB6CYT at 11:42, 25 July 2019

2019-07-25T11:42:53Z

← Older revision		Revision as of 11:42, 25 July 2019
Line 1:		Line 1:
	A lot of the ~~44/8~~ address space is interconnected via [[gateway\|gateways]]. These are IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) encapsulated [[tunnel\|tunnels]] that carry the AMPRNet 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.		A lot of the AMPRNet address space is interconnected via [[gateway\|gateways]]. These are IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) encapsulated [[tunnel\|tunnels]] that carry the AMPRNet 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.

	Learn how to [[Setting up a gateway on Linux\|setup a Linux gateway]]		Learn how to [[Setting up a gateway on Linux\|setup a Linux gateway]]

WB6CYT at 11:38, 25 July 2019

2019-07-25T11:38:22Z

← Older revision		Revision as of 11:38, 25 July 2019
Line 1:		Line 1:
	A lot of the 44/8 address space is interconnected via [[gateway\|gateways]]. These are IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) 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.		A lot of the 44/8 address space is interconnected via [[gateway\|gateways]]. These are IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) encapsulated [[tunnel\|tunnels]] that carry the AMPRNet 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.

	Learn how to [[Setting up a gateway on Linux\|setup a Linux gateway]]		Learn how to [[Setting up a gateway on Linux\|setup a Linux gateway]]
Line 10:		Line 10:

	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.		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.

	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!

Kb3vwg at 00:49, 18 February 2017

2017-02-18T00:49:07Z

← Older revision		Revision as of 00:49, 18 February 2017
Line 1:		Line 1:
	A lot of the 44/8 address space is interconnected via [[gateway\|gateways]]. These are IPENCAP (IP Protocol Number 4) 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.		A lot of the 44/8 address space is interconnected via [[gateway\|gateways]]. These are IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) 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.

	Learn how to [[Setting up a gateway on Linux\|setup a Linux gateway]]		Learn how to [[Setting up a gateway on Linux\|setup a Linux gateway]]

← Older revision		Revision as of 12:02, 4 May 2024
Line 1:		Line 1:
	~~A lot~~ of the AMPRNet address space is interconnected via [[gateway\|gateways]]~~. These are~~ IPENCAP ([http://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml IP Protocol Number 4]) encapsulated [[tunnel\|tunnels]] ~~that carry~~ the AMPRNet 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 MikroTik Routers\|setting up a gateway on MikroTik Routers~~]]		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 [[Setting up a gateway on ~~OpenWRT~~\|~~setup an OpenWRT~~ gateway]]		Learn how to [[Setting up a gateway on Cisco Routers\|set up a Cisco Router gateway]]

	Learn how to [[Setting up a gateway on ~~Cisco Routers~~\|~~setup~~ a ~~Cisco Router~~ gateway]]		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]]

	~~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 OpenWRT\|set up an OpenWRT gateway]]