44Net Connect: Difference between revisions
// via Wikitext Extension for VSCode |
mw push |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 9: | Line 9: | ||
{{Section| | {{Section| | ||
{{SectionCard| | {{SectionCard| | ||
==Start | == Start using 44Net Connect == | ||
New to Connect? Jump straight to the step‑by‑step setup guide: | New to Connect? Jump straight to the step‑by‑step setup guide: | ||
[[44Net Connect Quick Start|→ 44Net Connect Quick Start]] | [[44Net Connect/Quick Start|→ 44Net Connect Quick Start]] | ||
You can return here later to learn how Connect works in more detail. | You can return here later to learn how Connect works in more detail. | ||
| Line 20: | Line 20: | ||
[[File:44net-connect-overview.svg|center|800px|alt=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.]] | [[File:44net-connect-overview.svg|center|800px|alt=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.]] | ||
If you prefer to follow a guided setup instead of reading the overview first, see [[44Net Connect Quick Start]]. | If you prefer to follow a guided setup instead of reading the overview first, see [[44Net Connect/Quick Start|44Net Connect Quick Start]]. | ||
== What 44Net Connect | == What 44Net Connect provides == | ||
* A WireGuard tunnel to a Connect endpoint node | * A WireGuard tunnel to a Connect endpoint node | ||
| Line 29: | Line 29: | ||
* Participation in 44Net without running BGP routing | * Participation in 44Net without running BGP routing | ||
== How Connect | == How Connect works == | ||
# You authenticate to your Connect dashboard using your Portal account. | # You authenticate to your Connect dashboard using your Portal account. | ||
| Line 37: | Line 37: | ||
# Your device participates on the Internet as a normal routed system. | # Your device participates on the Internet as a normal routed system. | ||
The WireGuard tunnel | The WireGuard tunnel is transport, not cover. It is not designed for privacy or anonymity and does not replace your internet connection. | ||
== Requirements == | == Requirements == | ||
| Line 58: | Line 58: | ||
A continuously running device is supported if you plan to host services. | A continuously running device is supported if you plan to host services. | ||
== Connect | == Connect endpoint nodes == | ||
44Net Connect uses multiple endpoint nodes operated within the 44Net infrastructure. | 44Net Connect uses multiple endpoint nodes operated within the 44Net infrastructure. | ||
| Line 69: | Line 69: | ||
Connect is designed as a distributed system rather than a single gateway. | Connect is designed as a distributed system rather than a single gateway. | ||
== What Connect | == What Connect is not == | ||
44Net Connect is '''not''': | 44Net Connect is '''not''': | ||
| Line 78: | Line 78: | ||
* Required for participants who already operate routed subnets or BGP connectivity | * Required for participants who already operate routed subnets or BGP connectivity | ||
== Typical | == Typical use cases == | ||
* Personal stations reachable on 44Net | * Personal stations reachable on 44Net | ||
| Line 89: | Line 89: | ||
* Exploring and experimenting with 44Net | * Exploring and experimenting with 44Net | ||
== Relationship to | == Relationship to other participation methods == | ||
{| class="wikitable" | {| class="wikitable" | ||
| Line 101: | Line 101: | ||
|} | |} | ||
== Future | == Future development == | ||
Ongoing work includes: | Ongoing work includes: | ||
| Line 110: | Line 110: | ||
* Deeper integration with Portal services | * Deeper integration with Portal services | ||
== Ready to | == Ready to try it? == | ||
You can set up a working 44Net connection in just a few minutes: | You can set up a working 44Net connection in just a few minutes: | ||
* [[44Net Connect Quick Start|Start the Quick Start Guide]] | * [[44Net Connect/Quick Start|Start the Quick Start Guide]] | ||
== Related | == Related pages == | ||
* [[Portal]] | * [[Portal]] | ||
Latest revision as of 22:50, 25 February 2026
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.
Start using 44Net Connect
New to Connect? Jump straight to the step‑by‑step setup guide:
You can return here later to learn how Connect works in more detail.
If you prefer to follow a guided setup instead of reading the overview first, see 44Net Connect Quick Start.
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 is transport, not cover. It is not designed for privacy or anonymity and 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
Ready to try it?
You can set up a working 44Net connection in just a few minutes: