Encap.txt - Revision history

KI5QKX: mw push

2026-03-01T00:14:24Z

mw push

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

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

KI5QKX: mw push

2026-02-28T23:20:10Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
Line 23:		Line 23:
	== HTTP ==		== HTTP ==

	Previously, a complete encap.txt file was available from the ~~portal~~ as a web page.		Previously, a complete encap.txt file was available from the Portal as a web page.
	This is no longer supported.		This is no longer supported.

	[[Category:Reference]]		[[Category:Reference]]

KI5QKX at 20:26, 12 December 2024

2024-12-12T20:26:44Z

← Older revision		Revision as of 20:26, 12 December 2024
Line 25:		Line 25:
	Previously, a complete encap.txt file was available from the portal as a web page.		Previously, a complete encap.txt file was available from the portal as a web page.
	This is no longer supported.		This is no longer supported.

			[[Category:Reference]]

W6JMK: add links

2024-10-15T18:27:09Z

add links

← Older revision		Revision as of 18:27, 15 October 2024
Line 1:		Line 1:
	An encap.txt file lists ~~AMPRNet~~ [[~~gateway~~\| gateways]], in a format like this:		An encap.txt file lists [[Gateway\|AMPRNet gateways]], in a format like this:

	<nowiki># This is a comment		<nowiki># This is a comment
Line 10:		Line 10:

	To get an encap.txt file that lists all current gateways,		To get an encap.txt file that lists all current gateways,
	request all routes from the [[API]] and convert the response from JSON to text.		request all routes from the [[API\|Portal API]] and convert the response from JSON to text.
	For example (using API version 2):		For example (using [[API]] version 2):

	<nowiki>curl -s -H "Authorization: Bearer $APItoken" -H "Accept: application/json" https://portal.ampr.org/api/v2/encap/routes \| jq -r '.encap[] \| select(.encapType == "IPIP") \| "route addprivate \(.network)/\(.cidr) encap \(.gatewayIP)"'</nowiki>		<nowiki>curl -s -H "Authorization: Bearer $APItoken" -H "Accept: application/json" https://portal.ampr.org/api/v2/encap/routes \| jq -r '.encap[] \| select(.encapType == "IPIP") \| "route addprivate \(.network)/\(.cidr) encap \(.gatewayIP)"'</nowiki>

	A more complete example is in [[~~encap~~.txt/get-encap]].		A more complete example is in [[Encap.txt/get-encap]].

	If something goes wrong, the result won't be a complete list.		If something goes wrong, the result won't be a complete list.

W6JMK: Recommend validating a response from the API.

2024-10-15T03:08:57Z

Recommend validating a response from the API.

← Older revision		Revision as of 03:08, 15 October 2024
Line 14:		Line 14:

	<nowiki>curl -s -H "Authorization: Bearer $APItoken" -H "Accept: application/json" https://portal.ampr.org/api/v2/encap/routes \| jq -r '.encap[] \| select(.encapType == "IPIP") \| "route addprivate \(.network)/\(.cidr) encap \(.gatewayIP)"'</nowiki>		<nowiki>curl -s -H "Authorization: Bearer $APItoken" -H "Accept: application/json" https://portal.ampr.org/api/v2/encap/routes \| jq -r '.encap[] \| select(.encapType == "IPIP") \| "route addprivate \(.network)/\(.cidr) encap \(.gatewayIP)"'</nowiki>

			A more complete example is in [[encap.txt/get-encap]].

			If something goes wrong, the result won't be a complete list.
			Before using it to update routing tables, it's worth checking whether it has the right syntax and it's reasonably long.
			An empty list or a list that's much shorter than a previous version is probably erroneous.

	== HTTP ==		== HTTP ==

W6JMK: Use the API to get all routes. The portal doesn't provide an encap.txt file via HTTP.

2024-10-15T01:38:47Z

Use the API to get all routes. The portal doesn't provide an encap.txt file via HTTP.

