44Net Wiki - Recent changes [en]

Get Help

KI5QKX — Wed, 15 Apr 2026 17:15:33 GMT

mw push

← Older revision		Revision as of 17:15, 15 April 2026
Line 41:		Line 41:
	Good problem statements get better answers faster.		Good problem statements get better answers faster.

	~~== How help works here ==~~		For the broader explanation of how discussion, coordination, and shared knowledge work here, see [[Community]].

	~~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 ==		== Related pages ==

Contributing

KI5QKX — Wed, 15 Apr 2026 17:15:33 GMT

mw push

@@ Line 1: / Line 1: @@
 {{DISPLAYTITLE:Contributing}}
-== What this page is ==
+This page explains how to contribute useful work to 44Net docs and systems.
-This page explains how to contribute useful work to 44Net docs and operations.
+It is for operators, maintainers, developers, and participants who want to help.
-== What you can do today ==
+== Why contribute ==
-== What this page will cover ==
+ARDC staff help produce documentation and maintain software tools, but the community is what keeps 44Net running and usable.
-* Contribution workflow for wiki content.
-* Standards for operational accuracy and scope.
+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.
-* How to document procedures with rollback and safety notes.
-* Review expectations for networking and policy content.
+Many of the best improvements start the same way:
-* Ownership and maintenance for long-lived pages.
 == Related pages ==
-* [[Community|Community and mailing lists]]
+* [[Community]]
 * [[Governance|Governance]]
 * [[Policies|Policies]]
@@ Line 26: / Line 103: @@
 * [[Routing|Routing and connectivity]]
 [[Category:Documentation]]

Community

KI5QKX — Wed, 15 Apr 2026 17:15:33 GMT

mw push

← Older revision		Revision as of 17:15, 15 April 2026
Line 10:		Line 10:
	More than just a block of IP addresses, 44Net is also a long-running technical 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.		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.		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.
Line 28:		Line 28:

	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.		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 ==		== Groups.io and discussion channels ==
Line 37:		Line 39:
	* [https://ardc.groups.io/g/44Net-connect 44Net Connect]: discussions specifically about the 44Net Connect project		* [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/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/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/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		* [https://ardc.groups.io/g/wiki ARDC Wiki]: discussion related to the wiki and documentation work
Line 73:		Line 75:
	=== Asking questions ===		=== 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.		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 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:		For a practical checklist of what context to include, see [[Get Help]].

	* 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 ===		=== Sharing knowledge and experience ===
Line 97:		Line 93:
	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.		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.		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.

	== ~~Contributing~~ ==		== 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:

	~~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.~~		* [[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

	~~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.~~		== Contributing ==

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

	~~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~~.		If you want to help improve the wiki, contribute code, test ideas, or share a project writeup, see [[Contributing]].

Get Help

KI5QKX — Wed, 15 Apr 2026 15:47:48 GMT

mw push

New page

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

KI5QKX — Wed, 15 Apr 2026 15:40:38 GMT

mw push

New page

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

KI5QKX — Wed, 15 Apr 2026 15:40:38 GMT

mw push

Show changes