Ways to Connect

New here? Start with Getting started.

There are several ways to bring 44Net to your device or network. Each method reflects a different networking environment rather than a level of experience. Some participants place 44Net on a single system behind NAT, others operate within shared community networks, and some integrate 44Net directly into independently operated infrastructure.

Choose the approach that fits best with your current setup. To understand why these approaches are independent by design, see Decentralization.

Choose your starting point

Single host or mobile deployment

44Net Connect

The fastest way to put 44Net on a device or small network.

• Works from typical home networks, cloud hosts, or mobile devices
• Minimal setup; often requires no router changes
• Good for experimentation, hosting services, or learning how 44Net works
• Lets you route a small subnet if you want to grow beyond a single host

→ Get started with 44Net Connect

---

Community or regional network

IPIP Mesh

A long‑standing 44Net deployment model built around shared community routing.

• Connect independent stations into a shared routed environment
• Common in long‑running regional and club networks
• Traffic to and from the wider Internet typically transits shared gateways (such as UCSD)
• Well suited for persistent stations that participate in community infrastructure

---

Independently routed network

BGP-announced subnet

Integrate 44Net directly into an independently operated network.

• Announce 44Net routes using your existing routing infrastructure
• Maintain your own routing policy and operational practices
• Suitable for research networks, IX-connected operators, community backbones, and advanced deployments
• Emphasizes autonomy rather than centralized gateways

Comparing the approaches

Use this table to decide which model matches how you want to participate.

Path	Best when you…	How your traffic reaches the Internet	What you operate
44Net Connect	want a 44Net presence on one host or a small network, from almost any uplink (home, cloud, mobile)	44Net traffic is carried over a tunnel you operate from your host or router	a tunnel endpoint you control; optional routing for a small routed subnet
IPIP Mesh	want to participate in a shared community network (regional, club, collaborative)	your traffic typically transits shared mesh gateways (such as UCSD) and can route within the mesh	a mesh node that peers with other nodes; routing within the shared mesh
BGP-announced subnet	already operate routable infrastructure and want to integrate 44Net directly into it	your routes are announced via BGP as part of global routing (under your policy)	your own routers, BGP edge, and routing policy for the subnet

Choosing the right fit

These connection methods coexist and serve different operational needs.

• 44Net Connect places 44Net on an individual device or small network and works from almost anywhere.

• IPIP Mesh connects independently operated stations into a shared routing environment with community gateways.

• BGP‑announced subnets integrate 44Net into networks that already participate in Internet routing.

Many participants use whichever model fits their environment today. Some operate more than one at the same time.

Under the hood

All connection methods ultimately place your systems into the same shared 44Net address space. The differences are operational: how routes reach you, where gateways exist, and who is responsible for routing decisions.

Learn more

• Getting started
• Routing and connectivity
• Community projects
• How Connect, IPIP Mesh, and BGP fit together

Older docs and notes

Earlier pages that may still be useful:

• Gateway
• Registering Your Gateway
• Tunnel
• AMPRNet VPN
• Routing your allocation via BGP
• Announcing your allocation directly
• Why can’t I announce my allocation directly?
• See Archive for more.