44Net Wiki - User contributions [en]

Get Help

2026-04-15T17:15:33Z

KI5QKX: mw push

{{DISPLAYTITLE:Get Help}}

Use this page when you are stuck, unsure where to start, or trying to find the right place to ask a question.

44Net support is primarily community-based. The wiki is the first place to look for documented setup paths, and the discussion groups are where operators help one another with edge cases, troubleshooting, and operational questions.

== Start here first ==

Before posting a question, check the page that matches what you are trying to do:

* [[GetStarted|Getting started]] if you need the overall onboarding path
* [[Provisioning Methods|Provisioning Methods]] if you are not sure whether to use Connect, IPIP Mesh, or BGP
* [[44Net Connect/Quick Start|44Net Connect Quick Start]] if you want to bring up a WireGuard-based tunnel
* [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]] if you want to participate through the shared mesh model
* [[BGP/Quick Start|BGP Direct Announce Quick Start]] if you already manage routed infrastructure
* [[FAQ]] if you want answers to common operational and policy questions
* [[Portal/Sign Up|Portal Sign Up]] if you are still creating your account or verifying your callsign
* [[Portal/Request Address Space|Requesting Address Space]] if you are ready to request resources

== Ask for help ==

If the wiki does not answer your question, use the discussion channels or the Portal as appropriate:

* [https://groups.io/g/ardc/44net ARDC 44Net discussion group] for setup questions, troubleshooting, routing questions, and general operational discussion
* [[Community|Community]] for the broader explanation of how help, coordination, and participation work on 44Net
* The Portal's ticket system for account access, callsign verification, address verification, or other administrative issues

If you cannot log in to the Portal, see [[Portal]] for the note about using the Portal's contact option.

== Before you post ==

Include enough context for someone else to reason about the problem:

* Which participation model you are using: Connect, IPIP Mesh, or BGP
* Your platform or device: Linux, UniFi, MikroTik, cloud VM, and so on
* Your network posture: home NAT, public IP, CGNAT, VPS, or routed subnet
* The exact step where things fail
* The exact error message or observed behavior
* What you already tried

Good problem statements get better answers faster.

For the broader explanation of how discussion, coordination, and shared knowledge work here, see [[Community]].

== Related pages ==

* [[Community]]
* [[GetStarted|Getting started]]
* [[Provisioning Methods|Provisioning Methods]]
* [[FAQ]]
* [[Contributing|Contributing]]
* [[Verification]]

[[Category:Community]]
[[Category:Getting Started]]

Contributing

2026-04-15T17:15:33Z

KI5QKX: mw push

{{DISPLAYTITLE:Contributing}}

This page explains how to contribute useful work to 44Net docs and systems.
It is for operators, maintainers, developers, and participants who want to help.

== Why contribute ==

ARDC staff help produce documentation and maintain software tools, but the community is what keeps 44Net running and usable.

If you have a question, ask it. If you have an answer, share it. If you have a project writeup or lesson learned, post it. If you find a gap in the docs or a rough edge in a tool, fix it or help someone else fix it.

Many of the best improvements start the same way:

* someone runs into a real problem
* the answer is worked out in public
* the result is turned into documentation, code, or a better workflow

== What kinds of contributions help ==

Useful contributions include:

* documenting a setup that actually works
* correcting outdated or incomplete wiki content
* improving examples, troubleshooting notes, and caveats
* contributing code to tools and infrastructure
* testing new features or configurations and reporting what happened
* helping others troubleshoot on the discussion groups
* sharing project writeups, lessons learned, and operating experience

== Documentation ==

Documentation work is one of the highest-leverage ways to help.

If a recurring question appears on the mailing list or discussion group, consider converting the answer into a short wiki update. That keeps operational guidance searchable and reduces repeated troubleshooting cycles.

When contributing documentation:

* start with a specific gap from [[GetStarted|Getting started]], [[Provisioning Methods|Provisioning Methods]], or a platform/setup page
* prefer small, verifiable updates over broad rewrites
* include concrete context such as device role, NAT posture, tunnel endpoint, routing behavior, and observed outcomes
* document caveats, rollback concerns, and anything still unverified
* write from actual tested experience where possible

For large or potentially contentious changes, it is often worth discussing them first in [[Community]].

== Software and tools ==

If you have software development experience and want to contribute code, there are several ways to help:

* propose a new tool or feature and discuss it in [[Community]]
* contribute to an existing project on [https://git.ampr.org GitLab]
* improve small operational tools, scripts, and documentation helpers
* help test changes and report regressions or rough edges

If you want to contribute to an existing repository, check its contribution guidelines and open issues first. If the direction is unclear, start by asking in the relevant discussion space.

== Other ways to participate ==

Not every contribution needs to be a wiki edit or a code change.

Other valuable ways to help include:

* testing configurations and reporting outcomes
* helping others troubleshoot their setups
* handling verification-related or administrative volunteer work where appropriate
* supporting community projects with time, equipment, hosting, or coordination
* building something useful and sharing it back with the rest of 44Net

== Collaboration and feedback ==

In a contribution context, collaboration is about how work gets improved without creating churn.

The contributions that tend to stick are the ones that:

* solve a specific problem
* explain their scope and tradeoffs clearly
* stay open to correction and revision
* leave room for others to build on the result

When proposing or making changes:

* be explicit about what problem you are trying to solve
* distinguish tested facts from assumptions or preferences
* prefer incremental improvements over broad rewrites unless there is a clear reason not to
* share suggestions in a blameless way that focuses on the work, not the person
* respond to review with concrete adjustments, not defensiveness
* avoid presenting one setup, tool, or practice as the only valid approach unless policy or technical constraints require it

The goal is not consensus for its own sake. The goal is to produce work that is accurate, useful, reviewable, and maintainable.

== Licensing ==

Material produced by ARDC staff is generally released under a Creative Commons Attribution-ShareAlike license ([https://creativecommons.org/licenses/by-sa/3.0/ CC-BY-SA]) or the non-commercial variant. ARDC-supported software projects are generally licensed under the Affero GNU General Public License ([https://www.gnu.org/licenses/agpl-3.0.html AGPL]).

Others in the community may publish material under different licenses or according to different terms, but if those terms are not compatible with the CC-BY-SA license or the AGPL, that material should not be posted to this wiki or shared as an official 44Net resource. Here, we like to share work openly.

== Related pages ==
* [[Community]]
* [[Governance|Governance]]
* [[Policies|Policies]]
* [[What People Build|What People Build]]
* [[GetStarted|Getting started]]
* [[Routing|Routing and connectivity]]

[[Category:Documentation]]

Community

2026-04-15T17:15:33Z

KI5QKX: mw push

{{DISPLAYTITLE:Community}}

This page explains how 44Net works as a community of operators, maintainers, and contributors.
It is also a directory of the main places where people ask questions, coordinate changes, and stay in touch.

If you are blocked right now and want the most direct support entry point, start with [[Get Help]].

== What we mean by “community” ==

More than just a block of IP addresses, 44Net is also a long-running technical community.

Much of the operational knowledge that keeps 44Net usable lives in the experience of the people who run it, troubleshoot it, write documentation, maintain software tools, and help newcomers get unstuck. The mailing lists are where that knowledge is developed and shared.

Asking for help is one of the first ways people join the community. As with amateur radio, asking questions and helping one another is how people learn about how things work and eventually go on to help the next person.

== Where to ask questions ==

For most 44Net technical questions, start here:

* [https://ardc.groups.io/g/44net ARDC 44Net discussion group]

This is the main public forum for:

* Setup questions that go beyond the documented quick starts
* Troubleshooting odd routing, NAT, DNS, or platform-specific behavior
* Discussing proposed documentation changes or shared operational practices
* Sharing working examples, lessons learned, and project writeups

Note that administrative issues like account access, verification, or requests that depend on Portal workflow should generally go through the [https://portal.ampr.org/ Portal ticket system] instead of the discussion group.

If you are blocked and want the clearest practical starting point, see [[Get Help]].

== Groups.io and discussion channels ==

ARDC maintains a Groups.io presence with multiple public subgroups. The most relevant ones for 44Net readers are:

* [https://ardc.groups.io/g/main ARDC Main]: low-volume announcements and broad ARDC updates
* [https://ardc.groups.io/g/44net 44Net]: the main 44Net discussion group for setup, troubleshooting, and operations
* [https://ardc.groups.io/g/44Net-connect 44Net Connect]: discussions specifically about the 44Net Connect project
* [https://ardc.groups.io/g/community ARDC Community]: broader discussion about ARDC and its work ''not related to 44Net''
* [https://ardc.groups.io/g/net-44-vpn ARDC 44Net VPN]: discussion related to VPN-style access systems ''not specifically related to 44Net Connect''
* [https://ardc.groups.io/g/developer-community ARDC Developer Community]: discussion related to software development and open source projects supported by ARDC
* [https://ardc.groups.io/g/wiki ARDC Wiki]: discussion related to the wiki and documentation work

There are other groups related to the grants program, committees, and more. See the [https://ardc.groups.io/ ARDC Groups.io directory] for a full list.

== Social and other community resources ==

Official ARDC channels and resources that may be useful:

* [https://www.ardc.net/44net/ ARDC 44Net page]
* [https://www.ardc.net/about/contact/ ARDC contact page]
* [https://mastodon.hams.social/@ARDC Mastodon]
* [https://bsky.app/profile/ardc-73.bsky.social Bluesky]
* [https://twitter.com/ardc_73 Twitter / X]
* [https://www.facebook.com/ardc.73 Facebook]
* [https://www.linkedin.com/company/amateur-radio-digital-communications/ LinkedIn]
* [https://www.youtube.com/@ARDC73 YouTube]
* [https://vimeo.com/ardc73 Vimeo]

Other useful entry points:

* [[Get Help]]
* [[GetStarted|Getting started]]
* [[What People Build|What People Build]]
* [[Contributing|Contributing]]
* [[44Net mailing list]] for historical context and legacy list references

== Community norms ==

Fundamentally, 44Net is a federation of technical operators who share a common interest in building and maintaining non-commercial, community-run network infrastructure. The community is generally welcoming and supportive of newcomers, and encourages people to ask questions, share their experiences, and contribute in whatever way they can.

There is no one project that constitutes all of 44Net. It is not just RF networks, or just tunnels, or just a specific set of services. It is a collection of different activities that all contribute to the overall ecosystem. This range of disparate efforts is part of what makes the community interesting.

=== Asking questions ===

When asking a question, it’s helpful to be as specific as possible about the problem you’re facing and what you’ve already tried. This can help others understand your situation and provide more targeted advice.

For example, instead of asking “Why isn’t my tunnel working?”, you might say “I’m trying to set up a WireGuard tunnel on my Linux server using the configuration from the 44Net dashboard, but I’m getting an error message that says ‘Configuration Invalid’. I’ve checked that the private key is correct and that the config works on another device, but I’m still stuck. Has anyone seen this before?”

For a practical checklist of what context to include, see [[Get Help]].

=== Sharing knowledge and experience ===

When sharing a project writeup or lesson learned, consider how it might be useful to others in the community. Include details about your setup, what worked well, and any challenges you faced. This can help others understand how your experience might apply to their own situation.

For example, instead of saying “I got it working by doing X”, you might say “I was able to get my WireGuard tunnel working on my Raspberry Pi by following the instructions in the 44Net Connect quick start guide, but I had to make a few adjustments. I had to change the MTU setting to 1380 because I was experiencing packet loss with the default MTU of 1420. I also had to make sure that my firewall was allowing traffic on the WireGuard port. Once I made those changes, everything started working smoothly.”

=== Collaboration and feedback ===

The projects that tend to succeed are those that focus on solving a specific problem, and that are open to collaboration and feedback from others. Projects that are less open to collaboration, that hold strict expectations for how things should be done, or that try to represent themselves as the “one true way” to do something, tend to be less successful and less well-received by the community.

For these reasons and more, it’s ''pragmatic'' to be respectful and considerate of others and to focus on the problem at hand and how to solve it, rather than on personal opinions or preferences.

Attempts to gatekeep or exclude certain types of participation are generally avoided and discouraged, except when there's a need to address bad-faith behavior or the potential for harm. The community generally seeks to preserve and protect healthy, constructive, non-disruptive activity.

== Community structure ==

The 44Net community is supported by several overlapping structures. If you want to understand how people participate, how decisions get made, or where stewardship responsibilities sit, these pages provide the next layer of context:

* [[Governance]]: how decisions are made for shared resources, documentation, and unresolved questions
* [[Roles and Participation]]: the broad map of who helps sustain 44Net and how those roles differ
* [[Regional Coordinator]]: how local stewardship, mentorship, and regional continuity work in practice
* [[Policies]]: the formal expectations that sit alongside community norms

== Contributing ==

One of the ways community knowledge becomes useful is by turning answers, working configurations, shared practices, and lessons learned into documentation and software.

If you want to help improve the wiki, contribute code, test ideas, or share a project writeup, see [[Contributing]].

== Related pages ==
* [[Get Help]]
* [[GetStarted|Getting started]]
* [[Provisioning Methods|Provisioning Methods]]
* [[What People Build|What People Build]]
* [[Contributing|Contributing]]
* [[Governance|Governance]]
* [[Policies|Policies]]

== Older docs and notes ==
Earlier pages that may still be useful:
* [[44Net mailing list]]
* [[Re: 44Net Digest, Vol 3, Issue 96]]
* [[K2IE]]
* [[ARDC]]
* [[Ampr.org]]
* See [[Archive]] for more.
[[Category:Community]]

Get Help

2026-04-15T15:47:48Z

KI5QKX: mw push

{{DISPLAYTITLE:Get Help}}

Use this page when you are stuck, unsure where to start, or trying to find the right place to ask a question.

44Net support is primarily community-based. The wiki is the first place to look for documented setup paths, and the discussion groups are where operators help one another with edge cases, troubleshooting, and operational questions.

== Start here first ==

Before posting a question, check the page that matches what you are trying to do:

* [[GetStarted|Getting started]] if you need the overall onboarding path
* [[Provisioning Methods|Provisioning Methods]] if you are not sure whether to use Connect, IPIP Mesh, or BGP
* [[44Net Connect/Quick Start|44Net Connect Quick Start]] if you want to bring up a WireGuard-based tunnel
* [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]] if you want to participate through the shared mesh model
* [[BGP/Quick Start|BGP Direct Announce Quick Start]] if you already manage routed infrastructure
* [[FAQ]] if you want answers to common operational and policy questions
* [[Portal/Sign Up|Portal Sign Up]] if you are still creating your account or verifying your callsign
* [[Portal/Request Address Space|Requesting Address Space]] if you are ready to request resources

== Ask for help ==

If the wiki does not answer your question, use the discussion channels or the Portal as appropriate:

* [https://groups.io/g/ardc/44net ARDC 44Net discussion group] for setup questions, troubleshooting, routing questions, and general operational discussion
* [[Community|Community]] for the broader explanation of how help, coordination, and participation work on 44Net
* The Portal's ticket system for account access, callsign verification, address verification, or other administrative issues

If you cannot log in to the Portal, see [[Portal]] for the note about using the Portal's contact option.

== Before you post ==

Include enough context for someone else to reason about the problem:

* Which participation model you are using: Connect, IPIP Mesh, or BGP
* Your platform or device: Linux, UniFi, MikroTik, cloud VM, and so on
* Your network posture: home NAT, public IP, CGNAT, VPS, or routed subnet
* The exact step where things fail
* The exact error message or observed behavior
* What you already tried

Good problem statements get better answers faster.

== How help works here ==

44Net does not work like a conventional product with a separate support department for every technical question.

Most practical help happens through participants helping one another in public discussion spaces and then turning durable answers into documentation. That is why the best long-term way to get help is to use the wiki, ask clearly in the discussion group when needed, and feed working answers back into the documentation.

For more on that model, see [[Community]].

== Related pages ==

* [[Community]]
* [[GetStarted|Getting started]]
* [[Provisioning Methods|Provisioning Methods]]
* [[FAQ]]
* [[Contributing|Contributing]]
* [[Verification]]

[[Category:Community]]
[[Category:Getting Started]]

44Net Connect/UniFi

2026-04-15T15:40:38Z

KI5QKX: mw push

{{DISPLAYTITLE:44Net Connect on UniFi Network}}

Use this guide to import a 44Net Connect WireGuard configuration into UniFi
Network and create a tunnel on a UniFi gateway.

== What you need ==

* A 44Net Portal account
* A verified amateur radio callsign
* A 44Net Connect tunnel created in the Connect dashboard
* A UniFi gateway managed in UniFi Network
* A computer with a web browser and a plain-text editor

If you still need to create your account, verify your callsign, or create your
first Connect tunnel, start with [[GetStarted|Get Started]] and
[[44Net Connect/Quick Start|44Net Connect Quick Start]].

{{Info|Note|Ubiquiti updates the Network application frequently, so the steps and screenshots in this guide may not match exactly with the current version of UniFi Network. The general process should still be similar, but if you have trouble following these instructions, refer to the UniFi Network documentation or support resources for the most up-to-date information on creating a WireGuard VPN client. You can also ask a question the 44Net Connect mailing list.}}

== Before you upload the configuration ==

UniFi Network does not currently accept the IPv6 address included in the
<code>Address</code> line of the WireGuard configuration generated by the
Connect dashboard. The configuration must be edited to remove the IPv6 address
before it can be imported into UniFi Network.

Copy and paste the <code>wg-quick</code> configuration from the Connect
dashboard to a plain-text file, then edit the <code>Address</code> line so it
contains only the IPv4 address.

For example, change:

<pre>
Address = fe80::dca1:c755:aa1:28f2/128, 44.27.128.48/32
</pre>

to:

<pre>
Address = 44.27.128.48/32
</pre>

Save the file before continuing.

== Configure UniFi Network ==

{{Step|
=== Step 1: Open UniFi Site Manager ===
{{StepText|
* On a computer, open a web browser.
* For cloud-connected gateways, go to [https://unifi.ui.com unifi.ui.com].
* For local-only gateways, go to the gateway's local IP address instead.
* Sign in and select the site that contains the gateway you want to configure.
}}
}}

{{Step|
=== Step 2: Open the Network application ===
{{StepText|
* From Site Manager, open the '''Network''' application for the selected gateway.
* Wait for the gateway and site settings to finish loading before creating the VPN client.
}}
}}

{{Step|
=== Step 3: Start a new WireGuard VPN client ===
{{StepText|
* In UniFi Network, click the Settings (gear) icon.
* In the Settings sidebar, click '''VPN'''.
* In the '''VPN Client''' section, click '''Create New'''.
* In the details pane:
* Under '''Type''', select '''WireGuard'''.
* Under '''Name''', provide a name for the VPN client, like <code>44Net Connect</code>.
* Under '''Setup''', choose '''File'''.
}}
}}

{{Step|
=== Step 4: Upload the 44Net Connect configuration file ===
{{StepText|
* In the details pane, click the '''Upload Configuraton File''' button.
* Navigate to the file you saved in the previous section and select it for upload.
* Select the plain-text file you saved from the Connect dashboard (after removing the IPv6 address from the <code>Address</code> line).
* Review the imported settings to confirm the endpoint, keys, and IPv4 address were accepted.
}}
}}

{{Step|
=== Step 5: Create the tunnel ===
{{StepText|
* Click the '''Create''' button to create the VPN client and tunnel.
}}
}}

== Verify operation ==

After the tunnel is created:

* Confirm the VPN client shows as connected in UniFi Network.
* Confirm the tunnel shows "Connected" in the Connect dashboard.

You may need to reload the page or wait a few moments for the status to update from "Connecting" to "Connected".

== Troubleshooting ==

If the import fails, re-open the configuration file and confirm the <code>Address</code> line contains only the IPv4 address. Re-import it if necessary.

If the tunnel fails to connect, confirm the public key and endpoint in UniFi Network match the values shown in the Connect dashboard.

In UniFi Network, you can also check the gateway's logs for any error messages related to the VPN client. Click the Logs (clipboard) icon, then check the "VPN" box to filter for VPN-related log entries.

== Explore further ==

=== Routing ===

UniFi Network does not automatically route traffic through the VPN tunnel. You can create a “Policy-based Route” that directs traffic to the tunnel based on criteria like source IP address or destination IP address. For example, you could create a policy that sends all traffic through the tunnel, or only traffic destined for 44Net IP addresses.

=== Subnets ===

With just a tunnel configured, the gateway will use NAT to send traffic from your network through the tunnel. If you want to use 44Net IP addresses directly on devices in your network, you can request a subnet from 44Net Connect and configure it in UniFi Network.

# In the 44Net Connect dashboard, request a Network Allocation.
# Once the allocation is approved, note the IPv4 subnet assigned to you.
# In UniFi Network, go to '''Settings''' > '''Networks''' and create a new network.
# Un-check '''Auto Scale Network'''.
# In the IPv4 Address field, enter the first address in the assigned subnet. For example, if your assigned subnet is 44.27.30.'''112'''/29, enter 44.27.30.'''113'''.
# In the '''Netmask''' field, enter the prefix length for the assigned subnet. For example, if your assigned subnet is a '''/29''', choose '''29'''.
# In the '''VLAN ID''' field, enter any VLAN ID not already in use on your gateway. You can accept the suggested VLAN ID or choose a different one.
# You can accept the '''Auto''' settings provided, or click '''Manual''' and adjust DHCP and other settings as needed.
# Click '''Create''' to create the network.

To route traffic from this subnet through the tunnel, create a policy-based route that matches the new subnet as the source and the VPN client as the next hop.

To use this Network/VLAN for devices in your local network, connect them to the new VLAN you created. This can be done by configuring switch ports or Wi-Fi networks to use this Network as the “native” network, or by configuring devices on your LAN to use this Network’s VLAN ID.

For more configuration options and details, see the UniFi Network documentation:

* [https://help.ui.com/hc/en-us/articles/9761080275607-Creating-Virtual-Networks-VLANs Networks and VLANs]
* [https://help.ui.com/hc/en-us/articles/12566175125783-UniFi-Gateway-Policy-Based-Routing Policy-Based Routing]
* [https://help.ui.com/hc/en-us/articles/5546542486551-Traffic-Policy-Management-in-UniFi Firewall and Traffic Policies] (including allowing traffic from the Internet to your 44Net subnet)

== Related pages ==

* [[44Net Connect|44Net Connect overview]]
* [[44Net Connect/Quick Start|44Net Connect Quick Start]]
* [[44Net Connect/Supported Platforms|44Net Connect Supported Platforms]]
* [[GetStarted|Get Started]]

[[Category:Participation Methods]]
[[Category:44Net Connect]]
[[Category:Getting Started]]

Community

2026-04-15T15:40:38Z

KI5QKX: mw push

{{DISPLAYTITLE:Community}}

This page explains how 44Net works as a community of operators, maintainers, and contributors.
It is also a directory of the main places where people ask questions, coordinate changes, and stay in touch.

If you are blocked right now and want the most direct support entry point, start with [[Get Help]].

== What we mean by “community” ==

More than just a block of IP addresses, 44Net is also a long-running technical community.

Much of the operational knowledge that keeps 44Net usable lives in the experience of the people who run it, troubleshoot it, write documentation, maintain software tools, and help newcomers get unstuck. The mailing lists and discussion groups are where that knowledge is developed and shared.

Asking for help is one of the first ways people join the community. As with amateur radio, asking questions and helping one another is how people learn about how things work and eventually go on to help the next person.

== Where to ask questions ==

For most 44Net technical questions, start here:

* [https://ardc.groups.io/g/44net ARDC 44Net discussion group]

This is the main public forum for:

* Setup questions that go beyond the documented quick starts
* Troubleshooting odd routing, NAT, DNS, or platform-specific behavior
* Discussing proposed documentation changes or shared operational practices
* Sharing working examples, lessons learned, and project writeups

Note that administrative issues like account access, verification, or requests that depend on Portal workflow should generally go through the [https://portal.ampr.org/ Portal ticket system] instead of the discussion group.

== Groups.io and discussion channels ==

ARDC maintains a Groups.io presence with multiple public subgroups. The most relevant ones for 44Net readers are:

* [https://ardc.groups.io/g/main ARDC Main]: low-volume announcements and broad ARDC updates
* [https://ardc.groups.io/g/44net 44Net]: the main 44Net discussion group for setup, troubleshooting, and operations
* [https://ardc.groups.io/g/44Net-connect 44Net Connect]: discussions specifically about the 44Net Connect project
* [https://ardc.groups.io/g/community ARDC Community]: broader discussion about ARDC and its work ''not related to 44Net''
* [https://ardc.groups.io/g/44net-vpn ARDC 44Net VPN]: discussion related to VPN-style access systems ''not specifically related to 44Net Connect''
* [https://ardc.groups.io/g/developer-community ARDC Developer Community]: discussion related to software development and open source projects supported by ARDC
* [https://ardc.groups.io/g/wiki ARDC Wiki]: discussion related to the wiki and documentation work

There are other groups related to the grants program, committees, and more. See the [https://ardc.groups.io/ ARDC Groups.io directory] for a full list.

== Social and other community resources ==

Official ARDC channels and resources that may be useful:

* [https://www.ardc.net/44net/ ARDC 44Net page]
* [https://www.ardc.net/about/contact/ ARDC contact page]
* [https://mastodon.hams.social/@ARDC Mastodon]
* [https://bsky.app/profile/ardc-73.bsky.social Bluesky]
* [https://twitter.com/ardc_73 Twitter / X]
* [https://www.facebook.com/ardc.73 Facebook]
* [https://www.linkedin.com/company/amateur-radio-digital-communications/ LinkedIn]
* [https://www.youtube.com/@ARDC73 YouTube]
* [https://vimeo.com/ardc73 Vimeo]

Other useful entry points:

* [[Get Help]]
* [[GetStarted|Getting started]]
* [[What People Build|What People Build]]
* [[Contributing|Contributing]]
* [[44Net mailing list]] for historical context and legacy list references

== Community norms ==

Fundamentally, 44Net is a federation of technical operators who share a common interest in building and maintaining non-commercial, community-run network infrastructure. The community is generally welcoming and supportive of newcomers, and encourages people to ask questions, share their experiences, and contribute in whatever way they can.

There is no one project that constitutes all of 44Net. It is not just RF networks, or just tunnels, or just a specific set of services. It is a collection of different activities that all contribute to the overall ecosystem. This range of disparate efforts is part of what makes the community interesting.

=== Asking questions ===

When asking a question, it’s helpful to be as specific as possible about the problem you’re facing and what you’ve already tried. This can help others understand your situation and provide more targeted advice.

For example, instead of asking “Why isn’t my tunnel working?”, you might say “I’m trying to set up a WireGuard tunnel on my Linux server using the configuration from the 44Net dashboard, but I’m getting an error message that says “Configuration Invalid”. I’ve checked that the private key is correct and that the config works on another device, but I’m still stuck. Has anyone seen this before?”

When asking a technical question, the following information is often helpful to include:

* Which operating model you are using: IPIP Mesh, BGP, or 44Net Connect
* What platform or device you are using, such as a specific router, Linux distribution, or cloud provider
* The exact step that failed
* Any error messages or unexpected behavior you observed
* Anything you have already tried

=== Sharing knowledge and experience ===

When sharing a project writeup or lesson learned, consider how it might be useful to others in the community. Include details about your setup, what worked well, and any challenges you faced. This can help others understand how your experience might apply to their own situation.

For example, instead of saying “I got it working by doing X”, you might say “I was able to get my WireGuard tunnel working on my Raspberry Pi by following the instructions in the 44Net Connect quick start guide, but I had to make a few adjustments. I had to change the MTU setting to 1380 because I was experiencing packet loss with the default MTU of 1420. I also had to make sure that my firewall was allowing traffic on the WireGuard port. Once I made those changes, everything started working smoothly.”

=== Collaboration and feedback ===

The projects that tend to succeed are those that focus on solving a specific problem, and that are open to collaboration and feedback from others. Projects that are less open to collaboration, that hold strict expectations for how things should be done, or that try to represent themselves as the “one true way” to do something, tend to be less successful and less well-received by the community.

For these reasons and more, it’s ''pragmatic'' to be respectful and considerate of others and to focus on the problem at hand and how to solve it, rather than on personal opinions or preferences.

Attempts to gatekeep or exclude certain types of participation are generally avoided and discouraged, except when bad-faith behavior or harm is involved. The community generally seeks to preserve and protect healthy, constructive, non-disruptive activity.

== Contributing ==

ARDC staff help produce documentation and maintain software tools, but the community is what keeps 44Net running and usable. If you have a question, ask it. If you have an answer, share it. If you have a project writeup or lesson learned, post it.

If a recurring question appears on the mailing list, consider converting the answer into a short wiki update; see [[Contributing]] for guidance. This can help keep operational guidance searchable and reduce repeated troubleshooting cycles.

=== Note on licensing ===

Material produced by ARDC staff is generally released under a Creative Commons Attribution-ShareAlike license ([https://creativecommons.org/licenses/by-sa/3.0/ CC-BY-SA]) or the non-commercial variant. These licenses are designed to encourage sharing and collaboration, while also giving credit to the original creators. Others may publish material under different licenses or according to different terms, as is their right, but if such terms are not compatible with the CC-BY-SA license, that material should not be posted to this wiki.

== Related pages ==
* [[Get Help]]
* [[GetStarted|Getting started]]
* [[Provisioning Methods|Provisioning Methods]]
* [[What People Build|What People Build]]
* [[Contributing|Contributing]]
* [[Governance|Governance]]
* [[Policies|Policies]]

== Older docs and notes ==
Earlier pages that may still be useful:
* [[44Net mailing list]]
* [[Re: 44Net Digest, Vol 3, Issue 96]]
* [[K2IE]]
* [[ARDC]]
* [[Ampr.org]]
* See [[Archive]] for more.
[[Category:Community]]

44Net Connect

2026-03-05T13:06:55Z

KI5QKX: mw push

{{DISPLAYTITLE:Start Using 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 a transport, but it is not a privacy VPN. You are not logging in to a service; you are provisioning 44Net onto your system for public-Internet participation. The purpose of the tunnel is to carry your traffic to a point of presence. Your system can participate as a public network host.

{{SectionFigure|file=44Net_Connect_overview.png|caption=44Net Connect makes the 44Net addresses on your devices appear on the public Internet.}}

{{Section|
{{SectionCard|
New to Connect? Jump straight to the step‑by‑step setup guide:

[[44Net Connect/Quick Start|→ 44Net Connect Quick Start]]

You can return here later to learn how Connect works in more detail.
}}
}}

== 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

== Future development ==

Ongoing work includes:

* Additional endpoint regions
* Volunteer-hosted nodes
* Deeper integration with Portal services

== Getting started ==

You can set up 44Net on your device in just a few minutes:

* [[44Net Connect/Quick Start|Start the Quick Start Guide]]

== Related pages ==

* [[Portal]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]

44Net Connect

2026-03-05T13:03:59Z

KI5QKX: mw push

{{DISPLAYTITLE:Start Using 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 a transport, but it is not a privacy VPN. You are not logging in to a service; you are provisioning 44Net onto your system for public-Internet participation. The purpose of the tunnel is to carry your traffic to a point of presence. Your system can participate as a public network host.

{{SectionFigure|file=44Net_Connect_overview.png|caption=44Net Connect makes the 44Net addresses on your devices appear on the public Internet.}}

{{Section|
{{SectionCard|
New to Connect? Jump straight to the step‑by‑step setup guide:

[[44Net Connect/Quick Start|→ 44Net Connect Quick Start]]

You can return here later to learn how Connect works in more detail.
}}
}}

== 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 ==

{| class="wikitable"
! 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 44Net on your device in just a few minutes:

* [[44Net Connect/Quick Start|Start the Quick Start Guide]]

== Related pages ==

* [[Portal]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]

About This Documentation

2026-03-05T04:42:12Z

KI5QKX: mw push

This page explains how the 44Net wiki is proposed to work and how contributors can think about adding or improving documentation.

It aims to describe the assumptions behind the structure you see here.

Other documentation systems approach organization with folders and hierarchies. With MediaWiki, the hierarchy is flat, and structure emerges through navigation, linking, categories, and templates. This wiki embraces that approach, organizing around a small number of essential concepts and leaving it to the editors to link pages together in a way that makes sense for each topic.

== Purpose of the Wiki ==

The 44Net wiki exists to help people:

* Understand what 44Net is and why it exists
* Find ways to participate
* Build projects and services
* Collaborate in stewarding the community

The ultimate goal is to promote participation by promoting understanding. Along the way, we want to help the reader feel more competent ''and'' more confident about building with 44Net.

Pages in this wiki apply two dimensions of structure:

{| class="wikitable"
! Dimension !! Question
|-
| Conceptual Element || What part of the 44Net world is this about?
|-
| Page Archetype || What is this page trying to do for the reader?
|}

Conceptual Element + Page Archetype = A Page.

Here are more details about each of these dimensions.

== The conceptual elements ==

With MediaWiki’s facilities for categorization and navigation, we don’t need a strict taxonomy from the outset. Still, there are a few general conceptual categories that are important to the sustainability of the 44Net program and that should be reflected in the documentation.

{| class="wikitable"
! Conceptual Element !! Core Question !! Typical Content
|-
| About 44Net || What is 44Net? || Explanations, history, core ideas
|-
| Provisioning || How does 44Net become available? || Methods, onboarding, setup guides
|-
| Use Cases || What do people do with 44Net? || Project examples, inspiration, applications
|-
| Applications || What tools support 44Net? || Portal docs, dashboards, software usage
|-
| Community || How is 44Net stewarded? || Governance, policy, collaboration
|}

; About 44Net
: Orientation and explanation of what 44Net is, in and of itself. This includes history, context, and the core concepts that define 44Net as a thing. This is probably a mix of philosophical, observational, and slightly technical material.

; Provisioning
: How participants actually put 44Net subnets or IP addresses on their devices or networks. This would include general explainers as well as practical, step‑by‑step instructions.

; Use Cases
: “Use cases,” meaning things people ''do'' with 44Net. The point is to help people envision what they too could do with 44Net by showing them what others have done. This is probably a mix of inspirational and practical material.

; Applications
: Conceptual and practical documentation related to tools that make 44Net work. This includes the Portal, the 44Net Connect dashboard, `ampr-ripd`, etc. This is ”open this, click that” type documentation for tools that are unique to 44Net.

; Community
: Governance, policy, collaboration, and stewardship. How 44Net is managed, how decisions are made, and how volunteers can get involved. This includes rules of the road and “how to be a good citizen,” but also info about the mailing lists and how to get involved in the community.

Documents that fall outside these categories are not necessarily out of scope. The point is, we want to be sure to cover at least these kinds of things.

Moreover, the structure should emerge from the content, not the other way around.

{{Note|The term “Provisioning” is used intentionally. Participants are not connecting to a single centralized network, so language about “connecting” can be misleading. People don’t exactly dial up to something, rather they ''provision 44Net resources onto systems and networks they operate.'' This more accurately reflects 44Net’s distributed nature. It also helps avoid confusion with the thing named “44Net Connect,” which is ''one way'' to provision 44Net but not the ''only way''.}}

If there is an overarching organizing principle, it might be this: ''Organize around aspects of people’s experiences.'' What do they want to do? What are they working with? How can we help? This helps keep it more user‑centric than technology‑centric. We want to serve the people who are trying to use 44Net, rather than just describing technology for its own sake.

== Page archetypes ==

The wiki generally adopts a handful of recognizable types of pages. Being deliberate about the type of page you are writing can help focus the material, and following recognizable patterns gives the reader helpful clues that reduce cognitive load, making the material easier to understand.

{| class="wikitable"
! Page Archetype !! Reader Intent !! Primary Goal
|-
| Concept Page || Understand || Build shared mental models
|-
| How-To Guide || Do || Enable successful action
|-
| Reference Page || Look up || Provide authoritative detail
|-
| Orientation / Landing Page || Decide || Guide navigation and discovery
|-
| Project Page || Explore || Show real-world examples
|-
| Stewardship Page || Participate responsibly || Explain governance and expectations
|}

=== Concept page ===
Explains what something is and why it exists. Demystifies something. These pages provide overviews and introduce ideas. They are not step‑by‑step instructions, but they might include examples and links to related procedures.

Reader intent: ''Help me understand this.''

==== Examples ====
* [[44Net Connect]]
* [[IPIP Mesh]]
* [[BGP|BGP on 44Net]]
* [[DNS|DNS within 44Net]]

==== Characteristics ====
* Narrative explanation
* Framing and context
* Relationships to other concepts
* Links to related how-to guides and reference material

Concept pages are interpretive more than instructional.

=== How‑to guide ===
Help someone accomplish a specific task with a clear successful outcome. This is where step-by-step instructions with annotated screenshots go.

Reader intent: ''I want to do this thing.''

==== Examples ====
* [[44Net Connect/Quick Start|44Net Connect Quick Start]]
* [[Portal/Sign Up|Create a Portal account and verify your callsign]]

==== Characteristics ====
* One goal per guide
* Clear, sequential steps
* Observable indicators of success

If a reader cannot successfully complete the task by following the steps on the page, the guide is unfinished, regardless of how well it is written.

=== Reference page ===
Provide authoritative “look it up” type information.

Reader intent: ''I need some details.''

==== Examples ====
* API documentation
* Technical specifications
* Policy requirements

==== Characteristics ====
* Precise
* Structured
* Non-linear

Reference pages are meant to be consulted as needed.

=== Orientation or landing page ===
Help readers understand a topic and decide where to go next.

Examples:
* [[Main Page]]
* [[Provisioning Methods]]
* [[What People Build]]

These pages are like trailhead signposts. They should be welcoming and informative to help readers find what they need. ''Links'' to how-tos and references pages live here.

=== Project pages ===
Describe something a participant has built.

Reader intent: ''What is this thing I saw someone doing with 44Net?''

Purpose:
* Showcase real deployments
* Help demonstrate what’s possible
* Inspire others to join a project or start one of their own
* Link outward to active work, code repositories, documentation, Discord, etc.

Like [https://qrz.com QRZ], but for 44Net projects.

=== Stewardship pages ===
Describe how the community is supported and maintained.

Examples:
* [[Policies]]
* [[Volunteer|Volunteer Roles]]
* [[Verification|How Verification Works]]

At heart, stewardship pages are about what community members expect of one another and how the community works together.

== Editorial discipline ==

Two types of pages are especially important to 44Net’s mission and deserve special care: Concept Pages and How‑To Guides.

=== Concept pages must be clear ===
A reader should leave able to answer:
* What is this?
* Why does it exist?
* Why would I use it?
* How does it fit into the bigger picture?

Concept pages are more like Wikipedia articles than user manuals. They should help readers form mental models, provide context, and give background or framing to practical instructions found elsewhere.

=== How‑to guides must work ===
A guide succeeds only if a reader can complete the task.

Every How‑To should include:
* A statement of the goal
* Prerequisites
* Sequential steps, with screenshots and other resources as needed
* A verification step allowing the reader to confirm they have succeeded
* Links back to the related concept page
* Links to related articles that answer “Great, so what’s next?”

== Deciding where a page goes ==

Although the wiki is generally flat, “folder structure” can help ''maintainers'' by keeping related pages together. For example, all documentation related to the Portal application lives under the “Portal/” prefix.

{{Note|This is not for navigation purposes or for the reader’s benefit. The reader will use links and categories to find their way around. Any folder structure is for the maintainers’ benefit, to help them find and manage related pages.}}

Also, this is not a hard rule, just a helpful convention.

When unsure where a page belongs, try the ownership rule:

''Place the page under the concept that would feel incomplete if the page disappeared.''

Examples:
; '''Portal''' DNS management → ''Portal/DNS''
: If the documentation on the Portal’s DNS functions disappeared, people would not know how to manage their DNS records. The Portal documentation would therefore be incomplete without it, so it belongs under the Portal/.

; DNS delegation '''in general''' → ''DNS/Delegation''
: If the documentation on DNS delegation disappeared, people would would struggle to understand DNS delegation. The DNS documentation would therefore be incomplete without it, so it belongs under DNS/.

When starting a new page or group of pages, ask yourself: am I documenting a new concept that deserves its own top-level page, or am I creating concept/how-to/reference documentation for an existing concept? If the former, create a new top-level page. If the latter, place it under the existing concept.

== Categories over hierarchy ==

So MediaWiki does not actually track pages in folders. What is its native way to organize pages? Categories and links.

Categories provide the multidimensional organization that paths alone cannot. A page can belong to multiple categories, and categories can be nested. This allows for more flexible organization and navigation than a strict hierarchy.

Contributors should add categories rather than restructuring page paths.

Contributors should also use categories liberally. If a page belongs to a category, it should be in that category. If it belongs to multiple categories, it should be in all of them.

== Navigation philosophy ==

Readers rarely browse the wiki as a directory tree.

They experience it through:
* the Main Page
* topic landing pages
* contextual links
* search results

The goal is discoverability: perfect hierarchy is less important than reliable navigation. Pages may move over time, but clarity for readers must be maintained.

== An invitation ==

The 44Net wiki is part of the commons it describes.

Its structure will continue to evolve as participants build, document, and teach one another. Contributors are encouraged to improve explanations, refine navigation, and leave the next reader slightly less confused than they were when they arrived.

Good documentation here will pretty much always be ongoing, unfinished work in progress.
[[Category:Documentation]]

44Net Connect

2026-03-05T04:34:14Z

KI5QKX:

{{DISPLAYTITLE:Start Using 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 a transport, but it is not a privacy VPN. You are not logging in to a service; you are provisioning 44Net onto your system for public-Internet participation. The purpose of the tunnel is to carry your traffic to a point of presence. Your system can participate as a public network host.

{{SectionFigure|file=44Net_Connect_overview.png|caption=44Net Connect makes the 44Net addresses on your devices appear on the public Internet.}}

{{Section|
{{SectionCard|
New to Connect? Jump straight to the step‑by‑step setup guide:

[[44Net Connect/Quick Start|→ 44Net Connect Quick Start]]

You can return here later to learn how Connect works in more detail.
}}
}}

== 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 ==

{| class="wikitable"
! 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 44Net on your device in just a few minutes:

* [[44Net Connect/Quick Start|Start the Quick Start Guide]]

== Related pages ==

* [[Portal]]
* [[Address Allocations]]
* [[Routing 44Net]]
* [[Mesh Networking]]
* [[Getting Started with 44Net]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]

44Net Connect

2026-03-05T04:28:50Z

KI5QKX: mw push

{{DISPLAYTITLE:Start Using 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 provisioning 44Net onto your system for public-Internet participation. The purpose of the tunnel is to carry your traffic to a point of presence. Your system can participate as a public network host.

{{SectionFigure|file=44Net_Connect_overview.png|caption=44Net Connect makes the 44Net addresses on your devices appear on the public Internet.}}

{{Section|
{{SectionCard|
New to Connect? Jump straight to the step‑by‑step setup guide:

[[44Net Connect/Quick Start|→ 44Net Connect Quick Start]]

You can return here later to learn how Connect works in more detail.
}}
}}

== 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 ==

{| class="wikitable"
! 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 44Net on your device in just a few minutes:

* [[44Net Connect/Quick Start|Start the Quick Start Guide]]

== Related pages ==

* [[Portal]]
* [[Address Allocations]]
* [[Routing 44Net]]
* [[Mesh Networking]]
* [[Getting Started with 44Net]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]

File:44Net Connect overview.png

2026-03-04T23:42:31Z

KI5QKX:

44Net Connect

2026-03-04T23:41:32Z

KI5QKX: mw push

{{DISPLAYTITLE:Start Using 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 provisioning 44Net onto your system for public-Internet participation. The purpose of the tunnel is to carry your traffic to a point of presence. Your system can participate as a public network host.

{{Section|
{{SectionCard|
New to Connect? Jump straight to the step‑by‑step setup guide:

[[44Net Connect/Quick Start|→ 44Net Connect Quick Start]]

You can return here later to learn how Connect works in more detail.
}}
}}

{{SectionFigure|file=44Net_Connect_overview.png|width=100%|caption=44Net Connect makes the 44Net addresses on your devices appear on the public Internet.}}

== 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 ==

{| class="wikitable"
! 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 44Net on your device in just a few minutes:

* [[44Net Connect/Quick Start|Start the Quick Start Guide]]

== Related pages ==

* [[Portal]]
* [[Address Allocations]]
* [[Routing 44Net]]
* [[Mesh Networking]]
* [[Getting Started with 44Net]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]

44Net Connect

2026-03-04T21:50:38Z

KI5QKX:

{{DISPLAYTITLE:Start Using 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 provisioning 44Net onto your system for public-Internet participation. The purpose of the tunnel is to carry your traffic to a point of presence. Your system can participate as a public network host.

{{Section|
{{SectionCard|
New to Connect? Jump straight to the step‑by‑step setup guide:

[[44Net Connect/Quick Start|→ 44Net Connect Quick Start]]

You can return here later to learn how Connect works in more detail.
}}
}}

== 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 ==

{| class="wikitable"
! 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 44Net on your device in just a few minutes:

* [[44Net Connect/Quick Start|Start the Quick Start Guide]]

== Related pages ==

* [[Portal]]
* [[Address Allocations]]
* [[Routing 44Net]]
* [[Mesh Networking]]
* [[Getting Started with 44Net]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]

44Net Connect

2026-03-04T21:50:24Z

KI5QKX:

{{DISPLAYTITLE:Start Using 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 provisioning 44Net onto your system for public-Internet participation. The purpose of the tunnel is to carry your traffic to a point of presence. Your system can participate as a public network host.

{{Section|
{{SectionCard|
New to Connect? Jump straight to the step‑by‑step setup guide:

[[44Net Connect/Quick Start|→ 44Net Connect Quick Start]]

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|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 ==

{| class="wikitable"
! 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 44Net on your device in just a few minutes:

* [[44Net Connect/Quick Start|Start the Quick Start Guide]]

== Related pages ==

* [[Portal]]
* [[Address Allocations]]
* [[Routing 44Net]]
* [[Mesh Networking]]
* [[Getting Started with 44Net]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]

Roles and Participation

2026-03-01T01:14:42Z

KI5QKX: mw push

{{DISPLAYTITLE:Roles and Participation in 44Net}}

44Net is not operated entirely by a single organization alone. It exists through a combination of governance, stewardship, technical advice, and community participation. This page provides an overview of the primary roles that support and sustain the network.

== Governance ==
; [[Board of Directors (ARDC)|ARDC Board of Directors]]
: Provides organizational governance and fiduciary oversight.

== Stewardship and operations ==
; [[Staff (ARDC)|ARDC Staff]]
: Responsible for day-to-day operation of the 44Net program and infrastructure coordination.

== Technical advisory ==
; [[TAC|Technical Advisory Committee (TAC)]]
: Provides technical guidance and recommendations.

== Regional coordination ==
; [[Regional Coordinator|Regional Coordinators]]
: Support local participants, allocations, and community development.

== Community participation ==
44Net participants contribute in many ways, including:
* Operating subnets and experimental networks
* Building IPIP mesh links or routing infrastructure
* Running services and applications on 44Net
* Contributing documentation, tools, and technical expertise
* Supporting local and regional amateur radio networking efforts

Participation in 44Net is voluntary and decentralized. Individuals and groups engage in many different modes, from personal experimentation to operating shared infrastructure.

== Related pages ==
* [[About 44Net]]
* [[Provisioning Methods]]
* [[Technical Advisory Committee (TAC)]]
[[Category:Governance]]

IPIP Mesh

2026-03-01T01:14:38Z

KI5QKX: mw push

{{DISPLAYTITLE:IPIP Mesh (Stub)}}

== What this page is ==
This is an overview stub for the IPIP Mesh participation model on 44Net.
For setup steps, start with [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]].

== Start here ==
* [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]]
* [[Provisioning Methods|Provisioning Methods]]
* [[GetStarted|Getting started]]
* [[Routing|Routing and connectivity]]
* [[Community|Community and mailing lists]]

== What this page will cover ==
* What the IPIP Mesh model is and where it fits.
* Peering and topology expectations for mesh participants.
* Operational responsibilities in shared routing environments.
* Common validation and troubleshooting workflows.

== Related pages ==
* [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]]
* [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]]
* [[Provisioning Methods|Provisioning Methods]]
* [[Contributing|Contributing]]

== Contribute / next steps ==
If you run an IPIP Mesh node and can share practical guidance, please contribute through [[Contributing]] so this stub can be expanded into a full reference page.
[[Category:Participation Methods]]
[[Category:IPIP Mesh]]

BGP

2026-03-01T01:14:38Z

KI5QKX: mw push

{{DISPLAYTITLE:BGP (Stub)}}

== What this page is ==
This is an overview stub for BGP-based 44Net participation.
For setup steps, start with [[BGP/Quick Start|BGP Quick Start]].

== Start here ==
* [[BGP/Quick Start|BGP Quick Start]]
* [[Provisioning Methods|Provisioning Methods]]
* [[GetStarted|Getting started]]
* [[Routing|Routing and connectivity]]
* [[Policies|Policies]]
* [[Community|Community and mailing lists]]

== What this page will cover ==
* Where BGP participation fits in 44Net.
* Prerequisites such as routing policy and edge design.
* BGP operational responsibilities and filtering expectations.
* Validation, monitoring, and rollback practices.

== Related pages ==
* [[BGP/Quick Start|BGP Quick Start]]
* [[Routing your allocation via BGP]]
* [[Announcing your allocation directly]]
* [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]]
* [[Provisioning Methods|Provisioning Methods]]
* [[Contributing|Contributing]]

== Contribute / next steps ==
If you operate a BGP deployment on 44Net and can share a proven approach, contribute through [[Contributing]] so this stub can be expanded into a full reference page.
[[Category:Participation Methods]]
[[Category:BGP]]
[[Category:Infrastructure]]
[[Category:Routing]]

Decentralization

2026-03-01T01:14:38Z

KI5QKX: mw push

{{DISPLAYTITLE: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|BGP announcements]] ===
* Independently operated networks announce their own 44Net prefixes
* Requires upstream connectivity and an {{Term|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.

== See also ==

* [[44Net Connect]]
* [[IPIP Mesh]]
* [[BGP]]
* [[Provisioning Methods]]

About This Documentation

2026-03-01T01:14:36Z

KI5QKX: mw push

Routing

2026-03-01T01:14:35Z

KI5QKX: mw push

{{DISPLAYTITLE:Routing}}

== What this page is ==
This page is the routing orientation hub for 44Net participation.
Use it to understand how traffic reaches your systems across Connect, mesh, or BGP-operated networks.
For a conceptual overview of why these methods are separate, see [[Decentralization]].

== What you can do today ==
* Pick the operating model that matches your environment in [[Provisioning Methods|Provisioning Methods]].
* For fast single-endpoint onboarding, use [[44Net Connect/Quick Start|44Net Connect Quick Start]].
* For shared routing environments, review [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]] orientation.
* For independently routed infrastructure, review [[BGP/Quick Start|BGP Quick Start]] orientation.
* Confirm address and naming prerequisites in [[Portal/Request Address Space|Request Address Space]] and [[DNS|DNS]].

== What this page will cover ==
* Core routing concepts used by 44Net operators.
* Traffic flow patterns: behind NAT, shared gateways, and BGP edges.
* Prefix planning and route advertisement boundaries.
* Troubleshooting methodology for reachability and asymmetry.
* Operational checklists for changes and rollback.

== Related pages ==
* [[Provisioning Methods|Provisioning Methods]]
* [[44Net Connect|44Net Connect overview]]
* [[44Net Connect/Quick Start|44Net Connect Quick Start]]
* [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]]
* [[BGP/Quick Start|BGP Quick Start]]
* [[Portal/Request Address Space|Request Address Space]]
* [[DNS|DNS and naming]]
* [[Community|Community and mailing lists]]
* [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]]

== Contribute / next steps ==
If you troubleshoot a routing issue, document topology, path expectation, observed path, and fix. Submit concise incident notes through [[Contributing]] so this page can grow into a practical reference.

== Older docs and notes ==
Earlier pages that may still be useful:
* [[RIP]]
* [[Filtering RFC1918 Addresses]]
* [[Firewalls]]
* [[Ipv6]]
* [[Networks that use 44Net]]
* [[Routing your allocation via BGP]]
* [[Announcing your allocation directly]]
* See [[Archive]] for more.
[[Category:Infrastructure]]
[[Category:Routing]]

Portal/Introduction

2026-03-01T01:14:35Z

KI5QKX: mw push

{{DISPLAYTITLE:Portal Introduction}}

== What this page is ==
This page introduces what the 44Net Portal is used for after sign-up.
It helps operators understand which tasks happen in the Portal and which happen on their own infrastructure.

== What you can do today ==
* Complete account setup in [[Portal/Sign Up|Portal Sign Up]].
* Use [[GetStarted|Getting started]] to pick your connection model first.
* Use current DNS workflow in [[DNS/Portal/Subdomains|Claiming DNS]].
* Track address request flow in [[Portal/Request Address Space|Request Address Space]].

== What this page will cover ==
* Portal sections and what each one controls.
* Account/profile basics relevant to operations.
* Request workflows for address space and DNS.
* Verification state and common blockers.
* Hand-off points from Portal actions to deployment tasks.

== Related pages ==
* [[Portal/Sign Up|Portal Sign Up]]
* [[Portal/Request Address Space|Request Address Space]]
* [[DNS/Portal/Subdomains|Claiming DNS]]
* [[GetStarted|Getting started]]
* [[Provisioning Methods|Provisioning Methods]]
* [[Community|Community and mailing lists]]

== Contribute / next steps ==
If Portal screens or flow change, update this page with what moved and why. Keep screenshots and labels aligned so operators can map docs to the current interface.

== Older docs and notes ==
Earlier pages that may still be useful:
* [[Portal intro]]
* [[Portal Call Sign Verification]]
* [[Organizations in the Portal]]
* [[How Organizations Work on the Portal]]
* [[Approving Small Subnets on the Portal]]
* [[Verification]]
* See [[Archive]] for more.
[[Category:Portal]]
[[Category:Portal Workflows]]

IPIP Mesh/Quick Start

2026-03-01T01:14:34Z

KI5QKX: mw push

{{DISPLAYTITLE:IPIP Mesh Quick Start (Stub)}}

== What this page is ==
This is an orientation stub for joining the shared IPIP Mesh model on 44Net.
A full quick start procedure is not published yet.

== What you can do today ==
* Confirm that a shared mesh model fits your goals in [[Provisioning Methods|Provisioning Methods]].
* Complete account and verification prerequisites in [[GetStarted|Getting started]] and [[Portal/Sign Up|Portal Sign Up]].
* Identify local or regional peers and gateway expectations via [[Community|Community and mailing lists]].
* Review routing responsibilities in [[Routing|Routing and connectivity]].

== What this page will cover ==
* Prerequisites for mesh participation and peering.
* Endpoint setup expectations and addressing model.
* Shared gateway behavior and traffic flow patterns.
* Operational coordination with regional maintainers.
* Validation and troubleshooting checklist.

== Related pages ==
* [[Provisioning Methods|Provisioning Methods]]
* [[GetStarted|Getting started]]
* [[Routing|Routing and connectivity]]
* [[Community|Community and mailing lists]]
* [[Portal/Request Address Space|Request Address Space]]
* [[Contributing|Contributing]]
* [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]]

== Contribute / next steps ==
If you already operate in the mesh, contribute a minimal reproducible setup path with topology notes and failure modes. Submit through [[Contributing]] so this stub can become a complete Quick Start.

== Older docs and notes ==
Earlier pages that may still be useful:
* [[Gateway]]
* [[Registering Your Gateway]]
* [[Encap.txt]]
* [[Encap.txt/get-encap]]
* [[Rip44d]]
* [[RIP44.lua]]
* [[Amprgw]]
* [[Ampr-ripd]]
* [[Setting up a gateway on Linux]]
* See [[Archive]] for more.
[[Category:Participation Methods]]
[[Category:IPIP Mesh]]
[[Category:Getting Started]]

Eligibility

2026-03-01T01:14:33Z

KI5QKX: mw push

{{DISPLAYTITLE:Eligibility}}

== What this page is ==
This page explains who can participate in 44Net and what prerequisites are commonly required.
Use it before requesting address space or joining shared infrastructure.

== What you can do today ==
* Complete account and callsign verification steps in [[Portal/Sign Up|Portal Sign Up]].
* Read participation framing in [[About 44Net|About 44Net]].
* Choose a technical path in [[Provisioning Methods|Provisioning Methods]] based on your operating environment.
* Ask edge-case questions in [[Community|Community and mailing lists]].

== What this page will cover ==
* Baseline participant requirements.
* Callsign verification expectations and exceptions.
* Project vs individual participation patterns.
* Operational responsibilities after receiving resources.
* Links to authoritative policy text.

== Related pages ==
* [[Portal/Sign Up|Portal Sign Up]]
* [[GetStarted|Getting started]]
* [[About 44Net|About 44Net]]
* [[Policies|Policies]]
* [[Governance|Governance]]
* [[Community|Community and mailing lists]]

== Contribute / next steps ==
If you encounter an eligibility scenario not covered here, document the exact context and outcome through [[Contributing]]. That helps convert informal answers into durable guidance.

== Older docs and notes ==
Earlier pages that may still be useful:
* [[Verification]]
* [[Portal Call Sign Verification]]
* [[Organizations in the Portal]]
* [[How Organizations Work on the Portal]]
* See [[Archive]] for more.
[[Category:Portal]]
[[Category:Governance]]
[[Category:Policy]]

Contributing

2026-03-01T01:14:33Z

KI5QKX: mw push

{{DISPLAYTITLE:Contributing}}

== What this page is ==
This page explains how to contribute useful work to 44Net docs and operations.
It is for operators, maintainers, and new participants who want to help.

== What you can do today ==
* Start by identifying a specific gap from [[GetStarted|Getting started]] or [[Provisioning Methods|Provisioning Methods]].
* Share proposed changes in [[Community|Community and mailing lists]] before major edits.
* Prefer small, verifiable updates over broad rewrites.
* Add concrete context: device role, NAT posture, tunnel endpoint, routing behavior, and observed outcomes.

== What this page will cover ==
* Contribution workflow for wiki content.
* Standards for operational accuracy and scope.
* How to document procedures with rollback and safety notes.
* Review expectations for networking and policy content.
* Ownership and maintenance for long-lived pages.

== Related pages ==
* [[Community|Community and mailing lists]]
* [[Governance|Governance]]
* [[Policies|Policies]]
* [[What People Build|What People Build]]
* [[GetStarted|Getting started]]
* [[Routing|Routing and connectivity]]

== Contribute / next steps ==
When proposing edits, include the problem statement, what changed in real operation, and what remains unverified. That allows reviewers to approve updates without guessing intent or risk.
[[Category:Documentation]]

CommunityProjects

2026-03-01T01:14:33Z

KI5QKX: mw push

{{DISPLAYTITLE:Community Projects}}

== What this page is ==
This page is a landing point for shared projects run by multiple operators.
Use it to find active efforts where you can contribute technical work.

== What you can do today ==
* Browse examples on [[What People Build|What People Build]].
* Use [[Provisioning Methods|Provisioning Methods]] to pick a participation model that matches the project environment.
* Join discussion first in [[Community|Community and mailing lists]] before changing shared infrastructure.
* Track account prerequisites in [[GetStarted|Getting started]].

== What this page will cover ==
* Directory of active community projects and maintainers.
* Typical contribution roles (ops, docs, testing, monitoring).
* Dependency map: DNS, routing, gateways, and service ownership.
* Onboarding expectations for project contributors.
* Project lifecycle: launch, handoff, and archival.

== Related pages ==
* [[What People Build|What People Build]]
* [[Community|Community and mailing lists]]
* [[Contributing|Contributing]]
* [[GetStarted|Getting started]]
* [[DNS|DNS and naming]]
* [[Routing|Routing and connectivity]]

== Contribute / next steps ==
If you maintain a shared service, publish a short project profile with purpose, dependencies, contact point, and operational status. Submit updates through [[Contributing]] so others can join safely.
[[Category:Projects]]

Community

2026-03-01T01:14:32Z

KI5QKX: mw push

{{DISPLAYTITLE:Community}}

== What this page is ==
This page points to the places where 44Net operators ask questions, coordinate changes, and share results.
Use it when you need help, peer review, or operational context.

== What you can do today ==
* Join the [https://groups.io/g/ardc/44net ARDC 44Net discussion group].
* Read [[GetStarted|Getting started]] before posting setup questions.
* When asking for help, include topology basics (NAT, tunnel endpoint, routing method, and error symptoms).
* Cross-check your participation model in [[Provisioning Methods|Provisioning Methods]].

== What this page will cover ==
* Communication channels and expected use of each.
* How to ask effective technical questions.
* Change announcements and maintenance coordination.
* Community norms for troubleshooting and follow-up.
* Where to share project writeups and lessons learned.

== Related pages ==
* [[GetStarted|Getting started]]
* [[Provisioning Methods|Provisioning Methods]]
* [[What People Build|What People Build]]
* [[Contributing|Contributing]]
* [[Governance|Governance]]
* [[Policies|Policies]]

== Contribute / next steps ==
If a recurring question appears on the mailing list, convert the answer into a short wiki update and link it in [[Contributing]]. That keeps operational guidance searchable and reduces repeated troubleshooting cycles.

== Older docs and notes ==
Earlier pages that may still be useful:
* [[44Net mailing list]]
* [[Re: 44Net Digest, Vol 3, Issue 96]]
* [[K2IE]]
* [[ARDC]]
* [[Ampr.org]]
* See [[Archive]] for more.
[[Category:Community]]

BGP/Quick Start

2026-03-01T01:14:32Z

KI5QKX: mw push

{{DISPLAYTITLE:BGP Quick Start (Stub)}}

== What this page is ==
This is an orientation stub for BGP-based 44Net participation.
A full end-to-end quick start procedure is not published yet.

== What you can do today ==
* Use [[Provisioning Methods|Provisioning Methods]] to confirm BGP is the right operating model.
* Make sure your network already operates BGP-capable edge routing and has a stable tunnel or transit plan.
* Start account and eligibility prerequisites in [[GetStarted|Getting started]] and [[Portal/Sign Up|Portal Sign Up]].
* Review [[Routing|Routing and connectivity]] for routing concepts and decision points.
* Ask implementation questions in [[Community|Community and mailing lists]].

== What this page will cover ==
* Prerequisites: ASN, policy ownership, and upstream coordination.
* Address assignment scope and route advertisement boundaries.
* Session design, failover patterns, and filtering expectations.
* Validation and troubleshooting checklist.
* Operational hygiene for changes and incident response.

== Related pages ==
* [[Provisioning Methods|Provisioning Methods]]
* [[GetStarted|Getting started]]
* [[Routing|Routing and connectivity]]
* [[Portal/Request Address Space|Request Address Space]]
* [[Governance|Governance]]
* [[Policies|Policies]]
* [[Community|Community and mailing lists]]
* [[Decentralization|How Connect, IPIP Mesh, and BGP fit together]]

== Contribute / next steps ==
If you can share a proven deployment path, capture topology, BGP edge role, filtering assumptions, and rollback strategy. Add that material through [[Contributing]] so this stub can be upgraded to a real Quick Start.

== Older docs and notes ==
Earlier pages that may still be useful:
* [[Routing your allocation via BGP]]
* [[Announcing your allocation directly]]
* [[FAQ|Why can’t I announce my allocation directly?]]
* [[SWIP]]
* [[NSP Details]]
* See [[Archive]] for more.
[[Category:Participation Methods]]
[[Category:BGP]]
[[Category:Infrastructure]]
[[Category:Routing]]
[[Category:Getting Started]]

44Net Connect/Supported Platforms

2026-03-01T01:14:32Z

KI5QKX: mw push

{{DISPLAYTITLE:44Net Connect/Supported Platforms}}

== What this page is ==
This page lists platform support for 44Net Connect and who should use each option.
Use it when you need to choose a device, OS, or router for a tunnel endpoint.

== What you can do today ==
* Confirm baseline setup flow in [[44Net Connect/Quick Start|44Net Connect Quick Start]].
* Verify account and callsign status in [[GetStarted|Getting started]] and [[Portal/Sign Up|Portal Sign Up]].
* Check whether your target environment can run WireGuard before requesting production routing changes.
* If your platform is not documented yet, ask in the [https://groups.io/g/ardc/44net ARDC 44Net discussion group].

== What this page will cover ==
* Supported desktop operating systems and client choices.
* Supported router/firewall platforms and caveats behind NAT.
* Mobile platform status and operational limitations.
* Platform-specific notes for key handling and persistence.
* Known incompatibilities and current workarounds.

== Related pages ==
* [[44Net Connect/Quick Start|44Net Connect Quick Start]]
* [[44Net Connect|44Net Connect overview]]
* [[GetStarted|Getting started]]
* [[Provisioning Methods|Provisioning Methods]]
* [[Portal/Sign Up|Portal Sign Up]]
* [[Routing|Routing and connectivity]]
* [[Community|Community and mailing lists]]

== Contribute / next steps ==
If you operate a platform that works (or fails), document the exact OS/version, WireGuard client, NAT or firewall posture, and handshake behavior. Share those details in [[Contributing]] so this page can be updated with reproducible guidance.
[[Category:Participation Methods]]
[[Category:44Net Connect]]

About 44Net

2026-03-01T01:14:29Z

KI5QKX: mw push

{{DISPLAYTITLE:About 44Net}}

This page provides historical background and context. For onboarding and provisioning paths, start with [[GetStarted|Getting Started]], [[Provisioning Methods|Provisioning Methods]], and the [[Main Page]].

== What 44Net is and is not ==

44Net is shared technical infrastructure used and maintained by the people who participate in it. Participants operate systems on publicly routable IPv4 space, enabling projects that require stable addressing and Internet-visible services.

44Net is not a consumer ISP product or a managed hosting platform. Participants run and maintain their own systems, coordinate with one another, and contribute to the long-term health of the network.

== History and origins ==

44Net traces back to 1981, when [https://en.wikipedia.org/wiki/Hank_Magnuski Hank Magnuski] requested IP address space from [https://en.wikipedia.org/wiki/Jon_Postel Jon Postel] for amateur packet radio networking. The project became widely known as AMPRNet, and the term is still used today.

Over time, those early packet-radio experiments expanded into a broader system. Yes, there are still a few 1200bps VHF links out there, but today, people use high-speed microwave, fiber, and satellite to connect systems across neighborhoods, regions, countries, and around the world.

In 2019, a portion of AMPRNet address space was sold. The proceeds established long-term funding of [https://www.ardc.net ARDC], which supports ongoing 44Net operations as well as broader [https://www.ardc.net/grants grants] for open communications and digital infrastructure.

The evolution has been cumulative. New technologies have layered onto earlier practices, while the core idea — learning by operating real networks — has endured.

For more historical background as told by people who were there at the beginning, watch [https://archive.org/details/youtube-MQVyJUjmfZc The 44Net Origin Story].

== Why public addresses? ==

Using publicly routable space changes what you can learn and build:
* Services can be directly reachable without depending on NAT traversal.
* Networks can operate independently of any single hosting provider or transit network.
* Routing, naming, and security practices can be tested in realistic conditions.
* Projects can grow from a single host to routed subnets and multi-site networks.

In short, 44Net makes it possible to work under real operational conditions rather than only in isolated lab environments. This is especially important for learning about how the Internet works, and for building projects that need to be visible and reachable by others.

== Stewardship model ==

44Net is sustained by a shared model:
* [https://www.ardc.net ARDC] bears the legal, fiduciary, and organizational responsibilities of maintaining the address space.
* Participants operate systems, run services, maintain links, and collaborate on project development.

This balance helps keep the network stable enough to build on for the long term, while remaining open to experimentation and change in the short term.

44Net does not operate as a centrally delivered service. The network is sustained by participants who treat it as something worth maintaining for those who come after them.
For a deeper explanation of how independent participation methods coexist, see [[Decentralization]].

Related pages:
* [[Governance]]
* [[Policies]]
* [[Contributing]]

== Participation norms ==

Over the years, several practices have become common across the 44Net community:
* Experimentation and learning are encouraged.
* Sharing knowledge and working in the open are valued.
* Non-commercial use and community benefit are expected.
* Operators take responsibility for running their systems responsibly.
* Unused resources are returned so others can build.

== Ways people encounter 44Net ==

People often arrive at 44Net through one project or technical path before discovering the broader ecosystem.

Some encounter it through regional RF networks or IPIP Mesh links. Others encounter it through services such as IRLP, AREDN, HamNET, or 44Net Connect. Because participation is decentralized, 44Net looks different from place to place, and no single project or approach defines the network.

The underlying infrastructure exists so many kinds of efforts can coexist. Address space, routing, and coordination provide continuity, while participants shape what the network becomes through the systems they choose to build and maintain.

The spirit of 44Net is the spirit of amateur radio. Many operators first encounter ham radio through a single activity — voice repeaters, HF contesting, digital modes, emergency communications, or building hardware — yet amateur radio as a whole is defined by the diversity of what participants choose to explore. In the same way, 44Net can be one thing or many things. It becomes what its participants build with it over time.

Think of 44Net less as a single application or technology and more as a long-running environment where independent projects contribute to a shared, evolving network.

== What’s in a name? ==

People use several names when talking about it, often reflecting how they first encountered it or which aspect they are thinking about at the moment. In practice, these terms overlap more than they differ.

Many participants use '''44Net''' when describing the present-day community and the evolving ecosystem of projects built on the address space. The name tends to emphasize participation and collaboration.

'''AMPRNet''' is still widely heard, especially when discussing the origins of amateur packet radio networking or the early history of the network. For some operators the term carries historical continuity, while others use it interchangeably with 44Net still today.

Operators also refer to '''network 44''' when speaking specifically about the IP address block itself — a habit that dates back to the original Class A allocation. In conversation, the phrase often serves as a neutral shorthand that avoids implying any particular project or technology.

Rather than strict definitions, these names reflect different perspectives on the same long‑running system. What matters in practice is the shared infrastructure and the community of people who continue to build on it.

Main Page

2026-03-01T01:13:45Z

KI5QKX: mw push

{{DISPLAYTITLE:44Net Main Page}}
<div class="toclimit-3">
__TOC__
</div>

{{Lead|44Net is a community of licensed amateur radio operators building and connecting real networks using shared public address space.}}

== 44Net in brief ==
{{Section|class=mw-section--brief|1=
{{SectionAside|
{{SectionFigure|file=Network_map_illustration.png|width=400px|caption=44Net IP addresses are globally routable, enabling direct accessibility from the public Internet.}}
}}
'''44Net''' makes publicly reachable networking available for experimentation and learning. Amateur radio operators and groups use it to run systems that are directly accessible from the Internet using stable public IP addresses.

The resource that makes this possible is a block of over 12 million IP addresses tracing its origins to early packet radio. Today, [https://ardc.net/ Amateur Radio Digital Communications (ARDC)] maintains the address space in service to the community. See [[About 44Net]] for background and history.

}}

{{Section|
== What people build ==
People use 44Net in many ways. Some run a single system; others collaborate on shared projects or build independent networks. There is no single “right” way to participate.

Projects vary in scale and technical depth, from individual servers and stations to regional networks and volunteer-run independent systems.

{{SectionLayout|min=16rem|class=mw-section__layout--build|
{{SectionCard|
=== Individual projects ===
Remote station operation, self-hosted services, cloud services with {{Term|BYOIP}}.

==== Examples: ====
* [https://ni2o.ampr.org NI2O’s bit of Cyberspace]
* [https://yo2loj.ampr.org YO2LOJ’s map of 44Net]

{{SectionMoreLink|page=What People Build|label=See more projects →}}
}}

{{SectionCard|
=== Shared infrastructure ===
Club networks, linked repeaters, and services for the wider community.

==== Examples: ====
* [https://www.irlp.net The Internet Radio Linking Project]
* [https://hamgate.ampr.org HamGate Northeast US Networks]

{{SectionMoreLink|page=What People Build|label=See more projects →}}
}}

{{SectionCard|
=== Autonomous networks ===
Multi-site links, resilient backbones, and
globally-routed independent systems.

==== Examples: ====
* [https://www.darc.de/der-club/distrikte/c/hamnet/ HamNET broadband RF network]
* [https://www.arednmesh.org AREDN Emergency Data Network]

{{SectionMoreLink|page=What People Build|label=See more projects →}}
}}
}}

See [[What People Build|What People Build on 44Net]] for more examples.
}}

== How people participate ==
People arrive at 44Net by joining an existing project, contributing to a shared effort, or creating something new of their own.

Anyone interested can join one of the [https://ardc.groups.io/ mailing lists] to follow what people are actively doing with 44Net.

{{Section|variant=secondary|
=== Common paths into 44Net ===
{{SectionLayout|min=16rem|gap=0.75rem|
{{SectionCard|
==== Join a network ====
Many participants begin by joining an existing project. Regional RF networks, overlay networks, and other volunteer-run systems offer ways to learn and practice.

===== Examples: =====
Local packet and microwave networks, regional mesh projects, and shared access systems operated by volunteer groups.
}}

{{SectionCard|
==== Contribute to a shared project ====
Others participate by contributing to an active project. Technicians, designers, tower climbers, and system administrators — time and skills are always in demand.

===== Examples: =====
IRLP nodes, shared monitoring or DNS services, research collaborations, repeater linking systems, and community experimentation platforms.
}}

{{SectionCard|
==== Create something new ====
Some participants begin by building systems or tools of their own. Many parts of 44Net running today started as something one person built that others found useful.

===== Examples: =====
New club networks, independent routing experiments, novel services, or radio-linked systems exploring new technical ideas.
}}
}}
}}

== How people connect ==
When an operator is ready to run their own system, they choose a provisioning approach that fits their project, request address space, and get building.
These paths coexist but are not automatically integrated; see [[Decentralization|how Connect, IPIP Mesh, and BGP fit together]].

{{Section|variant=secondary|
=== Common ways projects connect ===
{{SectionLayout|min=16rem|gap=0.75rem|
{{SectionCard|
==== 44Net Connect ====
A WireGuard-based approach that uses secure tunnels over existing Internet links to bring 44Net to common, modern devices. Developed and maintained by volunteers with support from ARDC.

[[44Net Connect|Learn more about 44Net Connect →]]
}}

{{SectionCard|
==== IPIP Mesh ====
A community-operated overlay network built with IP-in-IP tunnels, allowing independently run systems to interconnect across the Internet. It’s a living descendant of the original AMPRNet packet networks.

[[GetStarted#Get_Started_with_IPIP_Mesh|Get Started with IPIP Mesh →]]
}}

{{SectionCard|
==== BGP-announced subnet ====
Projects integrate directly with the Internet’s global routing system by announcing 44Net subnets via BGP. Groups with ASNs, upstream peers, or datacenter facilities join the core of the Internet this way.

[[GetStarted#Get_Started_with_BGP-Announced_Subnets|Get Started with BGP-Announced Subnets →]]
}}
}}
}}

== A culture of experimentation ==
44Net is meant to be explored. Many operators begin with a small experiment and discover new ideas along the way. Projects may grow, change direction, or conclude entirely. Returning address space when a project ends keeps the resource available for others to try something new.

== Shared stewardship ==
ARDC maintains the address space and supporting infrastructure, while participants steward the network by building systems, maintaining projects, and supporting one another. As with amateur radio, wide freedom to experiment comes with shared responsibility to care for the resource and keep it useful for future builders.

ARDC maintains the address space and the core infrastructure that keeps 44Net available over time. Participants help care for the network by building things, keeping them running, and supporting one another’s work. In keeping with amateur radio tradition, operators have wide freedom to experiment, provided they help protect the resource and use it thoughtfully so others can build and explore as well.

To learn more about how decisions are made or how to take part, see [[About 44Net]], [[Governance]], [[Policies]], and [[Contributing]].

== Before starting ==
44Net is maintained as a community service for non-commercial projects and generally requires an amateur radio operating license. Community expectations follow amateur radio traditions. To learn more about eligibility, see [[Eligibility|Learn how eligibility works]].

== Further reading ==
* [[About 44Net|About 44Net]]: Understand history and stewardship
* [[What People Build|What People Build on 44Net]]: Project examples
* [[Provisioning Methods|Ways to Provision 44Net]]: Get 44Net on your device or network.

== Joining the discussion ==
You do not need a project or subnet to start. Many people begin just by listening.

* [[Community|Community and Mailing Lists]]: Subscribe to community discussions
* Introduce yourself or follow ongoing projects.
* See what others are building, and share ideas of your own.

{{Info|Note|The 44Net Wiki is being updated and expanded. You may notice new sections and stub pages while this work is in progress. If you have suggestions or comments, please share them on the [https://ardc.groups.io/g/44net mailing list] or help make contributions yourself.}}

== Older docs and notes ==
Earlier pages that may still be useful:
* [[Archive/Main Page]]
* [[Archive/Home]]
* [[Quickstart]]
* [[Requesting a block]]
* See [[Archive]] for more.

[[Category:Getting Started]]

GetStarted

2026-03-01T01:13:40Z

KI5QKX: mw push

{{DISPLAYTITLE:Get Started with 44Net}}

Welcome. This page helps you bring 44Net to your device or network and choose how you want to participate.

Start by creating an account, then select the participation model that matches your environment.

== Step 1: Create your Portal account ==

An account is required before requesting address space, managing DNS, or participating fully.

* [[Portal/Sign Up|Create a Portal account and verify your callsign]]

Once your account is ready, you can decide how you want to participate.

== Step 2: Choose an operating model ==

44Net can be operated in several different ways.
These methods are independent by design; see [[Decentralization]] for a conceptual overview.

If you want an overview of provisioning methods first, see [[Provisioning Methods|Provisioning Methods]].

=== Get connected quickly: 44Net Connect ===

Put 44Net on a single device or small network from almost any connection, including home networks, cloud hosts, or mobile devices.

* Start here: [[44Net Connect/Quick Start|44Net Connect Quick Start]]

Ideal when you want a flexible endpoint you control without operating shared infrastructure.

=== Participate via the IPIP Mesh ===

Join the long‑standing shared 44Net community network built from interconnected tunnel endpoints and regional collaboration.

* Start here: [[IPIP Mesh/Quick Start|IPIP Mesh Quick Start]]

Well suited for persistent stations participating in community routing environments.

=== Operate routed infrastructure: BGP announce ===

Integrate 44Net directly into an independently operated routed network using BGP.

* Start here: [[BGP/Quick Start|BGP Direct Announce Quick Start]]

Appropriate when you already manage routing infrastructure and participate in Internet routing, or if you have access to an upstream provider that can announce on your behalf.

=== Learn, explore, or contribute ===

You do not need infrastructure to participate.

* Browse documentation and projects
* Join discussions
* Help test, document, or support community efforts

Start with:

* [[Main Page|Explore the Wiki]]
* [https://ardc.groups.io/g/main ARDC 44Net discussion group]

== Step 3: Head out ==

After choosing a path, common next steps include:

* Request address space: [[Portal/Request Address Space|Requesting Address Space]]
* Claim DNS under <code><callsign>.ampr.org</code>: [[DNS/Portal/Subdomains|Claiming DNS]]
* Continue with Portal documentation: [[Portal/Introduction|Portal Introduction]]
* Find specific topics: [[Special:Search|Search the Wiki]]

== Older docs and notes ==
Earlier pages that may still be useful:
* [[Quickstart]]
* [[Requesting a block]]
* [[Getting started with Linux and packet radio]]
* See [[Archive]] for more.
[[Category:Getting Started]]

Board of Directors (ARDC)

2026-03-01T00:17:01Z

KI5QKX: mw push

{{DISPLAYTITLE:Board of Directors (ARDC)}}

The ARDC Board of Directors provides governance oversight for Amateur Radio Digital Communications (ARDC), the nonprofit organization that stewards the 44Net address space and program. The Board establishes organizational policy, approves major initiatives, and ensures that ARDC operates in accordance with its nonprofit mission.

Historically, many members of the ARDC Board have also been long‑time participants in 44Net itself. Past and present Board members include individuals who were directly involved in the early development of the network, including Bdale Garbee, Phil Karn, John Gilmore, and KC Claffey. This continuity reflects the Board’s longstanding roots in the amateur radio networking community.

== Relationship to 44Net ==
44Net is a program operated by ARDC. The Board of Directors holds ultimate legal, fiduciary, and administrative responsibility for 44Net, including approval of major policy directions, program priorities, and organizational strategy.

Day-to-day operation of 44Net — including subnet assignment processing, infrastructure management, documentation, and community support — is carried out by ARDC staff and volunteers.

== Relationship to ARDC staff ==
The Board governs ARDC at an organizational level. ARDC staff are responsible for implementing programs, operating services, and carrying out the organization’s work under Board oversight.

== Relationship to the technical advisory committee ==
The [[TAC|Technical Advisory Committee (TAC)]] provides technical advice and recommendations related to 44Net. The TAC serves in an advisory capacity. The Board retains final governance authority for ARDC and its programs.

== Further reading ==
For current information about ARDC governance and Board membership, see the ARDC website:

* [https://www.ardc.net/about/ About ARDC]
* [https://www.ardc.net/about/who-we-are/ ARDC Staff and Board of Directors]
[[Category:Governance]]

Setting up a gateway in a ROS7 Mikrotik router container on arm32, arm64 and x86-64

2026-03-01T00:15:02Z

KI5QKX: mw push

#REDIRECT [[Setting up a gateway in a ROS7 Mikrotik router container on arm32 arm64 and x86-64]]
[[Category:Infrastructure]]
[[Category:Gateways]]

Setting up a gateway in a ROS7 Mikrotik router container on arm32 arm64 and x86-64

2026-03-01T00:15:01Z

KI5QKX: mw push

Setting up a gateway in a ROS7 Mikrotik router running in a container on arm and arm64 models and x86-64 CHR

'''This is an experimental software build for the 'enthusiasts' out there.'''

Source code is available in git.ampr.org: https://git.ampr.org/yo2loj/ampr-ros7-container/-/tree/main

<h1>Info</h1>

These are the steps for setting up a fully functional AMPR gateway on an arm/arm64 MikroTik router
Tested and found working on CRS2116 and RB3011 for now.

MikroTik ARM64 devices:
Routers: CCR2004, CCR2116, CCR2216, RB5009
Switches: CRS520
Wireless and 5G: Netmetal ax, LHG-LTE6, ATL-LTE18
SOHO: hAP-ax2, cAP-ax, hAP-ax3, Chateau-ax
Others: AMPERE

MikroTik ARM32 devices:
Routers: L009, RB3011, RB4011, RB1100AHx4,
Switches: CRS305, CRS309, CRS310, CRS317, CRS320, CRS326, CRS328
Wireless and 5G: SXTsq-5ac, NetBox-5ax, LHGXL-5ac
SOHO: hAP-ax lite, hap-ac2, cAP-ac, wAP-ac, cAPXL-ac, hAP-ac3, Chateau
Routerboard: L11UG, L23UGSR, RB450Gx4

MikroTik x86-64 devices:
Others: Cloud Hosted Router

Containers are not available on MIPSBE, MMIPS, SMIPS, TILE or PPC architectures.

== General concept ==
Mikrotik routers running ROS 7 (7.15.3 being current at the time of writing) based on arm and arm64 processor, as well as CHR setups are able to run software containers (similar to docker).
This opens the possibility to host a virtualized gateway in such a container, allowing a simple and efficient setup on modern systems.

The gateway will be hosted in a VRF on the router, providing gateway services using policy routing.

As a concept, the container has a single VETH interface which will decapsulate all incoming IPIP traffic from the tunnels, and encapsulate all outgoing traffic towards them.
The container itself is isolated behind a bridge and offers some basic filtering function (e.g. restrict access from internet hosts).
It will receive the RIPv2 broadcasts from the AMPR gateway and provide the obtained routes as RIP broadcasts to the router itself inside the mentioned VRF.

The container does not save anything to disk (which would be a bad idea on the router's flash memory), so the AMPR routes are lost on container or router restart, and you need to wait the now classical 5 minutes. But this should be no problem on a 24/7 on router.

== Limitations ==

The router does not forward multicast frames at all, nor does it send out broadcasts.
Incoming broadcasts are accepted and forwarded to the local VRF.

The container itself needs to sit behind a bridge due to a kernel bug in the version used by Mikrotik which sends out "Port unreachable" ICMP messages on incoming IPIP traffic if it is handled in user space (The same thing causing the need of a kernel filter in amprd. This is fixed in newer kernel releases but it will take a while for it to make its way into ROS). Bridge filtering is used to mask those messages.

<h1>New router 5 minutes set up</h1>

As a prerequisite, get your internet connection working based on the default mikrotik configuration.
Basically set up your ISP uplink either via DHCP or by setting up a PPPoE or similar connection.
Leave the default firewall rule as they are.
Alternatively, you can start with a completely empty router, with only a active internet connection.

First you need to enable container support according to the info provided by Mikrotik.
In a console type in:
/system/device-mode/update container=yes
The system will want you to do a hard reset at this point to confirm the request. This means you need physical access to the device.

Next, you need to install the container package for your firmware version. Download the "extra" firmware package from MikroTik for your FW version and extract the "container-7.x.y-<arch>.npk" file. Upload it to your router and restart. This will install the package onto the router. After restart, you will have a new option available: /containers

== Installation script ==
Next we need to install the container according to your hardware.
Please chose the correct setup script variant:

ARM32 - ampr_arm32.rsc
ARM64 - ampr_arm64.rsc
CHRx86 - ampr_x86_64.rsc

Unfortunately, containers are not available on Mips, Tile or PowerPC devices.

The example assumes you use an arm32 device. Please use the proper one...

Open a route console window.

1. Check is the remote server is available:
[admin@MikroTik] > ping yo2loj.ro
SEQ HOST SIZE TTL TIME STATUS
0 89.33.44.100 56 58 10ms574us
1 89.33.44.100 56 58 9ms141us
2 89.33.44.100 56 58 9ms5us
sent=3 received=3 packet-loss=0% min-rtt=9ms5us avg-rtt=9ms573us max-rtt=10ms574us

2. Download the configuration script
[admin@MikroTik] > /tool fetch url="http://yo2loj.ro/containers/ampr_arm32.rsc"
status: finished
downloaded: 5KiB
total: 5KiB
duration: 1s

3. Run the configuration script
[admin@MikroTik] > import ampr_arm32.rsc
AMPR: Creating bridge and VRF
AMPR: Setting up RIP
AMPR: Creating container envs
AMPR: Setting up firewall rules
AMPR: Creating container update script
AMPR: Creating routing rules
AMPR: Installing container
No container is installed
status: finished
downloaded: 366KiB
total: 366KiB
duration: 1s
AMPR: Script finished successful
AMPR: Now update your container envs and start the container

Your container is now installed.
You need to configure its environment variables according to the description given below.

After configuration is complete, go to "containers" and star it up.
It should show "running" and you should see it's messages in the log window.

After at most 5 minutes, you should get the tunnel routes in your vrf, and your gateway should be fully up and running.

If logging/debugging is not needed anymore, please disable it by clicking on the container and unchecking te logging box.

== Container configuration parameters ==
You need to adapt the pre-existing container environment variables to your particular gateway before starting it again.
The following ENV parameters are preset in Container-> Envs:
AMPR_SUBNETS - holds your local subnets as defined in the Portal, as comma separated list of <SUBNET>/<MASK> tupples, e.g. "44.128.0.0/24,44.128.1.0/24"
ALL_VIA_AMPRGW - enables forwarding of all AMPR destinations via AMPRGW, values are "0" or "1"
FORWARD_INTERNET - enables forward of traffic from/to internet hosts, values are "0" or "1"
IGNORED_SUBNETS - allows you to ignore specific subnets provided by RIP, by <SUBNET>/<MASK> or gateway address e.g. "44.128.0.0/16"
CALL_HOME - the classic string, <CALLSIGN>@<LOCATOR> to show up on the map. You will get a yellow dot. e.g. "YO2LOJ@KN05OR". Leaving the field empty disables call home.

Please note that the provided default will allow you to play around, but will not provide a working set up.

Next, you need to set up a local AMPR LAN on your router router, or, if you have only a single IP address assigned, add it to one of your router's interfaces with a /32 netmask
Anyway, you need to add a src-nat rule to the router's IP address to get your traffic flowing (let's assume its 44.128.0.1).
The address shall be set on an interface OUTSIDE OF THE VRF.

For a single address:
/ip address add address=44.128.0.1 interface=bridge
or even on the loopback interface:
For a single address:
/ip address add address=44.128.0.1 interface=lo

For a subnet:
/ip address add address=44.128.0.1/24 interface=<interface name>

And your src-nat NAT rules:
/ip firewall nat add action=src-nat chain=srcnat out-interface=bridge-ampr-gw to-addresses=44.128.0.1
/ip firewall nat add action=src-nat chain=srcnat out-interface=vrf-ampr to-addresses=44.128.0.1

Of course you need to set up additional firewall rules and stuff, but if you do not enable internet forwarding, you should be pretty safe being exposed only to AMPR partners.

Please note that for your firewall rules the incoming interface from the tunnels is "vrf_ampr" and the outgoing interface is "bridge-ampr-gw" for forwarded and "vrf-ampr" for local outgoing data.

== Additional optional configuration ==

You may notice that on an external traceroute your router's IP address will show up as 172.17.0.1.
To fix this small glitch, you need to modify your existing "rip-ampr-in" RIP input filter rule to provide the correct preferred source address.

Modify the existing rule from
accept;

to set your router's local AMPR IP as its preferred source
set pref-src 44.128.0.1;
accept;

Also, if you want to access the AMPR network from a LAN not using AMPR addresses, you need to set up a forwarding rule and a SRC-NAT one:

/ip firewall filter
add action=accept chain=forward comment="from LAN" in-interface=<YourLANInterface> dst-address-list=ampr_addr
and
/ip firewall nat
add action=src-nat chain=srcnat comment="NAT to AMPR" dst-address-list=Ampr out-interface=bridge-ampr-gw \
src-address-list=!ampr_addr to-addresses=44.128.0.1

<h1>Configuration on an existing working router - 6 steps</h1>

1 - Bridge, VETH, VRF and interface setup
2 - RIP setup
3 - Firewall rules, Filter, NAT and Mangle
4 - Container environment setup
5 - Container installation (architecture dependent)
6 - Container configuration and final touches

== Preliminary: prepare the router to accept containers ==
First, you need to install container support on your router.
In a console issue:
/system/device-mode/update container=yes
The system will want you to do a hard reset at this point to confirm the request.
This means you need physical access to the device.

Next, you need to install the container package for your firmware version.
Download the "extra" firmware package from MikroTik for your FW version and extract the "container-7.x.y-<arch>.npk" file.
Upload it to your router and restart. This will install the package onto the router.
After restart, you will have a new option available: /containers

== Step 1: Bridge, VETH, VRF and interface setup ==

First create a bridge which will be used for your containr. Let's call it 'bridge-ampr-gw':
/interface bridge add comment="AMPR container" name=bridge-ampr-gw
Assign a network to it. The typical docker IP will be ok:
/ip address add address=172.17.0.1/24 interface=bridge-ampr-gw
Create a virtual ethernet interface for the container itself (call it veth-ampr):
/interface veth add name=veth-ampr address=172.17.0.2/24 comment="AMPR container interface" \
gateway=172.17.0.1
Add the VETH port to the bridge we created above:
/interface bridge port add bridge=bridge-ampr-gw interface=veth-ampr
Because of a kernel anomaly preventing proper userspace IPIP handling, we need to filter icmp messages on the bridge from the container itself:
/interface bridge filter add action=drop chain=input in-interface=veth-ampr ip-protocol=icmp \
mac-protocol=ip src-address=172.17.0.2/32
Now we create a vrf called "vrf-ampr" and add the bridge to it:
/ip vrf add interfaces=bridge-ampr-gw name=vrf-ampr

All the above steps are available here as a rsc file: http://yo2loj.ro/containers/1_ampr_bridge_vrf.rsc

== Step 2: RIP setup ==

First, create a simple accept routing filter to be used by RIP:
/routing filter rule add chain=rip-ampr-in disabled=no rule="accept;"
Next, create a RIP instance for your VRF using the above filter and the defined VRF:
/routing rip instance add afi=ipv4 in-filter-chain=rip-ampr-in name=rip-ampr vrf=vrf-ampr
And now add a passive (receive only) interface to our instance:
/routing rip interface-template add instance=rip-ampr interfaces=bridge-ampr-gw mode=passive

All the above steps are available here as a rsc file: http://yo2loj.ro/containers/2_rip.rsc

== Step 3: Firewall rules, filter, NAT and mangle ==

Now we need to forward out IPIP tunnels to the container, and extract our data from the VRF.
For our convenience we will set up an address list to handle AMPR space as one entity
(if you already have such a list on the router, you can use it)
/ip firewall address-list
add address=44.0.0.0/9 list=ampr_addr
add address=44.128.0.0/10 list=ampr_addr
Also, we can use an interface list called WAN for the internet access interfaces (like the one in the default config).
If you prefer individual interfaces, you can of course use them in your rules.

Filters are needed to allow data input and forward to/from the router.
Accept RIP from the VRF:
/ip firewall filter
add action=accept chain=input comment="RIP via VRF" dst-port=520 in-interface=vrf-ampr protocol=udp
Accept input from the AMPR address space to the router (important for ping and traceroute):
/ip firewall filter
add action=accept chain=input comment="AMPR via Tunnels" dst-address-list=ampr_addr in-interface=vrf-ampr \
src-address-list=ampr_addr
And we need to accept some forwarding for the IPIP tunnels, from VRF to our AMPR space and between AMPR hosts:
/ip firewall filter
add action=accept chain=forward comment="IPIP Tunnels from ISP" in-interface-list=Internet protocol=ipencap
add action=accept chain=forward comment="IPIP Tunnels from VRF" in-interface=vrf-ampr protocol=ipencap
add action=accept chain=forward comment="VRF to AMPR" dst-address-list=ampr_addr in-interface=vrf-ampr
add action=accept chain=forward comment="AMPR to AMPR" dst-address-list=ampr_addr src-address-list=ampr_addr

Next, we need to forward incoming IPIP traffic to our container (note that WAN interface list, use your interface if you like):
/ip firewall nat
add action=dst-nat chain=dstnat comment="NAT ENCAP" in-interface-list=WAN protocol=ipencap \
to-addresses=172.17.0.2

Now to be able to traverse int and from the VRF, we need some mangle rules.

Incoming IPIP traffic will be marked with the vrf routing mark:
/ip firewall mangle
add action=mark-routing chain=prerouting comment="AMPR IPIP incoming to VRF" in-interface-list=Internet \
new-routing-mark=vrf-ampr passthrough=no protocol=ipencap
Outgoing IPIP traffic will be marked for the main routing table (or the one you need to reach your ISP)
/ip firewall mangle
add action=mark-routing chain=prerouting comment="AMPR IPIP outgoing via ISP" in-interface=vrf-ampr \
new-routing-mark=main passthrough=no protocol=ipencap
Traffic to our local router IPs will be directed via our bridge
/ip firewall mangle
add action=route chain=prerouting comment="AMPR VRF route local" dst-address-type=local in-interface=vrf-ampr \
passthrough=no route-dst=172.17.0.1
And finally, the incoming AMPR traffic will go to the main routing table
/ip firewall mangle
add action=mark-routing chain=prerouting comment="AMPR VRF forward" in-interface=vrf-ampr new-routing-mark=main\
passthrough=no

All the above steps are available here as a rsc file: http://yo2loj.ro/containers/3_firewall.rsc

== Step 4 - Container environment setup ==
This step prepares the environment variables for the container.

/container envs
add comment="My subnets, as defined in the Portal" key=AMPR_SUBNETS name=ampr-cfg value=\
44.128.0.0/24,44.128.1.0/24
add comment="Default gateway is AMPRGW instead of Internet" key=ALL_VIA_AMPRGW name=ampr-cfg value=0
add comment="Forward internet traffic" key=FORWARD_INTERNET name=ampr-cfg value=0
add comment="Call home callsign and locator" key=CALL_HOME name=ampr-cfg value=test@AA00aa
add comment="Ignored subnets in RIP" key=IGNORED_SUBNETS name=ampr-cfg value=44.128.0.0/16

Just paste them into the console or import the rsc script as it is. You will edit those later.

The rsc file is here: http://yo2loj.ro/containers/4_container_env.rsc

== Step 5 - Container installation ==
Now you need to download the container which fits your architecture.
The following rsc files will install a script which, when run will import and install the container.
The same scripts will update and replace the container if run again.

ARM32 - http://yo2loj.ro/containers/5_container_arm32.rsc
ARM64 - http://yo2loj.ro/containers/5_container_arm64.rsc
CHRx86 - http://yo2loj.ro/containers/5_container_x86_64.rsc

Of course, instead of the script, you can download the appropriate tar container files yourself:
ARM32 - http://yo2loj.ro/containers/ampr-arm32.tar
ARM64 - http://yo2loj.ro/containers/ampr-arm64.tar
CHRx86 - http://yo2loj.ro/containers/ampr-x86-64.tar
and install them manually. Please set them to use the env variables "ampr-cfg".

Or, you can compile and pack the container yourself from source. At the time of writing, the current version is 1.2.0:
http://yo2loj.ro/containers/ampr-container-1.2.0-release.tgz

== Step 6 - Container configuration and final touches ==

You need to edit your env variables according to the description given in the new router setup.

Start your container and wait 5 min. You should see AMPR routes showing up in the VRF's routing table
(Some 840 of them if ALL_VIA_AMPRGW is not enabled, otherwise you will get only 2 routes, 44.0.0.0/9 and 44.128.0.0/10).

You may notice that on an external traceroute your router's IP address will show up as 172.17.0.1.
To fix this small glitch, you need to modify your existing "rip-ampr-in" RIP input filter rule to provide the correct preferred source address.

Modify the existing rule from
accept;

to set your router's local AMPR IP as its preferred source
set pref-src 44.128.0.1;
accept;

Now, activate the use of the whole system.
Set up a routing rule set to force all outgoing AMPR traffic to do a lookup in the VRF routing table:
/routing rule
add action=lookup disabled=yes dst-address=44.0.0.0/9 table=vrf-ampr
add action=lookup disabled=yes dst-address=44.128.0.0/10 table=vrf-ampr
If no route is found in that table, the lookup will continue via the main table towards your default route.

Your local AMPR network and additional routing will go into the main table and the lookup will be done AFTER passing through the VRF's routing table.
This means that a matching route in the VRF, including a default 0.0.0.0/0 will take precedence over any route defined in the main table.

Also, if you want to access the AMPR network from a LAN not using AMPR addresses, you need to set up a forwarding rule and a SRC-NAT one:

/ip firewall filter
add action=accept chain=forward comment="from LAN" in-interface=LAN dst-address-list=ampr_addr
and
/ip firewall nat
add action=src-nat chain=srcnat comment="NAT to AMPR" dst-address-list=Ampr out-interface=bridge-ampr-gw \
src-address-list=!ampr_addr to-addresses=<your router's AMPR ip>

== Additional info ==
All available files are here: http://yo2loj.ro/containers/

Rip Rip Hurray! de YO2LOJ

[[Category:How-To Guides]]
[[Category:Infrastructure]]
[[Category:Gateways]]

Services/Historic

2026-03-01T00:15:01Z

KI5QKX: mw push

Below is a list of historic services that were previously offered by ampr users but are not currently available.

{| class="wikitable sortable"
|-
! Maintainer !! Service Name!! URL/IP !! Service Type !! Description !! Other Information
|-
| N1URO ||Network Tools|| http://n1uro.ampr.org/do.shtml || HTTP|| source IP checker, speed test, Ping, Traceroute, etc.|| DNS entry no longer exists
|-
| Various Operators ||Network Time Protocol Server || ns.ardc.net (Stratum 2, UK) server.yo2loj.ampr.org (Stratum 2) f4gve.ampr.org (Stratum 3) ntp1.on3rvh.ampr.org || NTP|| Stratum 2 Network Time Server - References US, Canadian and Mexican|| No NTP server configured on host
|-
| OH7LZB ||[[AMPRNet_VPN]] || http://wiki.ampr.org/wiki/AMPRNet_VPN || VPN|| [http://en.wikipedia.org/wiki/OpenVPN OpenVPN]-based || '''Unavailable as of May 2024''' You must have a X.509 certificate issued by [http://www.arrl.org/logbook-of-the-world ARRL Logbook of the World (LoTW)]. ARRL membership is not required.
|-}

[[Category:Reference]]
[[Category:Infrastructure]]
[[Category:Core Services]]

DNS

2026-03-01T00:15:01Z

KI5QKX: mw push

{{DISPLAYTITLE:44Net DNS}}
The 44Net DNS service provides name resolution and delegation for 44Net users. Most participants use it to publish hostnames for their systems, starting with a callsign-based subdomain and adding records as needed.

A typical DNS path on 44Net:
# Claim a callsign-based subdomain under ampr.org.
# Create DNS records that map hostnames to IP addresses.

This is sufficient for publishing things like web servers, gateways, remote stations, and repeaters.

* [[DNS/Portal/Subdomains|Claiming a Subdomain]]
* [[DNS/Portal/Records|Managing Records]]

== Running your own DNS ==

Some participants run their own DNS servers rather than relying only on the Portal.

In this approach, control of a domain is delegated to local systems, while remaining part of the ampr.org domain.

This supports automation, custom workflows, and closer integration with locally managed services.

* [[DNS/Portal/Delegations|Delegating DNS to an Independent Name Server]]
* [[DNS/Setup/OpenBSD_Resolver|Setting up a Recursive Resolver on OpenBSD]]

== Understanding DNS ==

For background on how DNS works (with 44Net use in mind):

* [[DNS/Overview|DNS Overview and Concepts]]

== Older docs and notes ==
Earlier pages that may still be useful:
* [[Verification]]
* See [[Archive]] for more.
[[Category:DNS]]

Setting up a gateway on Linux

2026-03-01T00:15:00Z

KI5QKX: mw push

There are a few different ways to run an AMPRnet gateway on a Linux system. Each has some benefits, so you'll need to pick your favourite.

Before configuring the Linux gateway you'll need to:
# Using the [[Portal]], request an IP address (or addresses) by clicking on "Request address space" then selecting "IPIP Tunnel Mesh" as the Use Case.
# You will need to have a public static IP address for your gateway.
# Using the [[Portal]], create an entry for your gateway.
# Get some of your AMPRNet IP addresses registered in the [[ampr.org]] DNS.

= Flavours of Linux gateways =

== Native Linux kernel AX.25 and IPIP tunneling ==

Linux contains the necessary building blocks for a gateway without much added software. Radio interfaces are configured much like any other network interfaces such as Ethernet, they're just given amateur radio callsigns in addition to an IP address (callsign will act the role of the Ethernet MAC address). If you're familiar with Linux configuration but have not heard of NOS, or if you wish to go with minimal amount of moving parts, this would probably be your choice.

Setting up a native Linux gateway consists of two main steps:

=== Step 1: Setting up tunnel routing to the rest of the AMPRnet===
Configuring your Linux system to learn about other AMPRNet [[gateway| gateways]] can be done two ways:

# Automatically learn about other gateways via modified RIPv2 advertisements. Two popular programs to do this are:
## Using [[ampr-ripd]], a C based routing daemon
## Using [[rip44d]], a PERL based routing daemon
# Downloading an [[encap.txt]] file and setting up routes using a [[munge script]] is the traditional method

==== Example gateway configuration instructions ====
* [[Ubuntu Linux Gateway Example]]
* [http://www.qsl.net/k/kb9mwr//wapr/tcpip/ampr-ripd.html Two Interface Debian Linux Amprnet Gateway Example]
* [https://k7ilo.blogspot.com/p/server-setup.html K7ILO'S Two Interface Debian 11 AmprNet Gateway Build in layman's terms]

=== Step 2: Setting up radio interfaces in Linux===

* [http://www.tldp.org/HOWTO/AX25-HOWTO/ Linux AX.25 set-up]
* 802.11 WiFi on amateur frequencies (2.4 or 5 GHz) is a new popular way to set up fast links.

== Running JNOS (or other NOS) on top of Linux ==

If you're already familiar with running NOS on top of DOS or Linux, or wish to keep the AMPRnet IP packet routing away from the host Linux system, it might make sense to run JNOS as an application on top of Linux.

The downside is that it'll have a slightly higher overhead (consumed memory and CPU), and you'll have two IP routers running on top of each other instead of just one, which is seen as slightly complicated by some.

The upside is that you'll also get the JNOS BBS-type features, and some other traditional services without installing additional software on top.

=See also=

* [[Ubuntu Linux Gateway Example]]
* [[startampr]]

[[Category:How-To Guides]]
[[Category:Infrastructure]]
[[Category:Gateways]]

Portal intro

2026-03-01T00:15:00Z

KI5QKX: mw push

= ARDC Portal 2.0 Technical Documentation =

By Rebecca Key KO4KVG

Version: 4 (October 22, 2024)

== Accessing the Portal ==

Go to [https://portal.ampr.org/home https://portal.ampr.org], where you should see the following UI:

[[File:Portal-homepage-login-v4.png|750px]]

== Registration ==

# Click on the 'Register' button at the top right of the UI (see 'Accessing the Portal', step 1) or on the 'Register' button in the 'LOGIN' dialog box. This will take you to the following screen: [[File:Registration-step-1-of-3-v4.png|750px]]
# Complete the field for 'What should we call you?:' and click 'Continue'.
# In the dialog box titled 'Registration (Step 2/3)', you will be introduced to help icons ('?') that will provide you useful information throughout the Portal. Click 'Close' to exit the dialog box. [[File:Registration-step-2-of-3-popup-box-v4.png|740px]] From there, you enter your Given name, Family name, email address, a username (used to login) and a password, then click 'Continue'. [[File:Registration-step-2-of-3-v4.png|750px]]
# You should then arrive at a dialog box titled 'Registration (Step 3/3)' that displays the End User License Agreement (EULA). Read through the EULA, and if you agree to the terms and conditions, tick both 'I AM 18 YEARS OF AGE OR OLDER', and 'I accept and agree to the terms of this End User License Agreement', and then click 'I Accept'. Note that if you are under the age of 18, and/or if you do not agree with the Terms of Use, then you will not be able to use the Portal. [[File:Registration-step-3-of-3-v4.png|750px]]
## Note: When you log back in on a later date, you might get a notice about the addition and/or updates to the EULA. For example, if you see a dialog box titled 'The EULA has been updated', verify that you are 18 or older, and if you would like to continue using the Portal, accept the updated EULA.
# Upon accepting the Terms of Use, you should get a message (see below) informing you that the system is sending you an email verification with further instructions. Follow the instructions in this email. [[File:Verify-email-v4.png|750px]]
# Once you complete the instructions in the email, you should get a page that looks like the one below, which will have an alert entitled 'You successfully verified your email'. Fill in the information in the 'LOGIN' dialog box and click 'Login'. [[File:email-verified-v3.png|750px]]
# From there, you will be prompted to click 'Continue Registration'. [[File:Continue-registration-v4.png|750px]]
# Once you click 'Continue Registration', you will be brought to a page where you will be asked to complete registration. [[File:Complete-registration-form-v4.png|750px]]
# Confirm that the required information is correct; add any optional information you prefer to share; read and agree to the 'Terms and Conditions', and click the 'Continue' button. You should then see a page that shows 'Registration Complete', which includes a note to verify your call sign as the next step. [[File:Registration-complete-v4.png|750px]]
# To add and verify your call sign, go to the 'Account' dropdown menu and select 'Call signs'. You should see the 'Your call signs' dialog box. [[File:Your-call-signs-v4.png|750px]] Click 'Add a call sign', where you will see a form to add your call sign. Enter your call sign in the input field and click 'Add'. [[File:Add-a-call-sign-v4.png|750px]] You should then see a message stating 'The new call sign was successfully added'. [[File:Call-sign-successfully-added-v4.png|750px]] Clicking the 'Make Primary' button will make a desired call sign the primary call sign on the account, and you can delete a call sign from your account by simply clicking the 'Delete' button.
## If you did not add your maidenhead to your profile, you will get a message at the top of the page stating: [[File:Add-maidenhead-error-prompt-v4.png]] above the 'Update your profile' form. [[File:Update-your-profile-maidenhead-v4.png|750px]] Add your maidenhead, confirm your password, and click 'Save'.
## You will then see the following message above the 'Update your profile' form: [[File:profile-updated-ok-message-v4.png|500px]]
## Go back to Step 10, where you'll be prompted to add your call sign. 
# On the 'Your call signs' UI, click 'Verify'. This will take you to a screen that details the process of verification. [[File:Verify-call-sign-prompt-2-v4.png|750px]]
# Click on the green 'Verify' button: you should see an alert saying 'Your request to verify your callsign [$call sign] has been submitted', which will create a ticket for the Portal admins to verify your call sign. [[File:Callsign-is-verified-v4.png|750px]] You can check the ticket by going to the 'Tickets' dropdown menu, selecting 'View my tickets', where you see it listed. To see the details of the ticket, click 'View'. [[File:View-ticket-request-details-v4.png|500px]]
## Note that once your call sign has been verified, you will no longer see the ticket in the list. Alternatively, you can confirm that your call sign has been verified by going to 'Account' > 'Call signs', and the status of your call sign verification will be displayed in the 'Your call signs' dialog box. Once your call sign has been verified, you will be able to request address space. [[File:Verified-call-sign-v4.png|750px]]

== Requesting address space (beginner friendly steps) ==

This series of steps is aimed at users who are either new to requesting 44Net address space, need a refresher, or would like to streamline the process. Otherwise, you can also request address space via the Network list in the 'Requesting Address Space (via Network List)' and 'Requesting Address Space for BGP Use (via Network List)' sections below.

# Under the 'Networks' menu, select 'Request addresses'. Note that you can also request address space on the Dashboard by clicking 'Request address space'. [[File:request-address-space-dashboard-v4.png|750px]]
# You should see a dialog box entitled 'Request Address Space'. Select your address type (should be IPv4, as IPv6 is not currently available), use case, and click 'Continue'. Please see the below instructions for your particular use case. [[File:Request-address-space-form-v3.png|750px]]

=== Use case: IPIP tunnel mesh, radio, globally unique space, or general address assignment ===

# If you selected IPIP tunnel mesh, radio, globally unique space, or general address assignment as your use case, you will see a dialog box entitled 'Request IP Assignment'. Fill out the 'Request IP Assignment' dialog box with the required information; agree to the EULA; and click 'Continue'. [[File:Request-ip-assignment-v4.png|750px]]
# You will then see the following note thanking you for requesting address space from ARDC, which includes detailed information about next steps. [[File:Ty-for-requesting-address-space-v4.png|750px]]
# Once your address space has been assigned, you can proceed to step 6 under 'Requesting Address Space (via Network List)'.

=== Use case: BGP direct announce ===

#If you selected 'BGP Direct Announce' as your use case, you will see a dialog box entitled 'Request IP Assignment'. Fill out the 'Request IP Assignment' dialog box with the required information, agree to the EULA, and click 'Continue'. [[File:Request-ip-assignment-for-bgp-v4.png|750px]]
# Proceed to step 3 under 'Requesting Address Space for BGP Use (via Network List)'.

=== Other use cases ===

Selecting any of the below use cases will give you a dialog box that provides more details about the network:
* AREDN
* HAMNET
* HamWAN

== Requesting address space (via network list) ==

# Under the 'Networks' menu, select 'All IPv4 Networks'.
# In the 'List IPv4 Networks' dialog box, click the + sign to expand a line, or use the 'Expand All' button. [[File:List-ipv4-networks-v4.png|500px]]
# Scroll to look for the address space you are looking for (e.g., 44.63.0.0/16 - IPIP Mesh Assignments) and click on the green clipboard icon to the right of the assignment to request an assignment. [[File:Request-network-assignment-v4.png|750px]]
# Fill out the 'Request IP Assignment' dialog box with the required information, and click 'Continue'. [[File:Request-ip-assignment-v4-via-network-list.png|750px]] You will see the dialog box titled 'Thank you for requesting address space from ARDC' (see step 2 under 'Use Case: IPIP Tunnel Mesh, Radio, Globally Unique Space, or General Address Assignment'), which includes detailed information about next steps.
# To confirm that your address space has been successfully requested, you can go to 'Tickets' > 'View my tickets' to see if the request is in your ticket list. Note that you may be asked to provide more information to the Ticket Handler about your request before your address space is assigned. [[File:Confirm-address-request-in-tickets-v4.png|750px]] [[File:Justification-for-address-space-v4.png|750px]]
# Once your space has been assigned (and the associated ticket has been closed), you can view your IPv4 networks by going to 'Networks' > 'my IPv4 networks', where your network detail(s) will be provided. [[File:Network-detail-of-requested-address-space-v4.png|750px]]

== Adding DNS records to a subdomain ==

# On the 'DNS' dropdown menu, select 'My subdomains' and then click 'Request a subdomain' in the 'My subdomains' dialog box. [[File:my-subdomain-dialog-box.png|750px]]
# Choose your domain, determine a name for your subdomain (i.e., most likely your call sign), click 'Create request', and you should see a note [[File:Create-new-subdomain-request-v4.png|750px]] saying 'Subdomain $[call sign].ampr.org has been assigned to you'. [[File:Subdomain-has-been-assigned-to-you-v4.png|750px]] Please be aware that if your call sign has not been verified or if you are requesting a domain other than $[call sign].ampr.org, a ticket will be opened for an administrator to review your request(s). You can verify that your subdomain has been created by going to 'DNS' > 'My subdomains', and your subdomain should appear in the 'My subdomains' dialog box. [[File:Subdomain-creation-verification-v4.png|750px]]
# Once your subdomain has been created, you can add DNS records by going to 'DNS' > 'My subdomains', and click the icon under 'Actions' in the 'Subdomains' dialog box (see step 2 above).
# In the 'Resource records for $subdomain.ampr.org', click 'Add a resource record'. [[File:add-resource-record.png|750px]]
# In the 'Create resource record for $subdomain.ampr.org', select the record type, and click 'Next' (see below). [[File:create-resource-record-step-1.png|750px]]
# Add the details relevant to the record type and ensure that Active is checked, click 'Create', [[File:Create-resource-record-step-2-v4.png|750px]] and you should get an alert that says 'Subdomain Record created successfully'. [[File:Subdomain-record-created-successfully-v4.png|750px]]
# You can verify that your record has been created by going to 'DNS' > 'My records' and look for the record that is associated with your subdomain. [[File:record-associated-with-subdomain.png|750px]]

== Creating a gateway ==

# Go to 'Networks' > 'My gateways' and click 'Create a Gateway' in the 'My Gateways' dialog box. [[File:my-gateways.png|750px]]
# In the 'Create new Gateway' dialog box, fill out all required fields (Hostname can be left blank), click 'Add', and you should get an alert saying 'Gateway created successfully.' [[File:create-new-gateway.png|750px]] [[File:Gateway-created-successfully-v4.png|750px]]
# To add a subnet to your gateway, click the edit button under 'Actions' (see step 2 above). You will be taken to an 'Update Gateway' dialog box, which includes information about your gateway. Click 'Add New Network'. [[File:Update-gateway-v4.png|750px]]
# You will then see an 'Add New Network' dialog box (see below). Select a network from your list of networks; leave 'Find Network' field blank; and then click 'Add'. You should see an alert titled 'Network Successfully Linked to this Gateway' (see below). You can verify that your network has been added by clicking 'View My Gateways' and seeing said gateway under 'My Gateways' (see below). [[File:add-new-network-v3.png|750px]] [[File:Network-successfully-linked-to-gateway-v4.png|750px]] [[File:verify-my-gateways-v3.2.png|750px]]
# If you would like to add someone else's network using their unique code, click 'Add New Network', which will take you to the 'Add New Network' dialog box. Fill out the required information, and click 'Find'. You should have a 44Net address displaying in the 'Network found' field. Click 'Add', and you should see an alert titled 'Network Successfully Linked to this Gateway' (see step 4 above). [[File:Add-network-to-gateway-v4.png|750px]]
# You can add or remove linked networks by clicking the 'Add New Network' or 'Unlink' button, respectively (see steps 3 and 4 above).

== Requesting address space for BGP use (via network list) ==

# From the 'Networks' dropdown menu, go to 'All IPv4 networks', and request a BGP assignment (e.g., 44.31.0.0/16 - BGP Assignments) by clicking on the 'Request Assignment' icon to the right of the listed assignment (green clipboard). [[File:Request-bgp-assignment-v4.png|500px]]
# On the 'Request IP Assignment' dialog box, fill out the mandatory fields, agree to the EULA, and click 'Continue'. [[File:Request-ip-assignment-for-bgp-v4.png|750px]]
# You should see a 'BGP Information' dialog box on the UI. Fill out the mandatory information, click 'Submit Request', [[File:Bgp-information-v4.png|750px]] and you should now see 'Thank you for requesting address space from ARDC' (see Step 2 under 'Use Case: IPIP Tunnel Mesh, Radio, Globally Unique Space, or General Address Assignment'). Note that the justification must be at least 100 characters.
# You can confirm the address has been successfully requested by going to 'Tickets' > 'View my tickets', and your request should be visible in the 'List your tickets' dialog box. Once the ticket has been closed, you should see the allocation listed in your IPv4 networks. [[File:all-ipv4-allocations-by-user.png|500px]] Clicking 'Edit' will bring you to the 'Update Network' dialog box, where you can make appropriate updates, download the EULA, download the Letter of Authorization (LOA), etc (see below). [[File:update-network-v3.2.png|750px]]

== v2.0 Features ==

=== Dashboard ===

After logging in, you should see your Dashboard. If your email has been verified, you should see an 'Account' menu and a 'Tickets' menu at the top right-hand side of the UI. If you have been granted additional privileges, you will see additional menus for those related privileges. The Dashboard will also display information boxes, such as your latest login, IP, and timestamp, or outstanding notifications you need to be aware of.

[[File:Dashboard-v4.png|750px]]

=== Help ===

The 'Help' dropdown menu provides the following options:
*'''View EULA''': displays a copy of the Portal's End User License Agreement (EULA)

* '''2FA''': defines 2FA and provides details on multiple 2FA options to choose from to add to your account

* '''LoT''': provides an overview of Level of Trust (LoT), how it works, and how to increase your LoT

* '''CIDR''': provides an overview of Classless Inter-Domain Routing (CIDR)

* '''Limits''': provides an explanation of your specific limits on Portal activities, which are directly related to your current LoT

* '''Member pages''': These are pages generated by other members

* '''Subdomains''': provides an overview of subdomains and DNS and steps needed to request subdomains

* '''Passwords''': provides password requirements and recommendations for how to create a strong password for your Portal account

* '''Glossary''': includes definitions for terminology relevant to using the Portal

* '''Community''': includes links to ARDC's Groups.io group, along with links to relevant subgroups

* '''Lookup callsign''': allows you to look up call signs of other users on the Portal

=== Maps ===

* '''Distance''': allows you to perform distance and bearing calculations

* '''Maidenhead''': allows you to generate a map from a Maidenhead locator

* '''Conversions''': allows you to convert from DMS to lat/long and back

* '''World map''': a map that displays the approximate location for all members

=== Account ===

The 'Account' dropdown menu provides the following options:
* '''Profile''': allows you to view and update your personal data

* '''Call signs''': allows you to add/remove/verify your call sign(s)

* '''LoT entries''': lists your Level of Trust (LoT) entires

* '''Verify address''': allows you to go through the address verification process, which is needed if you are requesting BGP announced address space

* '''Organisations''': allows you to create organizations and view information of the organizations you are affiliated with

* '''Notifications''': displays a list of user notifications

* '''Notification types''': displays all notification types/options

* '''View all notifications''': displays all your active notifications

* '''Logs''': displays all your log entries

* '''My public page''': displays any public pages you have added and provides the ability to add more

* '''Delete my account''': allows a user to delete their account

==== Profile ====

A user's profile is always available, whether or not a their email address has been verified. Through the profile, a user has access to the following:
* Personal Information (PII) a user chooses to share with ARDC

* The ability for a user to update their account

* The ability for a user to enable 2FA on their account

Changes made to the profile will require the current password to be entered at the bottom of the page and clicking 'Save' for changes take effect.

==== Call signs ====

Here, the user is presented with a list of all call signs they have entered. A user can add up to a maximum of five call signs (can be adjusted on a per user basis), with only one call sign being the primary. Clubs and organization can add up to 10 of their own call signs by default. Call signs must be verified before they can be used. All verified call signs must be unique within the system.

==== Level of Trust (LoT) and LoT Entries ====

The Portal uses various methods to verify users and thus gain 'trust', which is referred to as the 'Level of Trust' (LoT). LoT is used to increase confidence that a user is who they say they are and record that there is a skill set and knowledge that is needed to assign responsibilities to said user in the Portal.

As various tasks are accomplished, such as verification of email and/or call signs, points will be assigned to a users' account. The more points a user has, the higher the LoT. You can learn more about LoT by going to either 'Help' > 'LoT' or 'Account' > 'LoT info' on the navigation menu.

The LoT List is a read-only list for LoT entries of a user. You can find this list by going to 'Account' > 'LoT list'. A user will have at least one entry that shows that their email address was verified. Below are a few examples of what accesses are granted based on a user's LoT.

* Email is not verified
** User can login, access their own profile, delete their account
* Call sign is not verified
** User cannot access DNS records or request address space

==== Notifications ====

The system informs users of various events via notifications. [[File:Notification-types-v4.png|750px]]

Mandatory Notifications:
* Contact Member
* Password Reset
* Ticket Reminder
* LoT Expiry
* LoT Added
* Account Expiry
* LOA Expiry

Optional Notifications:
* Login
* Profile Update
* Ticket Assigned
* ...and many more

Clicking on 'Methods' (under the 'Actions' column, see above) will allow the user to choose a preferred method of notification: [[File:notification-methods.png|750px]]

* Email
* SMS
* many more coming soon, e.g. Zulip, Signal, Telegram...

=== Tickets ===

Tickets track tasks, along with their associated progress, within the Portal. Items managed by tickets include, but are not limited to:
* Call sign verification
* Request(s) for resources (e.g., address space)

The 'Tickets' dropdown menu will allow the user to view all of their tickets, create a new support ticket, and serves as a reference to check the status of any user requests.

Ticket types that are not 'Support' are available within the system and are accessible to a user in a specific circumstance.

=== Domain name system (DNS) records ===

ARDC manages the ampr.org domain for its own use and supports Portal user needs.

Once a user's call sign is verified, they should see the DNS dropdown menu with submenu options 'Domains', 'My subdomains', and 'My records'.

[[File:dns-menu.png|750px]]

=== Networks ===

Once a user's call sign is verified, they should see the 'Networks' dropdown menu with submenu options 'Request addresses', 'All IPv4 networks', 'All IPv6 networks', 'All gateways', 'My IPv4 networks', 'My IPv6 networks', 'My gateways'.

=== Contact ===

Clicking 'Contact' takes you to the 'CONTACT US' form, where you can reach out to Portal admins with inquiries, reporting issues, etc.

[[File:contact-us-v3.png|750px]]

=== API ===

An [[API]] enables programs to access data maintained in the Portal.

== Helpful resources ==

'''Subnet calculator''': [https://www.calculator.net/ip-subnet-calculator.html https://www.calculator.net/ip-subnet-calculator.html]

[[Category:How-To Guides]]
[[Category:Portal]]
[[Category:Portal Workflows]]

AMPRNet VPN

2026-03-01T00:14:59Z

KI5QKX: mw push

#REDIRECT [[OH7LZB VPN]]
[[Category:VPN]]

K7ILO'S Two Interface Debian 11 AmprNet Gateway Build in layman's terms

2026-03-01T00:14:59Z

KI5QKX: mw push

Initial Server/Gateway Machine Setup

The computer I had laying around to build my basic server/gateway was an old Dell OptiPlex GX280 (Intel 3.2Ghz CPU) with 3GB’s of RAM, 160GB HD (Yeah, I know overkill but that's the HD that was in the machine) and two 1Gb Ethernet adapters, 1 built-in and 1 Intel PCI Ethernet adapter I installed, where..
1. the built-in Ethernet adapter is to my router for my Internet connection.
2. the PCI Ethernet adapter serves my AmprNet Network.

Because of the architecture of the computer, I had to use the 32bit version of Debian 11.5.0 netinstall image for this setup. I like Debian mainly because, well because I like it, LOL. BTW, it is not in the scope of these instructions to show you how to install Debian 11 so please search Google for information on the topic if needed. Keep in mind though the SSH server and the standard system utilities were the only software options I selected for my bare Debian 11 installation.

After the installation is completed, log in as root and make sure Debian has the latest fixes and patches by typing:
apt update && apt full-upgrade -y

During these procedures I used root directly since to me, it was quicker to setup the server/gateway. But if you want to use sudo, it is not installed by default on Debian 11 so again search Google on how to install it. There are a lot of resources on the subject. I installed sudo after getting the server/gateway up and running for future administration and security. If the server/gateway does any updates from the command's above, reboot to make sure updates take affect (old Windows habit). Type:
reboot

Install other software for this setup.

Descriptions..
1. screen (optional): This software allows you to connect back to a particular session if you are remote and loose connection to your server/gateway.
2. compile tools: Needed to compile software.
3. iptables-persistent: This installs the most used Linux firewall iptables and it's tools, well to my knowledge. When asked, it's not necessary to save the current v.4 and v.6 iptables rules.
4. psmisc: Installed for the killall command. Used for the update-server script found in the Optional Software and Task's section.
5. curl (optional): Used to install optional software found in the Optional Software and Task's section.
6. cron: Used to schedule task. This is more than likely already installed.
7. tcpdump: Useful networking tool.
8. traceroute: Useful networking tool. This is more than likely already installed.

To install these, Type:
apt install -y screen build-essential iptables-persistent psmisc curl tcpdump

Reboot. (Again, old Windows habit) Type:
reboot

Now let's turn this server machine into an AmprNet Gateway (Updates Coming so please check back soon)

[[Category:How-To Guides]]
[[Category:Infrastructure]]
[[Category:Gateways]]

Contribute

2026-03-01T00:14:59Z

KI5QKX: mw push

#REDIRECT [[Contributing]]
[[Category:Documentation]]

Networks that use 44Net

2026-03-01T00:14:58Z

KI5QKX: mw push

* [https://wiki.oevsv.at/wiki/Kategorie:Digitaler_Backbone The Austrian Ham Digital Backbone]
* [http://de.ampr.org/hamnet The German HAMNET]
* [http://www.cisar.it/radiowiki/index.php?title=Italian_Cisar_Radio_Amateur_WiFi_Network_Overview:_CisarNet The Italian CisarNet]
* [http://www.hamwan.org/t/Wiki+Home+Page The HamWAN]
* [http://www.hamnet.es/ HAMNET Iberia]

[[Category:Reference]]
[[Category:Community]]

Getting started with Linux and packet radio

2026-03-01T00:14:58Z

KI5QKX: mw push

* [http://www.tapr.org/pdf/AX25.2.2.pdf The AX.25 protocol specification]
* [http://www.tldp.org/HOWTO/AX25-HOWTO/index.html Jeff Tranter's Linux AX.25 Howto]
* [http://www.qsl.net/k/kb9mwr/projects/wireless/plan.html KB9MWR Using Part 15 Wireless Ethernet Devices for Amateur Radio]
* [http://www.qsl.net/k/kb9mwr/projects/wireless/70cm-ATV-HSMM.html KB9MWR 70cm Amateur Television and HSMM]
* [http://www.febo.com/packet N8UR’s packet radio pages]
* [http://vger.kernel.org/vger-lists.html#linux-hams Linux-hams mailing list]

[[Category:Reference]]
[[Category:Getting Started]]

44Net mailing list

2026-03-01T00:14:57Z

KI5QKX: mw push

ARDC now has several groups.io channels you can subscribe to, including one specifically for AMPRNet [https://ardc.groups.io/g/44net https://ardc.groups.io/g/44net] which is replacing the old style mailing list below.

The [https://mailman.ampr.org/mailman/listinfo/44net discussion list] is a mailing list where amprnet users and gateway operators discuss all things [[AMPRNet]]. Subscribe and browse the archives to learn more!

* [https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/ https://mailman.ardc.net/mailman3/postorius/lists/44net.mailman.ampr.org/]

[[Category:Reference]]
[[Category:Community]]

Ampr-map

2026-03-01T00:14:57Z

KI5QKX: mw push

== Viewing the map ==

We have a visual map of the AMPR network available, on which users can choose to voluntarily publish their callsign/locator, which is then shown on a vector map of the world.
Generally, the positions will time out after 1 hour.

On click on the dots on the map, additional information will be shown: type, IP, locator and seconds since the last information received.

No information are permanently stored on the server side.

To opt out, just stop sending position reports...

Some technical info:
<blockquote>
The server uses the following incoming ports: 
  - ampr-ripd uses UDP/59001, 
  - amprd uses UDP/59002, 
  - all other http requests use TCP/59001 
Map events sent to your browser are in json format and use websockets or event-stream as a fallback.
</blockquote>

The map can be reached via these URLs:

http://www.yo2loj.ro/ampr-map/
http://yo2loj.ampr.org/ampr-map/

== Sending the location to the map ==

Depending on your system setup and node type, there are 5 methods to get your positions on the map.

Please replace the callsign and position with your own in the given examples.

Position reports are case insensitive and will all be converted to upper case.

;; 1. ampr-ripd:

Add the parameter '-L <callsign@<locator>' to the ampr-ripd command line.

ampr-ripd [...other parameters...] -L N0CALL-T@kn01aa

Positions will be shown as green dots.

;; 2. amprd:

Add your locator in the configuration file, under your interface section:

call_home = N0CALL-T@KN05or

Positions will be shown as blue dots.

;; 3. Mikrotik routers

Set up a cyclic job to run a script in which you request a specific URL, using the command, e.g. every 5 minutes:

/tool fetch mode=http url="<nowiki>http://44.182.21.1:59001/mikrotik?id=N0CALL-T@kn01aa</nowiki>" keep-result=no

Positions will be shown as pink dots.

;; 4. 'Radio' positions

These positions are dedicated to stations not directly reachable via 44Net, and are sent out by other systems in their name.

To do this, do a periodic fetch on the following URL:

<nowiki>http://44.182.21.1:59001/radio_gateway?id=n0call-t@kn01aa</nowiki>

For radio stations, the position time-out is 3 hours.

Positions will be shown as yellow antenna symbols.

;; 5. Generic position reports

For other (generic) systems, do a periodic fetch on the following URL:

<nowiki>http://44.182.21.1:59001/generic?id=n0call-t@kn01aa</nowiki>

Positions will be shown as grey dots.

== Map server source code ==

The map server's source code can be found in the AMPR GIT repository:

<nowiki>https://git.ampr.org/yo2loj/ampr-map-server</nowiki>

[[Category:Reference]]
[[Category:Infrastructure]]
[[Category:Core Services]]

Setting up a complete gateway on Ubiquiti EdgeRouter

2026-03-01T00:14:57Z

KI5QKX: mw push

#REDIRECT [[Installing ampr-ripd on a Ubiquiti EdgeRouter or EdgeRouter X]]
[[Category:Infrastructure]]
[[Category:Gateways]]

Installing ampr-ripd on a Ubiquiti EdgeRouter or EdgeRouter X

2026-03-01T00:14:56Z

KI5QKX: mw push

'''These setup instructions are not related to any other ones mentioned for an Ubiquity EdgeRouter, describing a simple IPIP tunnel setup and do not assume you have done those steps, nor need you to do anything described there.'''

== Info ==

These are the steps for setting up a fully functional AMPR gateway on Ubiquiti's EdgeRouter Lite and EdgeRouter-X.
Tested and found working on the following firmware versions:
ER3 Lite 1.10.8
ER3 Lite 1.10.9
ER-X 1.10.9
ER3 Lite 2.0.0
ER3 Lite 2.0.1
ER3 Lite 2.0.3
ER3 Lite 2.0.4
ER3 Lite 2.0.5
ER3 Lite 2.0.8
ER3 Lite 2.0.9
ER3 Lite v2.0.9-hotfix.2
ER3 Lite v2.0.9-hotfix.7

'''NOTE: THE SETUP SCRIPT DOES NOT SECURE YOUR ROUTER. YOU NEED TO SET UP FIREWALL RULES YOURSELF.'''

We start assuming you have a complete working and configured router, that already has internet access (a configured WAN port and a local LAN).

; For technical reasons, this set-up does not support dynamic assigned WAN addresses. If you have a dynamic IP, this setup can only be used in the primary router's DMZ.

Some technical details:
<blockquote>
We will use an IPIP tunnel interface called 'tun44' connected to your external interface (with a fixed public IP or an interface in a DMZ). All ampr routes will be created in routing table 44. Routing table 45 will be used for routing requests from the public internet back via the ampr-gw.
</blockquote>

; On a firmware update, you need to reinstall ampr-ripd, since the file system gets replaced. The other settings like tunnel setup and the status wizard will stay.

== Router preparation ==
Our first step is to set up the router to accept IPENCAP (protocol 4 frames on the WAN interface).

Under "Firewall/NAT" and then the "Firewall Policies" tab edit your WAN_LOCAL ruleset (the interface/local handles the access to the router - if there is no such ruleset, you need to create it).
Usually it holds 2 rules, with a default policy of 'drop':
- accept established/related
- drop invalid

Now add a new rule:
- description: IPIP from WAN
- Action: accept
- Protocol: choose by name -> ipencap

...and save. You need to drag this rule into the first position of the ruleset and save the ruleset order

You may consider adding a similar rule for 'icmp' on WAN since this really helps debugging and ensures proper error handling (no, it will not compromise security since your gateway is detectable anyway).

== Tunnel setup ==
First add tunnel interface. You need to reserve an AMPR address from your AMPR subnet for the tunnel interface.
If you have a /32 assignment, you need to use that one, else pick an unused address.

Use the name 'tun44' for the tunnel, don't get creative since the script depends on this name.

- Config Tree -> add tun44 -> Update List

- tun44:
address: <your AMPR IP assigned to the router>/32 (this needs to be /32, no matter your allocated subnet, see above)
description: AMPR GW
encapsulation: ipip
local-ip: <your WAN IP - ISP assigned or router's DMZ IP>
remote-ip: 0.0.0.0 (this MUST be 0.0.0.0, no matter what, to allow P2MP connections)

- tun44 -> disable-link-detect, press + right of it to enable

- Press Preview and Apply

If you prefer to do it by CLI:
ubnt@YO2LOJ-ER3:~$ configure
ubnt@YO2LOJ-ER3:~$ set interfaces tunnel tun44
ubnt@YO2LOJ-ER3:~$ set interfaces tunnel tun44 local-ip <put the external ip>
ubnt@YO2LOJ-ER3:~$ set interfaces tunnel tun44 remote-ip 0.0.0.0
ubnt@YO2LOJ-ER3:~$ set interfaces tunnel tun44 encapsulation ipip
ubnt@YO2LOJ-ER3:~$ set interfaces tunnel tun44 address <44Net router ip>/32
ubnt@YO2LOJ-ER3:~$ set interfaces tunnel tun44 description "AMPR GW"
ubnt@YO2LOJ-ER3:~$ set interfaces tunnel tun44 disable-link-detect
ubnt@YO2LOJ-ER3:~$ commit; save

== Installing ampr-ripd ==
Download your packages from here (read this section to the end...):

Be certain to get the package that fits your router model. They use different processor types so they will not be compatible

Find the EdgeRouter setup package here: http://www.yo2loj.ro/hamprojects/Ampr_EdgeRouter.tgz (mips64)

For the EdgeRouterX setup use this one: http://www.yo2loj.ro/hamprojects/Ampr_EdgeRouterX.tgz (mipsel)

 In short, get it, unpack on the router and run the install.sh script.

Then edit your startup script if needed, and run it.

 Now the details...

a. First, log in and become root (don't omit that '-'):
Welcome to EdgeOS
ubnt@YO2LOJ-ER3:~$ sudo su -

b. Now download the correct package as described in the links above and unpack it:

EdgeRouter Lite3, possibly ER4, ER6 (mips64):
root@YO2LOJ-ER3:~# curl http://yo2loj.ro/hamprojects/Ampr_EdgeRouter.tgz -o er.tgz
(you should get some download stats here...)
EdgeRouter X (mipsel):
root@YO2LOJ-ERX:~# curl http://yo2loj.ro/hamprojects/Ampr_EdgeRouterX.tgz -o er.tgz
(you should get some download stats here...)
Check and unpack:
root@YO2LOJ-ER3:~# ls
er.tgz
root@YO2LOJ-ER3:~# tar -xf er.tgz
c. install the package:
root@YO2LOJ-ER3:~# ./install.sh

d. edit the startup script to fit your needs. This is only needed if your router is behind NAT or you need to reject specific subnets. Edit only the -a options like below, don't touch the rest. If you want to have your position shown on the ampr map, also add the -L option using your callsign and your QTH locator ( -L your-call@AA00aa ).

If you are using pppoe, the local gateway can not be properly detected by ampr-ripd, so an additional -g parameter is needed.

root@YO2LOJ-ER3:~# cd /etc
root@YO2LOJ-ER3:/etc# vi ampr.sh
<press insert to start editing>
[...]
ampr-ripd -s -t 44 -i tun44 -m 90 -g pppoe0 -a 44.128.1.0/24,44.128.2.0/24,your.gw.com (adapt this list to your needs - commna separated, no spaces)
~
~
~
<press esc>:wq (to save and exit - yes, vi is strange)

e. Now run the startup script:
root@YO2LOJ-ER3:/etc# ./ampr.sh
(On router restart, this will happen automatically)

'''NOTE: THE SETUP SCRIPT DOES NOT SECURE YOUR ROUTER. YOU NEED TO SET UP FIREWALL RULES YOURSELF.'''

== Adding basic security ==
Now your 44 subnet is still wide open for access, both from other users (let's assume we can trust those), and from the internet.

We need to add 2 rulesets in Firewall/NAT to get some kind of minimal protection:

Create an ruleset called TUNNEL_FORWARD (or something suggestive) with a default drop policy.

Set interface for the ruleset to 'tun44' and direction to 'in'.

This will hold 3 rules (take care, order is important):

1. Allow access from ampr hosts to your subnet:
- Description: Allow access to hosts from AMPR
- Action: Accept
- Protocol: All protocols
- Source: 44.0.0.0/9
- Destination: <your subnet>
2. Second rule to allow access from ampr hosts to your subnet:
- Description: Allow access to hosts from AMPR
- Action: Accept
- Protocol: All protocols
- Source: 44.128.0.0/10
- Destination: <your subnet>
3. Rule to allow all establihed and related traffic:
- Description: Allow Established/Related
- Action: Accept
- Protocol: All protocols
- State: Established, Related

Also we need to protect router access itself, so we need another ruleset, say TUNNEL_LOCAL, also with a default drop policy.

Set interface for the ruleset to 'tun44' and direction to 'local'.

One minimal rule is required, to accept incoming RIP packets from the gateway:
- Description: Allow incoming RIP
- Action: Accept
- Protocol: UDP
- Source Port: 520
- Destination Port: 520

If you want to allow access to the router itself, the rules should include the same as for the forward section.

If router access should not be permitted, then only add rule number 3 (established/related) from above:
- Description: Allow Established/Related
- Action: Accept
- Protocol: All protocols
- State: Established, Related

== Finishing touches ==

It is a good idea to disable ubnt discovery protocol on our tunnels.

In this case, the easiest way is to disable it completely:
- go to Config Tree -> service -> ubnt-discover
- click the '+' sign after 'disable'
This will completely disable ubnt neighbor discovery.

== Adding a local AMPR subnet ==
To use a local AMPR subnet, just assign the router's AMPR IP with the proper subnet mask to a local network interface (eth2-3, switch0 on the ER-X, or even a VLAN), using the regular EdgeRouter management interface. Remember to also set up the proper firewall rules to allow or disallow access to your hosts (if you use the rules as described in the previous chapter, 44Net hosts will be allowed to access your whole network, while access from the internet is prohibited).

== Status wizard ==
Optionally you can install a status page in the wizard section.

Download here: http://www.yo2loj.ro/hamprojects/Ampr_Status_Wizard.tar and add it in your configuration wizard tab.

On firmware update, there is no need to reinstall the wizard.

[[Category:How-To Guides]]
[[Category:Routing]]

Setting up a gateway on a VyOS instance

2026-03-01T00:14:56Z

KI5QKX: mw push

== Setting up a gateway on VyOS ==

VyOS is a Network Operating System, similar to pfSense, where everything is done on CLI. This is a fork of the base Vyatta network OS, which Ubiquiti uses for most of their products.

== Assumptions / pre requisites ==

• You have already registered with AMPRNet and got your 44.0.0.0/9 or 44.128.0.0/10 allocation and it is showing in the encap.txt file

• You have registered some hosts in the AMPRNet DNS like <your call sign>.ampr.org

• You have already setup VyOS and know how to get around linux. This guide only covers the AMPR connection, not a complete setup.

== Warning!! ==

The author does not assume responsibility if you mess up/brick your router. Please make sure to back up your VyOS configuration prior to any change.
Also make sure you know how to restore your configuration and you know how to restore your router to factory defaults if everything else fails.

== Process of getting started ==

We will begin by getting the Jesse repositories installed onto the router.
To do this, run the following command:
* sudo curl https://debgen.simplylinux.ch/txt/jessie/sources_fae18d34d49f95f3a5a8a2e2c7b3a633af708da9.txt | sudo tee /etc/apt/sources.list.d/00Debian

Next, run following commands:

*sudo apt-get -f install
*sudo apt-get update

'''NOTE: DO ''NOT'' RUN APT-GET UPGRADE!!!! This will break many things within VyOS'''

From that point it is possible to install many packages from Debian "jessie" distribution.

'''OPTIONAL''': As in VyOS there is no file manager. To make life a bit easier, you can install Midnight Commander:
sudo apt-get install mc

Now, it's time to configure access to 44-net.

== Downloading the Source Files for AMPR-RIPd and Compiling ==

What we can do now, is create a folder called ampr within our home directory, and install the materials to build out ampr-ripd.

So do the following:
* sudo -i # This will log you in as root
* apt-get update # Just to make sure your lists are updated
* apt-get install -y build-essential # This installs all the build materials needed to build our binary
* mkdir /home/ampr && cd /home/ampr # Self-Explanatory
* wget http://www.yo2loj.ro/hamprojects/ampr-ripd-1.15.tgz # Again, self-explanatory
* tar -xvzf ampr-ripd-1.15.tgz # Extracts the compressed file
* rm -rf ampr-ripd-1.15.tgz # Deletes it after extraction
* make # Compiles
* cp ampr-ripd /usr/local/bin/

After this, you need to find out the password for the RIP broadcasts. These broadcasts run every 5 minutes. Run the following command and wait:
./find_pass.sh

Once it shows the password, Ctrl-C out of there and copy the password down. You will need it.
Run the following after your done:
* rm -rf /home/ampr/*

== Creating the ax25 script ==

Copy the text linked here[https://hastebin.com/raw/fipacatota] to a text editor, like notepad, and edit the portions that are commented with <> and []:

----

Once done editing, you will copy the text and put it in your clipboard.
Open back up the terminal, and run the following:
* sudo nano /etc/rc.local
You should be at a screen with some text and with some key-commands on the bottom

Using your arrow keys, move your cursor above the part that says "# Do not remove----" and paste the contents of your clipboard into the terminal by right-clicking. You can close out the file once everything is in there.
Note: Close out of the file and save it, by doing Ctrl-X, then pressing 'Y', then 'Enter'.

== Script ==
Fire-up the ax25 script by just running 'ax25' and wait. Remember, there is a rip44 broadcast every 5 minutes.
After 10-15 minutes, check your routing table.

To check your routing table:
ip route show table 1
Table should be filled-up with many entries pertaining to AMPR
They should mimic /var/lib/ampr-ripd/encap-txt

[[Category:How-To Guides]]
[[Category:Infrastructure]]
[[Category:Gateways]]