44Net Wiki - User contributions [en]

NSP Details

2025-07-16T13:30:40Z

KC8QBA: NSP details required when creating a new provider.

Many Network Service Providers are already listed and have their information pre-populated in the [[Portal|ARDC Portal]]. If you need to create a new Network Service Provider in the portal to announce your allocation, you will need to obtain the following information:

[[File:NSP_Fields.PNG||Screenshot of NSP Provider Details]]

[[Category:Reference]]

Routing your allocation via BGP

2025-07-16T13:26:39Z

KC8QBA:

To announce an allocation of AMPRNet address space directly via your Internet Service Provider (ISP) you will need to:

# Find an ISP or Virtual Private Server (VPS) provider that is capable of announcing an AMPRNet allocation in accordance with the terms of the [https://www.ampr.org/terms-of-service/ AMPRNet Terms of Service and Acceptable Use Agreement]
# Obtain [[NSP Details|technical details]] from your ISP or VPS provider to include the Autonomous System Number (ASN) your provider will use to announce an AMPRNet allocation
# Request an allocation with a size of /24 from the [[Portal|ARDC Portal]] which will prompt you to provide the ASN and other technical details from your ISP or VPS provider
# Upon approval, appropriate entries will be created in the Internet Routing Registry[[#footnote|¹]] and an automated Letter of Authorization will be available for you to download in the [[Portal|ARDC Portal]] if required by your ISP or VPS provider

== Providers Supporting Customers Bringing IPv4 Blocks ==

