44Net Connect

44Net Connect is the quickest way to start participating in 44Net.

Instead of setting up BGP routing or IPIP Mesh, Connect establishes a WireGuard tunnel between your device and a Connect endpoint node. With the tunnel active, your system operates as a native 44Net host with its own address on the public Internet.

Your laptop, Raspberry Pi, router, cloud instance, or small lab can appear on 44Net even from behind residential NAT, CGNAT, mobile networks, or satellite links.

Connect uses WireGuard as transport, but it is not a privacy VPN. You are not logging in to a service; you are connecting your system to the public Internet. The purpose of the tunnel is to carry your traffic to a point of presence so your system can participate as a public network host.

Get Started with 44Net Connect

Step 1: Sign in to the Connect dashboard

Visit The 44Net Connect dashboard.
Click the “Log In to Get Started” button.
Sign in with your 44Net Portal account credentials.

New to the Portal? See GetStarted to sign up and get your callsign verified. You must have a verified callsign to use Connect. If you have a callsign but haven't completed verification, please do so before proceeding.

Step 2: Create your first tunnel

On the dashboard page, click the “Create Tunnel” button.
Select an endpoint region and node.
Enter a name for your tunnel, click the “Create Tunnel” button, and confirm.

Don’t worry too much about the endpoint selection. You can change it later if needed, and you can have multiple tunnels to different endpoints if you want. The tunnel name is just for your reference.

Step 3: Get your WireGuard configuration

Scroll down to find your tunnel configuration.
Click the “Copy to Clipboard” button to copy the configuration text.
Paste the configuration into your WireGuard client (Windows, macOS), or save it as a configuration file (e.g. wg0.conf on Linux, cloud instances, etc.).

The configuration includes your public and private keys, an automatically-assigned 44Net address, and the endpoint information. It’s a standard WireGuard config that you can use with any compatible client or device.

Step 4: Activate your tunnel

Start the WireGuard tunnel (“Activate” in the client, or wg-quick up wg0 on Linux).

Once the tunnel is active, your system operates as a native 44Net host. Inbound and outbound traffic is routed through the Connect endpoint, giving your device a direct connection to the Internet.

}} }}

Diagram showing a device connecting via WireGuard to a 44Net Connect endpoint and participating as a native 44Net host

How 44Net Connect works: your device establishes a WireGuard tunnel to a Connect endpoint node, which routes traffic to and from your assigned 44Net address.

What 44Net Connect Provides

A WireGuard tunnel to a Connect endpoint node
A usable 44Net IP address
Optional routed subnet assignments
Participation in 44Net without running BGP routing

How Connect Works

You authenticate to your Connect dashboard using your Portal account.
The Connect dashboard generates a WireGuard configuration.
Your device establishes a secure tunnel to a Connect endpoint node.
The endpoint routes traffic between your system and the Internet.
Your device participates on the Internet as a normal routed system.

The WireGuard tunnel provides transport only. It is not designed for privacy or anonymity, and it does not replace your internet connection.

Requirements

You will need:

A 44Net Portal account
A verified amateur radio callsign
A device capable of running WireGuard
Some sort of Internet access, even if it's behind NAT or CGNAT

Common supported platforms include:

Linux, macOS, and Windows systems
Raspberry Pi and similar single-board computers
Many home and commercial routers
Cloud instances and virtual machines
Some mobile hotspots and embedded networking devices

A continuously running device is supported if you plan to host services.

Connect Endpoint Nodes

44Net Connect uses multiple endpoint nodes operated within the 44Net infrastructure.

Endpoint nodes are hosted by ARDC in multiple locations.
Traffic entering through these nodes is routed to participating systems.
Capacity and geographic diversity continue to expand.
Future development includes support for volunteer-operated endpoint nodes.

Connect is designed as a distributed system rather than a single gateway.

What Connect Is Not

44Net Connect is not:

A commercial VPN service
An anonymity or privacy tool
A replacement for internet access
Required for participants who already operate routed subnets or BGP connectivity

Typical Use Cases

Personal stations reachable on 44Net
Remote access to home or lab systems
Temporary or portable applications
Linking or accessing remote repeaters
Learning about WireGuard and networking
Development of applications and services on 44Net
Remote monitoring or control systems
Exploring and experimenting with 44Net

Relationship to Other Participation Methods

Method	Best For
44Net Connect	Individuals and small systems
Routed Subnets	Established networks and organizations
RF / Mesh Networks	Local and regional wireless communities

Future Development

Ongoing work includes:

Additional endpoint regions
Volunteer-hosted nodes
Improved onboarding and automation
Deeper integration with Portal services

Related Pages