Approving Small Subnets on the Portal - Revision history

KI5QKX: mw push

2026-03-01T00:14:25Z

mw push

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

	[[Category:Portal Administration]]		[[Category:Portal Administration]]
			[[Category:Portal]]
			[[Category:Portal Workflows]]

KI5QKX: mw push

2026-02-28T23:20:11Z

mw push

← Older revision		Revision as of 23:20, 28 February 2026
Line 1:		Line 1:
	== DRAFT - ~~In Progress~~ ==		== DRAFT - in progress ==

	== Allocation ==		== Allocation ==
	'''How to Approve Small Subnets'''		'''How to Approve Small Subnets'''

	== Claim the ~~Ticket~~ ==		== Claim the ticket ==

	* Click “'''Preview'''”		* Click “'''Preview'''”
	* Click “'''Take Ownership'''”		* Click “'''Take Ownership'''”

	== Verify ~~Request~~ ==		== Verify request ==

	* Based on the request, determine if the user is requesting enough or too many IPs		* Based on the request, determine if the user is requesting enough or too many IPs
Line 19:		Line 19:
	* If the request is for a /28 or less, then accept the request without asking questions about intended usage		* If the request is for a /28 or less, then accept the request without asking questions about intended usage

	* If the request is for non IPIP ~~mesh~~, verify that they understand that the IP’s will not be Internet usable. If they want Internet reachability, ask them to open an IPIP Mesh or a BGP ticket.		* If the request is for non IPIP Mesh, verify that they understand that the IP’s will not be Internet usable. If they want Internet reachability, ask them to open an IPIP Mesh or a BGP ticket.

	* For any requests for a /27+ (32+ IP’s), ask what they plan on using them for. Any sort of networking setup will be an ok answer. Simply find out if they have a plan or aspirations. Examples include inter radio connection, local RFC1918, many IPIP ~~mesh~~ connections, etc. Gently suggest smaller allocations if it sounds like that option would be a better fit. If the request is larger (/26+), remind them that they can always ask for more IP’s as their project grows. Giving a /25 or less worth of IP’s should be done liberally.<br>		* For any requests for a /27+ (32+ IP’s), ask what they plan on using them for. Any sort of networking setup will be an ok answer. Simply find out if they have a plan or aspirations. Examples include inter radio connection, local RFC1918, many IPIP Mesh connections, etc. Gently suggest smaller allocations if it sounds like that option would be a better fit. If the request is larger (/26+), remind them that they can always ask for more IP’s as their project grows. Giving a /25 or less worth of IP’s should be done liberally.<br>
	Be excited for the user, and freely give IP’s. If it sounds like they might need help with using IP’s, offer suggestions and direct them to the mailing lists for discussions.		Be excited for the user, and freely give IP’s. If it sounds like they might need help with using IP’s, offer suggestions and direct them to the mailing lists for discussions.

	== Approve ~~Request~~ ==		== Approve request ==

	* Click “'''Accept'''”		* Click “'''Accept'''”

	== Find ~~Last Prefix~~ in ~~Parent Range~~ ==		== Find last prefix in parent range ==

	* Next, you will need to look at the IP list and subnet the next available prefix size within the parent network that they are requesting. This will require subnet math (see Subnet section)		* Next, you will need to look at the IP list and subnet the next available prefix size within the parent network that they are requesting. This will require subnet math (see Subnet section)
Line 47:		Line 47:
	*** '''/25''': add 128 to the last IP number (126 usable)		*** '''/25''': add 128 to the last IP number (126 usable)

	== Add ~~Subnet~~ to ~~Assignment Request~~ ==		== Add subnet to assignment request ==

	* In this example, the next /32 would be 44.63.0.74/32		* In this example, the next /32 would be 44.63.0.74/32

KI5QKX: Add portal administration category

2024-12-11T18:34:35Z

Add portal administration category

← Older revision		Revision as of 18:34, 11 December 2024
Line 60:		Line 60:
	** If this is the case, have the user request address verification		** If this is the case, have the user request address verification
	** Once address verification has been completed, you will be able to complete the ticket and add more IP’s to their profile.		** Once address verification has been completed, you will be able to complete the ticket and add more IP’s to their profile.

			[[Category:Portal Administration]]

KO4KVG: /* Complications */

2024-11-08T22:20:04Z

Complications

← Older revision		Revision as of 22:20, 8 November 2024
Line 56:		Line 56:

	== Complications ==		== Complications ==

			* If for any reason the approval gets denied, it's most likely due to a user having been already allocated more than a /25 without doing address verification
			** If this is the case, have the user request address verification
			** Once address verification has been completed, you will be able to complete the ticket and add more IP’s to their profile.

