Main Page Draft: Difference between revisions

From 44Net Wiki
// via Wikitext Extension for VSCode
// via Wikitext Extension for VSCode
Line 15: Line 15:
For an inside look at how 44Net came to be, see [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story], a series of conversations with people who were there.
For an inside look at how 44Net came to be, see [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story], a series of conversations with people who were there.


{{CardRow|
== Start Here ==
== Start Here ==
{{CardRow|
{{Card|New to 44Net|[[GetStarted|Getting started]]}}
{{Card|New to 44Net|[[GetStarted|Getting started]]}}



Revision as of 18:36, 5 February 2026


44Net gives licensed amateur radio operators access to public, globally routable IP addresses, so they can build and operate real systems on the open Internet.

44Net IP addresses are globally routable, enabling direct connectivity on the public Internet.

44Net exists so individuals and groups can learn, experiment, and run services using directly reachable addresses, free of the constraints of NAT or consumer-grade Internet service.

On 44Net, participants work directly with the connective tissue of the Internet as builders, not just users.

The network traces its roots to 1981, when Hank Magnuski asked Jon Postel for IP address space to support amateur packet radio networking, at a time when the Internet was still taking shape in text files on university minicomputers. As the Internet has evolved, 44Net has grown through decades of technical and community stewardship into a worldwide federation of community networks.

Today, 44Net continues to be built and operated by its participants, with the support of Amateur Radio Digital Communicatons (ARDC).

For an inside look at how 44Net came to be, see The 44Net Origin Story, a series of conversations with people who were there.

{{{title}}}

Start Here

New to 44Net

What People Build on 44Net

Participants use 44Net address space for a wide range of independent and community projects, including:

  • Personal and home infrastructure
    Remote access to home stations, self-hosted services, and project sites
  • Shared radio and emergency systems
    Networked repeaters, gateways, and public-service communications
  • Community networks
    Club, maker space, and local group infrastructure
  • RF and point-to-point links
    VHF, UHF, and microwave links across regions and between sites
  • Overlay and experimental networks
    VPNs, tunnels, mesh systems, and testbeds

For more detailed examples and case studies, see What People Build on 44Net.

Stewardship and Participation

44Net is sustained through a combination of volunteer effort, shared norms, and institutional support. Most of the network’s day-to-day work — from maintaining infrastructure to helping new participants — is carried out by members of the community.

ARDC provides governance, legal and fiduciary oversight, and staff support. Within that framework, participants are responsible for building, operating, and caring for their own systems, and for working cooperatively with others who share the network.

Policies and guidelines are developed and maintained in the open, drawing on community experience and evolving operational practice. While many reflect long-standing norms, others are still being refined as the network grows and new use cases emerge. ARDC provides continuity and institutional oversight, helping ensure that this process remains fair, consistent, and aligned with the network’s long-term stewardship.

Participation in 44Net takes many forms: running services, maintaining documentation, mentoring new users, contributing technical expertise, and helping coordinate shared projects. All of these forms of work are valued and necessary to the health of the network.

Documentation Status

This wiki is under active reconstruction as part of an ongoing effort to improve clarity, organization, and coverage. Some pages are incomplete, outdated, or in transition as this work progresses.

Foundational guides, portal documentation, and operational references are being developed in stages. For now, this page serves as a pointer to current, maintained resources.

Next Steps

If this page has helped you orient yourself, these are good ways to continue: