How Connect, IPIP Mesh, and BGP Fit Together
44Net is a decentralized network space. There is no single backbone, central router, or network operations center coordinating connectivity for all participants.
Instead, ARDC stewards the address space while independent operators bring portions of 44Net online using different technical approaches. These approaches coexist within the same address space, but they are not automatically integrated with one another.
One Address Space, Many Networks
Because 44Net is decentralized, participation happens through multiple independent systems rather than a single unified service. Think of 44Net as shared addressing used by many independently operated networks, rather than one global network run from a single place.
Three Ways to Put 44Net on Your Network
There are several common ways to make 44Net addresses reachable from participating systems:
44Net Connect
- Provides a reachable 44Net address directly to a device or local network
- Uses a managed WireGuard-based service
- Requires minimal routing knowledge
- Suitable for experimentation, services, and individual participation
IPIP Mesh
- A cooperative overlay network operated by participating nodes
- Routers form tunnels with peers and exchange routes
- Connectivity emerges from relationships between operators
- Often used for regional or collaborative networks
BGP Announcements
- Independently operated networks announce their own 44Net prefixes
- Requires upstream connectivity and an ASN
- Operators manage routing policy and infrastructure themselves
- Used by organizations or established network operators
Sometimes these seem like stages or upgrade levels, but they are really just different methods of participation. Many networks use a combination of these approaches based on the nature of each project.
Why These Systems Are Independent
The separation between Connect, Mesh, and BGP is a natural consequence of 44Net’s decentralized nature.
Each method has its own:
- control plane
- operational responsibilities
- trust relationships
- routing mechanisms
ARDC assigns address space, but does not operate a unified routing system for all users. As a result, no automatic coordination exists between participation methods.
A subnet reachable via Connect is not automatically part of the Mesh. A Mesh network does not automatically appear via BGP. A BGP-announced network operates independently unless operators choose to interconnect.
Connectivity in 44Net emerges from cooperation between participants rather than centralized control.
Can I Move or “Port” My Subnet Between Systems?
No. A subnet allocation is effectively tied to its origin. There is no migration path because the systems are independent by design.
You can, however, operate subnets in multiple systems simultaneously. You can even have multiple subnets accessible through a single router you operate, as long as you manage the routing appropriately. But there is no way to “port” a subnet from one system to another.