KO4KVG: /* Add Subnet to Assignment Request */

2024-11-08T22:19:02Z

Add Subnet to Assignment Request

← Older revision		Revision as of 22:19, 8 November 2024
Line 48:		Line 48:

	== Add Subnet to Assignment Request ==		== Add Subnet to Assignment Request ==

			* In this example, the next /32 would be 44.63.0.74/32

			* Enter prefix into the “'''Network'''” field

			* If during the discussion they need more or fewer IP’s, you can adjust this by changing the “Size” field. If you change the size, go back to network list and find last IP in that network size and do the necessary Subnet math. Enter the answer into the “'''Network'''” field.

	== Complications ==		== Complications ==

KO4KVG: /* Subnet */

2024-11-08T22:18:10Z

Subnet

← Older revision		Revision as of 22:18, 8 November 2024
Line 35:		Line 35:

	== Subnet ==		== Subnet ==

			* '''Subnet Math'''
			** For:
			*** '''/32''': give the next IP number in range (1 usable)
			*** '''/31''': add 2 to the last IP number
			*** '''/30''': add 4 to the last IP number (2 usable)
			*** '''/29''': add 8 to the last IP number (6 usable)
			*** '''/28''': add 16 to the last IP number (14 usable)
			*** '''/27''': add 32 to the last IP number (30 usable)
			*** '''/26''': add 64 to the last IP number (62 usable)
			*** '''/25''': add 128 to the last IP number (126 usable)

	== Add Subnet to Assignment Request ==		== Add Subnet to Assignment Request ==

	== Complications ==		== Complications ==

KO4KVG: /* Find Last Prefix in Parent Range */

2024-11-08T22:15:11Z

Find Last Prefix in Parent Range

← Older revision		Revision as of 22:15, 8 November 2024
Line 29:		Line 29:

	== Find Last Prefix in Parent Range ==		== Find Last Prefix in Parent Range ==

			* Next, you will need to look at the IP list and subnet the next available prefix size within the parent network that they are requesting. This will require subnet math (see Subnet section)

			* In a separate browser window, open the Network list in top menu bar: "'''Networks > All IPv4 networks'''"

	== Subnet ==		== Subnet ==

KO4KVG: /* Approve Request */

2024-11-08T22:11:36Z

Approve Request

← Older revision		Revision as of 22:11, 8 November 2024
Line 25:		Line 25:

	== Approve Request ==		== Approve Request ==

			* Click “'''Accept'''”

	== Find Last Prefix in Parent Range ==		== Find Last Prefix in Parent Range ==

KO4KVG: /* Verify Request */

2024-11-08T22:10:40Z

Verify Request

← Older revision		Revision as of 22:10, 8 November 2024
Line 10:		Line 10:

	== Verify Request ==		== Verify Request ==

			* Based on the request, determine if the user is requesting enough or too many IPs

			* If they want a General Allocation and are requesting a single /32, find out how they intend on using the IP since a single IP isn’t enough. Give guidance to move them into a large enough subnet size for their intended usage.

			* If the IPs are to be used for interlinks, suggest that they request at least a /30 (2 usable IP’s)

			* If the request is for a /28 or less, then accept the request without asking questions about intended usage

			* If the request is for non IPIP mesh, verify that they understand that the IP’s will not be Internet usable. If they want Internet reachability, ask them to open an IPIP Mesh or a BGP ticket.

			* For any requests for a /27+ (32+ IP’s), ask what they plan on using them for. Any sort of networking setup will be an ok answer. Simply find out if they have a plan or aspirations. Examples include inter radio connection, local RFC1918, many IPIP mesh connections, etc. Gently suggest smaller allocations if it sounds like that option would be a better fit. If the request is larger (/26+), remind them that they can always ask for more IP’s as their project grows. Giving a /25 or less worth of IP’s should be done liberally.<br>
			Be excited for the user, and freely give IP’s. If it sounds like they might need help with using IP’s, offer suggestions and direct them to the mailing lists for discussions.

	== Approve Request ==		== Approve Request ==

KO4KVG: /* Claim the Ticket */

2024-11-08T21:57:15Z

Claim the Ticket

← Older revision		Revision as of 21:57, 8 November 2024
Line 5:		Line 5:

	== Claim the Ticket ==		== Claim the Ticket ==

			* Click “'''Preview'''”
			* Click “'''Take Ownership'''”

	== Verify Request ==		== Verify Request ==