Requesting a block: Difference between revisions

From 44Net Wiki
Jump to navigation Jump to search
← Older edit
No edit summary
No edit summary
 
(19 intermediate revisions by 3 users not shown)
Line 1: Line 1:
You '''must''' request an amprnet block direct from the Portal.
'''ARDC/44net'''
 
You '''must''' request an assignment direct from the Portal.
First you must create your account at the [https://portal.ampr.org/ Portal].
First you must create your account at the [https://portal.ampr.org/ Portal].
Once you do, you must login.  
Once you do, you must login. <br>
 
* '''You also must login every 3-6 months even if it's just to check in to keep your assignment active, you have been warned!'''


Once logged in, from the '''top''' home tab, you next select the [https://portal.ampr.org/networks.php Networks]tab on the
Once logged in, from the '''top''' home tab, you next select the [https://portal.ampr.org/networks.php Networks]tab on the
row below. You will see a listing of blocks pre-allocated to the
row below. You will see a listing of subnets.
people who coordinate for those blocks. Find the country you are
 
from and click on the block to the left that's associated with
In most cases you should then click on the 44.0.0.0/9 NO COUNTRY option (second from the top)
the place you live in. If you're in the United States, than
 
you would first select 44.0.0.0/9, and then search for the state
Next you need to select the subnet most appropriate to your use case:
you live in and click on that block assignment to the left.
 
* If you want to join the IPIP Tunnel Mesh, AKA AMPRNet, then select 44.63.0.0/16
* For standalone use / anything else, please select 44.61.0.0/16
* If you want a BGP announced assignment then please select 44.31.0.0/16
 
After you have clicked on the network of choice, scroll to the bottom of the subsequent page where you will see the message:
 
'''"If the address range you want is not within any of the subnets above, or the region you are located in is not listed above, you may request an allocation from the parent network by clicking here:"'''


Once you find the block associated with your QTH, you then click  
Go ahead and click on the link to the right of this message, this will display a request form for you to complete:
on that block. When it opens you'll see a listing of pre-allocated
IP space for that block assigned by that area's coordinator. You
will also notice the following:
"If the address range you want is not within any of the subnets above, or the region you are located in is not listed above, you may request an allocation from the parent network by clicking here: x.x.x.x/16"
This will open up a new screen. This will bring you to the "Request Allocation" page.


Your origin's subnet will automatically be selected as a /16 subnet however
* Choose the size of subnet you would like to request from the dropdown "Netmask requested". Don't be '''greedy''' please only request what you will realistically use within 6 to 12 months (you can always request a larger assignment if your project takes off and you find you need more IPs later on).
you need to enter in the actual subnet below it in which would suit your
needs. Don't be '''greedy''' request what you actually need for service
nodes. This would not include any 802.11 routers for use on ''HamWan/HamNet'' as
doing so would make you quite insecure. ISPs don't configure their routers
with publicly routable IP space for end users, why would you? To start with, I suggest
a /29 or if you feel you have a handful of devices such as a dozen Raspberry Pi
units you wish to host [http://wiki.ampr.org/index.php/URONode Nodes] with a /28
may better suit your needs.


Basic space allocation per block request and usable hosts within such as a quick
* In the "Description" field enter a short description of the network if it is assigned - generally your callsign is a good choice here, remember it will be public.
guideline would be:
*/32 - 1 usable host
*/30 - 2 usable hosts
*/29 - 6 usable hosts
*/28 - 14 usable hosts
*/27 - 30 usable hosts


Plan out your topology accordinly before you request your subnet. Many devices may share IPs for
* Leave the "Type" field set to "User" unless you have been instructed to do otherwise.
the services you might plan to host on them. An example for a full service [http://wiki.ampr.org/index.php/URONode Node]
you may have 44.1.2.3.4 and that may bind to such things as:
*SMTP/[http://wiki.ampr.org/index.php/URONode axMail]
*[http://wiki.ampr.org/index.php/URONode Node]
*APRS
*BBS
*IMAP
*POP3
*HTTP/HTTPS
*and more!
All the above services may use a single IP on 1 host as these each may use 1 IP port each on the same IP address. As an example
if you had 4 Raspberry Pi units, and 4 PCs you were going to deploy out, that'd be 8 individual devices
in which you'd want a /28 subnet for because a /29 would leave you short 2 IPs for the host devices.


In the description field, I suggest you enter your callsign. It makes your subnet easier to locate in the portal.
* In the "Connection Details" section tick the appropriate option(s) for your request. Most folk can ignore the third option "Direct (BGP)" unless you understand what this represents (announcing the subnet direct on the internet).


Type will always be: '''End User'''
* In the "Notes" field you an enter any information you feel is relevant to your request, any information you feel would make the coordinators job easier when evaluating your request.


Underneath that will be 3 tick boxes:
Finally click the "Send" button and wait !
*Radio
*Tunnel
*[http://wiki.ampr.org/index.php/Announcing_your_allocation_directly Direct]
Unless you're jumping right into the fire and intend on BGP announcing your subnet,
you can ignore the last one otherwise click on the link above to see how to do BGP with the AmprNet.
If you'll be routing IP via RF you'll obviously want to tick on ''Radio''. If you'll have IP
connectivity via your ISP you'll want to also tick on ''Tunnel''. Note: Not all ISPs allow for the
passing of our tunnel protocol however most do. If you find you can not tunnel, check with your router's
manufacturer to insure they allow for passing of IP protocol 4. You may also want to place your main amprnet
device's lan IP into your local router's DMZ so that anything coming into your IP will default
route into the device you'll designate as your amprnet routing device. (Note: Raspberry Pi
units are a great device for this and you can turn them into a Wifi hotspot to route 44/8
via 802.11a/b/g/n)


Lastly you'll want to send a note to your coordinator. You'll find this to be a good way to
Please bear in mind that the people who process these requests are volunteers and as such your request may not get looked at immediately, please be patient. If you haven't had an initial contact within 3 or 4 weeks then feel free to email postmaster [at] ardc.net explaining the issue (or use the contact-us form on the portal).
open communications with your coordinator as well as helping them sort out your needs for a
subnet.


Your next step is [http://wiki.ampr.org/wiki/Registering_Your_Gateway Here] to register your AmprNet Gateway.
If you are planning on connecting to the IPIP TunnelMesh, AKA AMPRNet, your next step is [https://wiki.ampr.org/wiki/Registering_Your_Gateway Here] to register your Gateway.

Latest revision as of 16:35, 1 December 2023

ARDC/44net

You must request an assignment direct from the Portal. First you must create your account at the Portal. Once you do, you must login.

  • You also must login every 3-6 months even if it's just to check in to keep your assignment active, you have been warned!

Once logged in, from the top home tab, you next select the Networkstab on the row below. You will see a listing of subnets.

In most cases you should then click on the 44.0.0.0/9 NO COUNTRY option (second from the top)

Next you need to select the subnet most appropriate to your use case:

  • If you want to join the IPIP Tunnel Mesh, AKA AMPRNet, then select 44.63.0.0/16
  • For standalone use / anything else, please select 44.61.0.0/16
  • If you want a BGP announced assignment then please select 44.31.0.0/16

After you have clicked on the network of choice, scroll to the bottom of the subsequent page where you will see the message:

"If the address range you want is not within any of the subnets above, or the region you are located in is not listed above, you may request an allocation from the parent network by clicking here:"

Go ahead and click on the link to the right of this message, this will display a request form for you to complete:

  • Choose the size of subnet you would like to request from the dropdown "Netmask requested". Don't be greedy please only request what you will realistically use within 6 to 12 months (you can always request a larger assignment if your project takes off and you find you need more IPs later on).
  • In the "Description" field enter a short description of the network if it is assigned - generally your callsign is a good choice here, remember it will be public.
  • Leave the "Type" field set to "User" unless you have been instructed to do otherwise.
  • In the "Connection Details" section tick the appropriate option(s) for your request. Most folk can ignore the third option "Direct (BGP)" unless you understand what this represents (announcing the subnet direct on the internet).
  • In the "Notes" field you an enter any information you feel is relevant to your request, any information you feel would make the coordinators job easier when evaluating your request.

Finally click the "Send" button and wait !

Please bear in mind that the people who process these requests are volunteers and as such your request may not get looked at immediately, please be patient. If you haven't had an initial contact within 3 or 4 weeks then feel free to email postmaster [at] ardc.net explaining the issue (or use the contact-us form on the portal).

If you are planning on connecting to the IPIP TunnelMesh, AKA AMPRNet, your next step is Here to register your Gateway.

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