{| class="wikitable"
|-
! scope = col style = "width:10%" | Provider Name
! scope = col style = "width:22%" | URL
! scope = col style = "width:8%" | Region(s)
! scope = col style = "width:5%" | IPv6 Block Add-Ons
! scope = col | Info
|- style = "vertical-align:top"
! scope = row | Aussie Broadband
| https://www.aussiebroadband.com.au/ || Australia || Yes || Your Internet Service Provider (ISP) must be Aussie Broadband when you apply for your 44Net Direct Allocation. This ensures your application provides the appropriate contact information, plus you are an established Aussie Broadband client. The recommendation is an Aussie Broadband service with the Static IP Address option. Border Gateway Protocol (BGP) Protocol provides the routing of traffic between your network and the Internet. Your address allocation is only propagated to the Internet by Aussie Broadband when your BGP instance has established a session to the Aussie Broadband gateway.

Your application for a Direct Allocation must have been approved before you can submit your BGP application to Aussie Broadband. The BGP application procedure for Aussie Broadband is documented at [https://www.aussiebroadband.com.au/help-centre/internet/how-to-enable-border-gateway-protocol-routing/ How to enable Border Gateway Protocol routing]. Ignore the comment concerning APNIC as this is irrelevant for 44Net allocations. Currently Aussie Broadband does not charge an establishment fee or any operation costs for BGP sessions i.e. this is a zero cost option for your service. Other Australian ISPs may provide various levels of support for BGP but costs and availability for retail customers are not known.

For the BGP protocol your assigned Private AS Number (ASN) will not be created by Aussie Broadband until they receive your LOA (Legitimacy of Address, sometimes referenced as Letter of Authorization, Letter of Authority, etc.). Forward the LOA with a request for assignment of a BGP private AS Number to the Aussie Broadband Network Operations Team.

For Australians, a now dated version of the 44Net application procedure is covered in the Gippsland Gate Radio and Electronics Club, October 2022 issue, AMPRNET article, Page 12 at http://ggrec.org.au/Magazines/202209.pdf

The customer facing and technical support staff for Aussie Broadband retail customers can not resolve BGP related issues. Lodge any problem dockets as a retail customer and if required request the problem be referred to the Network Operations Team.

Aussie Broadband will enable a filter for the transit of traffic within the appropriate address range. The IPv4 Static IP Address option ensures there are no port filters, Carrier NAT, etc. For the Aussie Broadband account they will assign/implement addresses in the form of:
<ul>
<li>IPv6 /64</li>
<li>IPv6 /48</li>
<li>IPv4 An assigned Public, Static IP Address</li>
<li>IPv4 44Net assigned /24</li>
</ul>
|- style = "vertical-align:top"
! scope = row | Free Range Cloud
| https://freerangecloud.com/ || Fremont/CA/US, Ashburn/VA/US || Yes ||
|- style = "vertical-align:top"
! scope = row | Spartan Host
| https://spartanhost.net/ || Seattle/WA/US, Dallas, TX/US || ? ||
|- style = "vertical-align:top"
! scope = row | Virtua Cloud
| https://virtua.cloud/ || Paris/Lille FR, Fremont US || ? || Requires Net-Block in ARIN IRR (AltDB/RadDB not accepted)
|- style = "vertical-align:top"
! scope = row | Vultr
| https://www.vultr.com/ || 16 Worldwide Locations || Yes ||
|}

== Notes ==
¹RPKI entries are not currently available for AMPRNet address space.

[[Category:Reference]]

File:NSP Fields.PNG

2025-07-16T13:25:59Z

KC8QBA: Screenshot of data fields required when creating a new Network Service Provider on the ARDC Portal.

== Summary ==
Screenshot of data fields required when creating a new Network Service Provider on the ARDC Portal.

Routing your allocation via BGP

2025-07-16T13:06:23Z

KC8QBA: Update description of process requesting a BGP allocation on new portal

To announce an allocation of AMPRNet address space directly via your Internet Service Provider (ISP) you will need to:

# Find an ISP or Virtual Private Server (VPS) provider that is capable of announcing an AMPRNet allocation in accordance with the terms of the [https://www.ampr.org/terms-of-service/ AMPRNet Terms of Service and Acceptable Use Agreement]
# Obtain technical details from your ISP or VPS provider to include the Autonomous System Number (ASN) your provider will use to announce an AMPRNet allocation
# Request an allocation with a size of /24 from the [[Portal|ARDC Portal]] which will prompt you to provide the ASN and other technical details from your ISP or VPS provider
# Upon approval, appropriate entries will be created in the Internet Routing Registry[[#footnote|¹]] and an automated Letter of Authorization will be available for you to download in the [[Portal|ARDC Portal]] if required by your ISP or VPS provider

== Providers Supporting Customers Bringing IPv4 Blocks ==

{| class="wikitable"
|-
! scope = col style = "width:10%" | Provider Name
! scope = col style = "width:22%" | URL
! scope = col style = "width:8%" | Region(s)
! scope = col style = "width:5%" | IPv6 Block Add-Ons
! scope = col | Info
|- style = "vertical-align:top"
! scope = row | Aussie Broadband
| https://www.aussiebroadband.com.au/ || Australia || Yes || Your Internet Service Provider (ISP) must be Aussie Broadband when you apply for your 44Net Direct Allocation. This ensures your application provides the appropriate contact information, plus you are an established Aussie Broadband client. The recommendation is an Aussie Broadband service with the Static IP Address option. Border Gateway Protocol (BGP) Protocol provides the routing of traffic between your network and the Internet. Your address allocation is only propagated to the Internet by Aussie Broadband when your BGP instance has established a session to the Aussie Broadband gateway.

Your application for a Direct Allocation must have been approved before you can submit your BGP application to Aussie Broadband. The BGP application procedure for Aussie Broadband is documented at [https://www.aussiebroadband.com.au/help-centre/internet/how-to-enable-border-gateway-protocol-routing/ How to enable Border Gateway Protocol routing]. Ignore the comment concerning APNIC as this is irrelevant for 44Net allocations. Currently Aussie Broadband does not charge an establishment fee or any operation costs for BGP sessions i.e. this is a zero cost option for your service. Other Australian ISPs may provide various levels of support for BGP but costs and availability for retail customers are not known.

For the BGP protocol your assigned Private AS Number (ASN) will not be created by Aussie Broadband until they receive your LOA (Legitimacy of Address, sometimes referenced as Letter of Authorization, Letter of Authority, etc.). Forward the LOA with a request for assignment of a BGP private AS Number to the Aussie Broadband Network Operations Team.

For Australians, a now dated version of the 44Net application procedure is covered in the Gippsland Gate Radio and Electronics Club, October 2022 issue, AMPRNET article, Page 12 at http://ggrec.org.au/Magazines/202209.pdf

The customer facing and technical support staff for Aussie Broadband retail customers can not resolve BGP related issues. Lodge any problem dockets as a retail customer and if required request the problem be referred to the Network Operations Team.

Aussie Broadband will enable a filter for the transit of traffic within the appropriate address range. The IPv4 Static IP Address option ensures there are no port filters, Carrier NAT, etc. For the Aussie Broadband account they will assign/implement addresses in the form of:
<ul>
<li>IPv6 /64</li>
<li>IPv6 /48</li>
<li>IPv4 An assigned Public, Static IP Address</li>
<li>IPv4 44Net assigned /24</li>
</ul>
|- style = "vertical-align:top"
! scope = row | Free Range Cloud
| https://freerangecloud.com/ || Fremont/CA/US, Ashburn/VA/US || Yes ||
|- style = "vertical-align:top"
! scope = row | Spartan Host
| https://spartanhost.net/ || Seattle/WA/US, Dallas, TX/US || ? ||
|- style = "vertical-align:top"
! scope = row | Virtua Cloud
| https://virtua.cloud/ || Paris/Lille FR, Fremont US || ? || Requires Net-Block in ARIN IRR (AltDB/RadDB not accepted)
|- style = "vertical-align:top"
! scope = row | Vultr
| https://www.vultr.com/ || 16 Worldwide Locations || Yes ||
|}

== Notes ==
¹RPKI entries are not currently available for AMPRNet address space.

[[Category:Reference]]

Rip44d

2024-06-13T16:48:05Z

KC8QBA: Change in url for content hosted at github.

Technically, rip44d is a custom RIPv2 daemon which receives periodic routing table updates from the [[AMPRNet]] routing service, and inserts them in the Linux routing table.

RIP ([http://en.wikipedia.org/wiki/Routing_Information_Protocol Routing Information Protocol]) is a method to dynamically update IP routing tables. In practice, on the [[AMPRNet]] [[Gateway]], it removes the requirement to periodically download the tunnel routing table ([[encap.txt]]) using FTP and apply it to the routing table. It transmits changes quicker and should be simpler to set up. Amprgw transmits the RIP routing table updates every 5 minutes, while the encap.txt has traditionally been only updated once per day. Some operators have even done the downloads manually (and not very often).

The RIP protocol is used in a slightly unconventional way on the AMPRNet, and the standard IP routing daemons such as zebra/quagga are not able to process these packets. Until those daemons are modified to support Amprnet routing updates, a custom implementation such as rip44d can be used.

rip44d is written in the Perl programming language. C might be the conventionally right language to implement daemons such as this, but the author happened to have a good bunch of perl code that could be easily reused in the implementation of rip44d. The routing table is relatively small, so the performance or memory consumption of this daemon isn't very critical.

= Requirements =

# You'll need a Linux computer, which has been added in the Gateways file using the [[Portal]], so that it is know as an AMPRnet gateway and will receive RIP updates from the [[Amprgw]]. It will take some time before Amprgw will learn about new gateways.
# If you have been running the gateway before, and you have already set up a cron job to automatically update the routing table by downloading encap.txt, you need to disable that cron job so that there's only one updating method running at a time.
# The instructions below are currently only for Debian/Ubuntu, but there's nothing Debian-specific in rip44d - it should work fine on other distributions. It does not read or touch any of the operating system's configuration files.

= Installation of dependencies on Debian/Ubuntu =

install perl, and IO::Socket::Multicast, a Perl module used for receiving the RIP multicast packets

sudo apt-get install perl libio-socket-multicast-perl libio-interface-perl

install something to download the daemon, if needed

sudo apt-get install curl

= Installation of dependencies on other distributions =

Other distributions should have an easy way to install the required packages too (using yum or a similar program). Please fill in details here, if you know them.

If all else fails, but you have Perl installed already, you can use CPAN to install the module. For details, please see the [http://www.cpan.org/modules/INSTALL.html CPAN installation guide].

cpan App::cpanminus
cpanm IO::Socket::Multicast

= Installation of rip44d =

Download the daemon

curl -O https://raw.githubusercontent.com/hessu/rip44d/master/rip44d

Make it executable

chmod u+x rip44d

= Run it for the first time =

Run it first with the -v option to verify that it sees the route announcements from amprgw, and to learn the plaintext password used to authenticate the RIP packets (it's not included in the script, and I'm not posting it here, so that spoofing can only be done by those who are already receiving the announcements). Wait up to 5 minutes until the routes are transmitted, and it'll complain about the password it's not expecting:

hessu@gateway:~$ sudo ./rip44d -v
found local address: 1.2.3.4
found local address: 127.0.0.1
found local address: 44.255.259.253
opening UDP socket...
entering main loop, waiting for RIPv2 datagrams
received from 44.0.0.1: 520: 504 bytes
RIPv2 packet contains password PasswordFoundHere but we require none

Run it again with the correct password

hessu@gateway:~$ sudo ./rip44d -p PasswordGoesHere

Within 5 minutes it should receive the new routing table and take it into use. For added fun, use -v (verbose) or -d (debug, really verbose) to see what it does.

After confirming that it works, move it to /usr/local/sbin (or something) and put it in your boot scripts '''(see: [[startampr]])'''. At minimum, the following lines in /etc/rc.local should do the required tricks to bring Amprnet routing up. The IP addresses are intentionally invalid – you'll need to replace them with your own.

# Route my own subnet to blackhole, just to make sure I don't accidentally
# transmit packets destined for us back out to Amprgw and create a loop.
# More specific routes will route packets for these addresses out on the
# correct radio interfaces.
/sbin/ip route add blackhole 44.255.259.0/24
# Bring up the tunnel interface and assign an IP address to it.
/sbin/ifconfig tunl0 44.255.259.253 up || exit 2
# Start up the RIP routing daemon to learn the routing table.
/usr/local/sbin/rip44d -p PasswordGoesHere < /dev/null &

That should be all. Really. The downside of this configuration is that it will take up to 5 minutes for the gateway to receive a routing update and become operational after a reboot. The daemon should really be improved to store the current routing table in a local file and load it from there when starting up. '''(See: [[startampr]] about configuring reload of the AMPR routing table upon reboot with rip44d.)'''

The above route add command will cause packets destined to 44.255.259.* to be dropped on the floor, unless a more specific route (such as 44.255.259.0/25) exists. If you route the whole /24 subnet to your radio interface, the blackhole route should not be used. If you have smaller subnets or per-host routes for each user host, the blackhole route will prevent packets destined to unused addresses from getting into a loop between your gateway and the Amprgw.

= Notes =

* rip44d automatically ignores announced routes which are pointed to the system's local addresses. The addresses are automatically learned using /sbin/ifconfig, but you can add more gateway addresses using -a (comma-separated list of IP addresses).
* It expects that your tunnels are configured on tunl0. Use the -i <if> option to change to another. The tunnel interface must be up and configured before rip44d starts up.
* Old encap routes may be present, the daemon will overwrite them as necessary (it won't touch more specific routes, or ones which are not found in the route advertisements). You don't need to "clean" the routing table before running rip44d if you have populated it from encap.txt.
* rip44d does not automatically start, see [[startampr]] for more information about running on boot

= Support, bug reports and improvements =

If you have questions to ask about the usage of this daemon, please contact the [[44Net mailing list]].

If you have improved the daemon and wish to submit a patch, please use Github. Create an account, fork the rip44d repository to your own private repository, push your changes there, and submit a merge request. I'll then merge the changes in the master source tree and release a new version. Thank you!

Github repository: [https://github.com/hessu/rip44d https://github.com/hessu/rip44d]

The daemon was written by Heikki Hannikainen, OH7LZB.

Services

2024-05-22T22:05:21Z

KC8QBA: Moved some resources that are no longer available to a new historic services page; minor edits elsewhere.

{| class="wikitable sortable"
|-
! Maintainer !! Service Name!! URL/IP !! Service Type !! Description !! Other Information
|-
| AMPR ||[[Portal]] || https://portal.ampr.org || HTTPS || Used to request allocations, manage user profile information, [[Gateway]] entries, [[Encap.txt]] preferences and ampr.org DNS entries|| NONE
|-
| AMPR ||Website || https://www.ampr.org || HTTPS || AMPRNet Main Page|| NONE
|-
| AMPR ||Wiki || https://wiki.ampr.org || HTTPS || This Wiki|| NONE
|-
| AMPR ||44Net discussion group || https://ardc.groups.io/g/44net || HTTPS || AMPR discussion group|| NONE
|-
| AMPR ||ARDC announcements || https://ardc.groups.io/g/main || HTTPS || ARDC announcements|| NONE
|-
| AMPR ||AMPRNet Gateway [[Amprgw|(AMPRGW)]] || amprgw.ucsd.edu/169.228.34.84 || IP and IPENCAP [[Tunnel]]|| Routes traffic between the public internet and AMPRNet hosts connected via the IPIP mesh and originates [[RIP]] packets || Gateways use IP Protocol 4 (IPENCAP) to receive traffic via AMPRGW. Allocation must be registered in the [[Portal]] with a ampr.org DNS entry, and gateways must run an AMPRNet routing protocol (i.e. [[RIP]]44 or [[munge script]])
|-
| AMPR ||[[RIP]]44 || provided via [https://en.wikipedia.org/wiki/Broadcasting_%28networking%29 broadcast] from 44.0.0.1 to all [[gateway]]s registered in the [[portal]] || Routing Information (modified RIPv2 protocol) || distributed by main AMPRNet Router to multicast address 224.0.0.9|| 1.) an enabled IPENCAP tunnel, and 2.) [[ampr-ripd]] or [[rip44d]] must be running and properly configured on your registered gateway
|-
| AMPR ||[[Encap.txt]] || N/A || Routing Information (EMAIL/FTP/HTTP)|| routing information for download|| file must be must be parsed by a self-developed [[munge script]]
|-
| Various Operators||[[Ampr.org]] DNS and Reverse DNS (44.in-addr.arpa) ||
ns.ardc.net 
a.gw4.uk 
ns2.us.ardc.net 
ns1.de.ardc.net 
(These hosts are authoritative for AMPR.ORG and most of the '[0-191].44.in-addr.arpa' reverse zones. 
 
44.0.0.0/9 thru 44.128.0.0/10 hosts may use dns-mdc.ampr.org (44.60.44.3) as a recursive DNS server. It also has a copy of HAMWAN.ORG 
srv.kz2x.ampr.org (44.44.48.29) is a recursive resolver available to 44.0.0.0/9 and 44.128.0.0/10 
|| DNS || name resolution services||
|-
| Various Operators||Network Tools||
http://whatismyip.ampr.org 
http://yo2tm.ampr.org/nettools.php 
http://kb3vwg-010.ampr.org/tools 
http://speedtest.ampr.org 
|| HTTP|| source IP checker, speed test, Ping, Traceroute, etc.|| '''kb3vwg-010.ampr.org''' only available from hosts with an AMPRNet IP address
|-
| Various Operators ||Network Time Protocol || ntp.vk2hff.ampr.org (Stratum 1, AU) kb3vwg-001.ampr.org (Stratum 2, US) gw-44-137.pi9noz.ampr.org (Stratum 2)|| NTP|| Stratum 2 Network Time Server - References US, Canadian and Mexican|| '''kb3vwg-001.ampr.org''' only available from hosts with an AMPRNet IP address
|-
| N1URO ||AMPRNet/RF faxing || http://wiki.ampr.org/wiki/axMail-FAX || Facsimile || Online IP based Facsimile service. You have the ability to send emergency communications from packet via Fax. || [http://axmail.sourceforge.net axMail-FAX] Sofware is here.
|-
| [http://allstarlink.org AllStar Link] || AllStar || http://allstarlink.org || Linking of repeaters || AllStar Link core network services are provided via redundant datacenters using 44net IP space. || [https://wiki.allstarlink.org/wiki/Main_Page ASL wiki]
|-
| N2NOV and G1FEF || Hub_NA and Hub_EU for WWconvers Chat System || 44.68.41.2:3600 convers.g1fef.co.uk:3600 || Telnet || Only connections from other 44Net addresses allowed using port 3600. Stations like JNOS with a built-in local chat server can link to it. Individuals without a local chat portal can use an IRC client to a public IP address that must be arranged with the owner. || None
|-
| N2NOV || AMPRNet NE US Regional Portal || http://n2nov.ampr.org/hamgate.html || HTTP || AMPRNet NE US Regional Portal || None
|-
| [https://flscg.org/ FSG]|| HamWAN Remote || https://flscg.org/2022/04/hamwan-remote/ || VPN/BGP || We provide a VPN based remote site connection to [https://flscg.org/hamwan/ HamWAN Tampa] and can announce your IP space. Performance of over 1gbit/s is possible and we provide an local connection point for amateurs in the South Eastern United States. || https://wiki.w9cr.net/index.php/HamWAN_Remote_Site
|-
| [https://hamwan.org HamWAN]||HamWAN Open Peering||https://hamwan.org/Labs/Open%20Peering%20Policy.html||BGP/IPSec(AH)||We provide IPsec VPN w/ BGP peering + Internet announcing.||
|-}

Services previously available on AMPRNet but no longer actively supported can be viewed on the [[Services/Historic|Historic Services]] page.

Services/Historic

2024-05-22T21:52:25Z

KC8QBA: New page to retain information on previous services no longer available on the network.

Below is a list of historic services that were previously offered by ampr users but are not currently available.

{| class="wikitable sortable"
|-
! Maintainer !! Service Name!! URL/IP !! Service Type !! Description !! Other Information
|-
| N1URO ||Network Tools|| http://n1uro.ampr.org/do.shtml || HTTP|| source IP checker, speed test, Ping, Traceroute, etc.|| DNS entry no longer exists
|-
| Various Operators ||Network Time Protocol Server || ns.ardc.net (Stratum 2, UK) time.kz2x.ampr.org (Stratum 1, US) server.yo2loj.ampr.org (Stratum 2) f4gve.ampr.org (Stratum 3) ntp1.on3rvh.ampr.org || NTP|| Stratum 2 Network Time Server - References US, Canadian and Mexican|| No NTP server configured on host
|-
| OH7LZB ||[[AMPRNet_VPN]] || http://wiki.ampr.org/wiki/AMPRNet_VPN || VPN|| [http://en.wikipedia.org/wiki/OpenVPN OpenVPN]-based || '''Unavailable as of May 2024''' You must have a X.509 certificate issued by [http://www.arrl.org/logbook-of-the-world ARRL Logbook of the World (LoTW)]. ARRL membership is not required.
|-}