← Older revision		Revision as of 01:38, 15 October 2024
Line 1:		Line 1:
	~~== The~~ encap.txt file ==		An encap.txt file lists AMPRNet [[gateway\| gateways]], in a format like this:

	~~The~~ encap.~~txt file is a file listing all the AMPRNet [[gateway\| gateways]]~~.		<nowiki># This is a comment
			route addprivate 44.10.0.100/32 encap 136.115.52.224
			route addprivate 44.100.129.0/24 encap 176.140.10.22</nowiki>

	Originally formatted for JNOS systems, it is often parsed with a "[[munge script]]" to update Linux system routing tables.		Originally formatted for JNOS systems, it is often parsed with a "[[munge script]]" to update Linux system routing tables.

	~~The file can be obtained via the [[Portal\| portal]] and private HTTP.~~

	== Portal ==		== Portal ==

	~~You can create~~ an ~~API key on~~ the ~~portal by visiting~~ [~~https://portal.ampr.org/profile.php your profile page~~]~~. Since it needs to be 32 characters I recommend using md5sum of any random data to generate it. The encap endpoint produces json format which you will need to format. You can then use~~ the ~~command line utilities '''curl''' and '''jq''' to turn this data into routes~~ to ~~ingest into about anything~~. For example ~~for JNOS encap.txt format~~:		To get an encap.txt file that lists all current gateways,
			request all routes from the [[API]] and convert the response from JSON to text.
			For example (using API version 2):

	curl -s -H "Authorization: Bearer ~~<Portal API Key>~~" -H "Accept: application/json" https://portal.ampr.org/api/v1/encap/routes \| jq -r '.encap[] \| "route addprivate \(.network)/\(.~~maskLength~~) encap \(.gatewayIP)"'		<nowiki>curl -s -H "Authorization: Bearer $APItoken" -H "Accept: application/json" https://portal.ampr.org/api/v2/encap/routes \| jq -r '.encap[] \| select(.encapType == "IPIP") \| "route addprivate \(.network)/\(.cidr) encap \(.gatewayIP)"'</nowiki>

	== HTTP ==		== HTTP ==

	~~This is still~~ available ~~on private HTTP but it is deprecated and also removed~~ from the ~~anonymous FTP~~. ~~44net list members can find the details in the mailman Archive in this thread:~~		Previously, a complete encap.txt file was available from the portal as a web page.
			This is no longer supported.
	~~[https://mailman.ampr.org/mailman/private/44net/2020-January/010633~~.~~html private gateway stats]~~

Vk7sh: Updated for new portal

2024-09-14T12:27:53Z

Updated for new portal

← Older revision		Revision as of 12:27, 14 September 2024
Line 11:		Line 11:
	You can create an API key on the portal by visiting [https://portal.ampr.org/profile.php your profile page]. Since it needs to be 32 characters I recommend using md5sum of any random data to generate it. The encap endpoint produces json format which you will need to format. You can then use the command line utilities '''curl''' and '''jq''' to turn this data into routes to ingest into about anything. For example for JNOS encap.txt format:		You can create an API key on the portal by visiting [https://portal.ampr.org/profile.php your profile page]. Since it needs to be 32 characters I recommend using md5sum of any random data to generate it. The encap endpoint produces json format which you will need to format. You can then use the command line utilities '''curl''' and '''jq''' to turn this data into routes to ingest into about anything. For example for JNOS encap.txt format:

	curl -s https://~~user:key@~~portal.ampr.org/api/v1/encap \| jq -r '.[] \| "route addprivate \(.network)/\(.maskLength) encap \(.gatewayIP)"'		curl -s -H "Authorization: Bearer <Portal API Key>" -H "Accept: application/json" https://portal.ampr.org/api/v1/encap/routes \| jq -r '.encap[] \| "route addprivate \(.network)/\(.maskLength) encap \(.gatewayIP)"'

	== HTTP ==		== HTTP ==

Ki4cuw: provide details on creating encap.txt from portal's json outside

2020-02-08T17:35:41Z

provide details on creating encap.txt from portal's json outside

@@ Line 1: / Line 1: @@
-The Encap.txt file is a file listing all the AMPRNet [gateway| gateways].
+== The encap.txt file ==
 Originally formatted for JNOS systems, it is often parsed with a "[[munge script]]" to update Linux system routing tables.
-The file can be obtain via the [[Portal| portal]], email, or by FTP.
+The file can be obtained via the [[Portal| portal]] and private HTTP.

Njohnson: Created page with "The Encap.txt file is a file listing all the AMPRNet [gateway| gateways]. Originally formatted for JNOS systems, it is often parsed with a "munge script" to update Linux ..."

2014-04-05T03:44:26Z

Created page with "The Encap.txt file is a file listing all the AMPRNet [gateway| gateways]. Originally formatted for JNOS systems, it is often parsed with a "munge script" to update Linux ..."

New page

The Encap.txt file is a file listing all the AMPRNet [gateway| gateways].

Originally formatted for JNOS systems, it is often parsed with a "[[munge script]]" to update Linux system routing tables.

The file can be obtain via the [[Portal| portal]], email, or by FTP.