Provisioning Methods
44Net provides address resources and ways to connect amateur radio projects. You can use a service that supplies connectivity, participate in a community network, or request address space for a network whose connectivity you arrange.
This page helps you choose what your project needs and where to start. New here? See Getting started for account setup.
IP networks and connectivity
44Net Connect
44Net Connect gives your device or network public IP addresses through a WireGuard tunnel over your existing Internet connection. ARDC operates the Connect endpoints; you maintain your device or gateway, its routing, and its firewall.
Includes: Addresses and a WireGuard tunnel, with routed subnets available through the Connect dashboard. You do not need to request address space separately in the Portal before creating a tunnel.
Requirements: Internet access and a device or router that supports WireGuard. Connect works behind NAT and CGNAT, provided your connection allows WireGuard traffic to reach the endpoint.
Start here: Choose a single-device or routed-subnet setup, then sign in to the Connect dashboard with your Portal account.
IPIP Mesh
The IPIP Mesh connects participating amateur radio networks through IP-in-IP tunnels. You can operate your own gateway or ask an existing participating network about connecting through its infrastructure. ARDC supports the Mesh and operates a shared Internet gateway; participants operate their own gateways and networks.
Includes: An address assignment for Mesh use. For your own gateway, you register its endpoint and subnet in the Portal and configure tunnels and routes to other Mesh networks.
Requirements: An IPIP-capable gateway, a reachable public IPv4 endpoint, and an Internet connection that permits IPIP (IP protocol 4). NAT and CGNAT are not supported. The Mesh does not provide general-purpose Internet access; see its overview for the limits of the shared Internet gateway.
Start here: Check the requirements and choose how to participate. For your own gateway, request a Mesh address assignment in the Portal.
Address space and registration
Connectivity you arrange
If you are building a network with your own connectivity, you can request 44Net address space for it. ARDC maintains the assignment and provides routing authorization where applicable. You and your network or upstream provider arrange how traffic reaches the addresses.
Includes: An IP address assignment, a Letter of Authorization (LOA) for BGP announcements where applicable, and optional reverse DNS delegation.
Requirements: A network plan and your own connectivity. For a BGP-announced subnet, you need an upstream or routing arrangement that can announce it. Your provider may announce on your behalf, or you may operate BGP yourself, depending on that arrangement.
Start here: Request address space in the Portal. For Internet routing through a provider, read the BGP overview and BGP Quick Start before requesting service from an upstream. You may also want to review the Guide for ISPs.
For these independently connected assignments, ARDC provides address resources and authorization. You and your provider are responsible for connectivity, routing, and transit.
If you are joining an existing network, ask its operators how addresses and routing are arranged before requesting a separate assignment.
Supporting services
DNS
DNS gives names to your devices and services. You can request an ampr.org subdomain for your callsign, or a club or organization subdomain subject to review, and manage records beneath it.
DNS can support projects using Connect, the Mesh, or independently arranged connectivity. A and AAAA records can point to addresses outside 44Net as well as to 44Net addresses.
Reverse DNS for an address assignment is a separate facility from a callsign subdomain. Reverse DNS for 44Net Connect is not currently available.
Reverse DNS delegation for eligible BGP subnets is available by request; check the delegation requirements and open a support ticket in the Portal.
Start here: Request and manage a subdomain in the Portal.
Joining an existing project
You may be able to participate through an independently operated network or project. Its operators determine how you join, what connectivity they provide, and what equipment or resources you need. Ask them whether you should request your own address assignment before applying for one.
Independently operated networks such as HAMNET and HAMGATE use 44Net resources. Networks built with AREDN can also use 44Net addresses; ask the local operators what their network supports.
Choosing for your project
If you want…
A public address for a device or small network over an existing Internet connection:
Start with 44Net Connect. It can work behind NAT and CGNAT.
Communication with networks on the IPIP Mesh:
Check the Mesh requirements, or ask a participating network about joining through it.
Addresses for a network whose connectivity you arrange:
Request address space. If an upstream will announce it to the Internet, follow the BGP guide.
Names for your devices or services:
Use DNS alongside the connection you choose.
These choices describe what your project needs, not a sequence of upgrades. A project may use more than one. Using 44Net addresses does not automatically make systems reachable from every other 44Net network; reachability depends on routing, service arrangements, and firewall rules.