44Net Wiki - User contributions [en]

44Net Connect/Quick Start/Raspberry Pi

2026-05-29T22:31:38Z

KN6DWI: Added section on starting automatically with systemd

<div class="toclimit-3">
__TOC__
</div>
{{DISPLAYTITLE:44Net Connect Quick Start: Raspberry Pi}}

=== What you need ===

* A 44Net Portal account
* A verified amateur radio callsign
* A Raspberry Pi with a working Raspberry Pi OS installation
* Some sort of Internet access

If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted|44Net: Get Started]] for instructions.

== Install Dependencies ==

=== Step 1: Ensure your OS is up to date ===
Open a terminal and run <code>sudo apt-get update</code>, then <code>sudo apt-get upgrade</code>.

=== Step 2: Install wireguard and systemd-resolved ===
Run <code>sudo apt-get install wireguard systemd-resolved</code>, then restart your Raspberry Pi. Restarting is required for <code>systemd-resolved</code> to function.

=== Step 3: Verify that systemd-resolved is enabled ===
Run <code>systemctl status systemd-resolved</code>. If the unit is running without issues, there will be a green asterisk or circle at the top left. The second line, beginning with "Loaded," should indicate that the unit is enabled. If it's not, run <code>systemctl enable systemd-resolved</code> to enable the unit. This will ensure that the unit starts automatically when your Raspberry Pi boots from now on.

The third line, beginning with "Active," should indicate that the unit is active (running).
If it's not, run <code>systemctl start systemd-resolved</code> to start the unit. This will ensure that the unit is currently running.

== Create your Connect tunnel ==

{{Step|
=== Step 1: Sign in to 44Net Connect ===
{{StepImage|file=Click to Log In.png}}
{{StepText|
* Visit [https://connect.44net.cloud The 44Net Connect dashboard].
* Click the “Log In to Get Started” button.
* Sign in with your 44Net Portal account credentials.

}}
}}

{{Step|
=== Step 2: Create your first tunnel ===
{{StepImage|file=Create Tunnel.png}}
{{StepText|
* On the dashboard page, click the “Create Tunnel” button.
}}
}}

{{Step|
=== Step 3: Choose region and node ===
{{StepImage|file=Choose Region and Node.png}}
{{StepText|
* In the list of regions, click the region closest to you.
* Nodes available in that region will appear.
* Click a node to select it as your endpoint.

You can change endpoints later if needed.
}}
}}

{{Step|
=== Step 4: Name your tunnel ===
{{StepImage|file=Name Tunnel.png}}
{{StepText|
* Enter a name for your tunnel (e.g. “Home Laptop” or “Raspberry Pi”)
}}
}}

{{Step|
=== Step 5: Save your new tunnel ===
{{StepImage|file=Complete Tunnel Creation.png}}
{{StepText|
* Check or uncheck the option to receive tunnel details via email.
* Click the “Create Tunnel” button.
* Review the confirmation dialog and click “Save Changes” to proceed.
}}
}}

== Configure your WireGuard client ==
* On your Raspberry Pi, create a new file for your WireGuard configuration in <code>/etc/wireguard/</code>, for example <code>/etc/wireguard/wg0.conf</code>.
* You can name this file however you want, but this file name will become the name of your WireGuard interface.
* Paste the configuration text in from 44Net Connect, or if you prefer to use the file that was emailed to you, upload that one.

[[File:wireguard_tunnel_config.png|500px]]

The first time you create your tunnel, the private key will be present in the config for you to copy. Every subsequent time you view the config in the portal, the private key will not be shown. Saving a backup of the private key in a secure place is recommended.

After creating your config file, set its permissions so that only the owner has read or write permissions. This can be done with the command <code>sudo chmod 600 /etc/wireguard/wg0.conf</code>. (Replace <code>wg0</code> with the name of your file.)

== Activate and connect ==
=== Activate your tunnel ===
* Run the command <code>wg-quick up wg0</code> (replace <code>wg0</code> with the name of your configuration file if different).
* If at this step WireGuard reports the error <code>Failed to activate service 'org.freedesktop.resolve1': timed out</code>, you may have forgotten to restart your Pi after installing <code>systemd-resolved</code>.

=== Confirm Connection in the Connect dashboard ===
* Your tunnel status should show as "Active" with a green indicator.
[[File:wireguard_tunnel_connected.png|500px]]
* The <code>Endpoint</code> field should show the IP address your device is connecting from, as well as the port it's using. This is not the 44Net IP from which your device is publicly accessible.

=== Other Ways to Confirm Connection ===
* Visit https://connect.44net.cloud/myip in your browser, or query it from the command line using <code>curl https://connect.44net.cloud/myip</code>
* Use <code>traceroute</code> to inspect the path between you and some other device, such as <code>traceroute 1.1.1.1</code>. When the tunnel is working, the first hop will be through a 44Net gateway, so its IP will be in the <code>44.0.0.0/9</code> or <code>44.128.0.0/10</code> subnet.

== Starting the Tunnel Automatically ==
* On Linux distributions that use <code>systemd</code>, creating a <code>systemd</code> unit is the recommended way to automatically start the tunnel.
* Create a unit file in <code>/etc/systemd/system/</code>, for example <code>/etc/systemd/system/44net-tunnel.service</code>.
* Paste the following into the file.
<nowiki>
[Unit]
Description=WireGuard single device 44Net Connect tunnel
Requires=network-online.target

[Service]
Type=oneshot
RemainAfterExit=true

# Edit these lines if your config file is named differently.
ExecStart=wg-quick up /etc/wireguard/wg0.conf
ExecStop=wg-quick down /etc/wireguard/wg0.conf

[Install]
WantedBy=multi-user.target
</nowiki>

* If your config file is named something other than <code>wg0.conf</code>, edit the <code>ExecStart</code> and <code>ExecStop</code> lines so that they reflect the correct file name.
* Enable and start the service by running <code>sudo systemctl enable --now 44net-tunnel.service</code>. If you named your unit file something else, use that name instead of <code>44net-tunnel.service</code>.
* Verify that the service has started by running <code>systemctl status 44net-tunnel.service</code> and checking that it says enabled and active, the same way we previously checked that systemd-resolved was working.

[[Category:Tutorial]]
[[Category:How-To]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]
[[Category:Getting Started]]

44Net Connect/Quick Start/Raspberry Pi

2026-05-29T21:53:35Z

KN6DWI: Added "Other Ways to Confirm Connection" section

<div class="toclimit-3">
__TOC__
</div>
{{DISPLAYTITLE:44Net Connect Quick Start: Raspberry Pi}}

=== What you need ===

* A 44Net Portal account
* A verified amateur radio callsign
* A Raspberry Pi with a working Raspberry Pi OS installation
* Some sort of Internet access

If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted|44Net: Get Started]] for instructions.

== Install Dependencies ==

=== Step 1: Ensure your OS is up to date ===
Open a terminal and run <code>sudo apt-get update</code>, then <code>sudo apt-get upgrade</code>.

=== Step 2: Install wireguard and systemd-resolved ===
Run <code>sudo apt-get install wireguard systemd-resolved</code>, then restart your Raspberry Pi. Restarting is required for <code>systemd-resolved</code> to function.

=== Step 3: Verify that systemd-resolved is enabled ===
Run <code>systemctl status systemd-resolved</code>. If the unit is running without issues, there will be a green asterisk or circle at the top left. The second line, beginning with "Loaded," should indicate that the unit is enabled. If it's not, run <code>systemctl enable systemd-resolved</code> to enable the unit. This will ensure that the unit starts automatically when your Raspberry Pi boots from now on.

The third line, beginning with "Active," should indicate that the unit is active (running).
If it's not, run <code>systemctl start systemd-resolved</code> to start the unit. This will ensure that the unit is currently running.

== Create your Connect tunnel ==

{{Step|
=== Step 1: Sign in to 44Net Connect ===
{{StepImage|file=Click to Log In.png}}
{{StepText|
* Visit [https://connect.44net.cloud The 44Net Connect dashboard].
* Click the “Log In to Get Started” button.
* Sign in with your 44Net Portal account credentials.

}}
}}

{{Step|
=== Step 2: Create your first tunnel ===
{{StepImage|file=Create Tunnel.png}}
{{StepText|
* On the dashboard page, click the “Create Tunnel” button.
}}
}}

{{Step|
=== Step 3: Choose region and node ===
{{StepImage|file=Choose Region and Node.png}}
{{StepText|
* In the list of regions, click the region closest to you.
* Nodes available in that region will appear.
* Click a node to select it as your endpoint.

You can change endpoints later if needed.
}}
}}

{{Step|
=== Step 4: Name your tunnel ===
{{StepImage|file=Name Tunnel.png}}
{{StepText|
* Enter a name for your tunnel (e.g. “Home Laptop” or “Raspberry Pi”)
}}
}}

{{Step|
=== Step 5: Save your new tunnel ===
{{StepImage|file=Complete Tunnel Creation.png}}
{{StepText|
* Check or uncheck the option to receive tunnel details via email.
* Click the “Create Tunnel” button.
* Review the confirmation dialog and click “Save Changes” to proceed.
}}
}}

== Configure your WireGuard client ==
* On your Raspberry Pi, create a new file for your WireGuard configuration in <code>/etc/wireguard/</code>, for example <code>/etc/wireguard/wg0.conf</code>.
* You can name this file however you want, but this file name will become the name of your WireGuard interface.
* Paste the configuration text in from 44Net Connect, or if you prefer to use the file that was emailed to you, upload that one.

[[File:wireguard_tunnel_config.png|500px]]

The first time you create your tunnel, the private key will be present in the config for you to copy. Every subsequent time you view the config in the portal, the private key will not be shown. Saving a backup of the private key in a secure place is recommended.

After creating your config file, set its permissions so that only the owner has read or write permissions. This can be done with the command <code>sudo chmod 600 /etc/wireguard/wg0.conf</code>. (Replace <code>wg0</code> with the name of your file.)

[[Category:Tutorial]]
[[Category:How-To]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]
[[Category:Getting Started]]

== Activate and connect ==
=== Activate your tunnel ===
* Run the command <code>wg-quick up wg0</code> (replace <code>wg0</code> with the name of your configuration file if different).
* If at this step WireGuard reports the error <code>Failed to activate service 'org.freedesktop.resolve1': timed out</code>, you may have forgotten to restart your Pi after installing <code>systemd-resolved</code>.

=== Confirm Connection in the Connect dashboard ===
* Your tunnel status should show as "Active" with a green indicator.
[[File:wireguard_tunnel_connected.png|500px]]
* The <code>Endpoint</code> field should show the IP address your device is connecting from, as well as the port it's using. This is not the 44Net IP from which your device is publicly accessible.

=== Other Ways to Confirm Connection ===
* Visit https://connect.44net.cloud/myip in your browser, or query it from the command line using <code>curl https://connect.44net.cloud/myip</code>
* Use <code>traceroute</code> to inspect the path between you and some other device, such as <code>traceroute 1.1.1.1</code>. When the tunnel is working, the first hop will be through a 44Net gateway, so its IP will be in the <code>44.0.0.0/9</code> or <code>44.128.0.0/10</code> subnet.

44Net Connect/Quick Start/Raspberry Pi

2026-05-29T21:24:02Z

KN6DWI: Added instruction to set chmod 600 permissions for WireGuard config file

<div class="toclimit-3">
__TOC__
</div>
{{DISPLAYTITLE:44Net Connect Quick Start: Raspberry Pi}}

=== What you need ===

* A 44Net Portal account
* A verified amateur radio callsign
* A Raspberry Pi with a working Raspberry Pi OS installation
* Some sort of Internet access

If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted|44Net: Get Started]] for instructions.

== Install Dependencies ==

=== Step 1: Ensure your OS is up to date ===
Open a terminal and run <code>sudo apt-get update</code>, then <code>sudo apt-get upgrade</code>.

=== Step 2: Install wireguard and systemd-resolved ===
Run <code>sudo apt-get install wireguard systemd-resolved</code>, then restart your Raspberry Pi. Restarting is required for <code>systemd-resolved</code> to function.

=== Step 3: Verify that systemd-resolved is enabled ===
Run <code>systemctl status systemd-resolved</code>. If the unit is running without issues, there will be a green asterisk or circle at the top left. The second line, beginning with "Loaded," should indicate that the unit is enabled. If it's not, run <code>systemctl enable systemd-resolved</code> to enable the unit. This will ensure that the unit starts automatically when your Raspberry Pi boots from now on.

The third line, beginning with "Active," should indicate that the unit is active (running).
If it's not, run <code>systemctl start systemd-resolved</code> to start the unit. This will ensure that the unit is currently running.

== Create your Connect tunnel ==

{{Step|
=== Step 1: Sign in to 44Net Connect ===
{{StepImage|file=Click to Log In.png}}
{{StepText|
* Visit [https://connect.44net.cloud The 44Net Connect dashboard].
* Click the “Log In to Get Started” button.
* Sign in with your 44Net Portal account credentials.

}}
}}

{{Step|
=== Step 2: Create your first tunnel ===
{{StepImage|file=Create Tunnel.png}}
{{StepText|
* On the dashboard page, click the “Create Tunnel” button.
}}
}}

{{Step|
=== Step 3: Choose region and node ===
{{StepImage|file=Choose Region and Node.png}}
{{StepText|
* In the list of regions, click the region closest to you.
* Nodes available in that region will appear.
* Click a node to select it as your endpoint.

You can change endpoints later if needed.
}}
}}

{{Step|
=== Step 4: Name your tunnel ===
{{StepImage|file=Name Tunnel.png}}
{{StepText|
* Enter a name for your tunnel (e.g. “Home Laptop” or “Raspberry Pi”)
}}
}}

{{Step|
=== Step 5: Save your new tunnel ===
{{StepImage|file=Complete Tunnel Creation.png}}
{{StepText|
* Check or uncheck the option to receive tunnel details via email.
* Click the “Create Tunnel” button.
* Review the confirmation dialog and click “Save Changes” to proceed.
}}
}}

== Configure your WireGuard client ==
* On your Raspberry Pi, create a new file for your WireGuard configuration in <code>/etc/wireguard/</code>, for example <code>/etc/wireguard/wg0.conf</code>.
* You can name this file however you want, but this file name will become the name of your WireGuard interface.
* Paste the configuration text in from 44Net Connect, or if you prefer to use the file that was emailed to you, upload that one.

[[File:wireguard_tunnel_config.png|500px]]

The first time you create your tunnel, the private key will be present in the config for you to copy. Every subsequent time you view the config in the portal, the private key will not be shown. Saving a backup of the private key in a secure place is recommended.

After creating your config file, set its permissions so that only the owner has read or write permissions. This can be done with the command <code>sudo chmod 600 /etc/wireguard/wg0.conf</code>. (Replace <code>wg0</code> with the name of your file.)

[[Category:Tutorial]]
[[Category:How-To]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]
[[Category:Getting Started]]

== Activate and connect ==
=== Activate your tunnel ===
* Run the command <code>wg-quick up wg0</code> (replace <code>wg0</code> with the name of your configuration file if different).
* If at this step WireGuard reports the error <code>Failed to activate service 'org.freedesktop.resolve1': timed out</code>, you may have forgotten to restart your Pi after installing <code>systemd-resolved</code>.

=== Confirm Connection in the Connect dashboard ===
* Your tunnel status should show as "Active" with a green indicator.
[[File:wireguard_tunnel_connected.png|500px]]
* The <code>Endpoint</code> field should show the IP address your device is connecting from, as well as the port it's using. This is not the 44Net IP from which your device is publicly accessible.

44Net Connect/Quick Start/Raspberry Pi

2026-05-29T19:00:32Z

KN6DWI: Started "Activate and Connect" section

File:Wireguard tunnel connected.png

2026-05-29T18:31:28Z

KN6DWI: A screenshot of the 44Net Connect page for a single device WireGuard tunnel, showing that the device is connected. The "Endpoint" field is blacked out and overwritten with "Your IP Here."

== Summary ==
A screenshot of the 44Net Connect page for a single device WireGuard tunnel, showing that the device is connected. The "Endpoint" field is blacked out and overwritten with "Your IP Here."

44Net Connect/Quick Start/Raspberry Pi

2026-05-29T17:42:56Z

KN6DWI: Added example picture for WireGuard tunnel config being copied from 44Net Connect

File:Wireguard tunnel config.png

2026-05-29T17:38:01Z

KN6DWI: A screenshot of a WireGuard tunnel config from the 44Net Connect website.

== Summary ==
A screenshot of a WireGuard tunnel config from the 44Net Connect website.

44Net Connect/Quick Start/Raspberry Pi

2026-05-29T17:29:23Z

KN6DWI: Fixed typo in code tag

44Net Connect/Quick Start/Raspberry Pi

2026-05-29T17:28:30Z

KN6DWI: Filled out section on configuring WireGuard client

44Net Connect/Quick Start/Raspberry Pi

2026-05-29T17:14:10Z

KN6DWI: Copied categories from 44Net Connect/Quick Start

44Net Connect/Quick Start/Raspberry Pi

2026-05-29T17:12:12Z

KN6DWI: Copied "Create Your Connect Tunnel" section from 44Net Connect/Quick Start page

44Net Connect/Quick Start/Raspberry Pi

2026-05-28T23:55:12Z

KN6DWI: Created sections "Create your Connect tunnel" and "Configure your WireGuard client"

44Net Connect/Quick Start/Raspberry Pi

2026-05-28T23:51:12Z

KN6DWI: Created page and Install Dependencies section

44Net Connect/Quick Start

2026-05-28T23:04:48Z

KN6DWI: Mention that device-specific tutorials are linked on the Supported Platforms page

<div class="toclimit-3">
__TOC__
</div>
{{DISPLAYTITLE:44Net Connect Quick Start}}

Use this guide to quickly set up your first 44Net Connect tunnel and get your device participating on the Internet as a native 44Net host.

=== What you need ===

* A 44Net Portal account
* A verified amateur radio callsign
* A device capable of running WireGuard
* Some sort of Internet access

If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted|44Net: Get Started]] for instructions. For a partial list of supported devices and device-specific tutorials, see [[44Net Connect/Supported Platforms|Supported Platforms]].

== Create your Connect tunnel ==

{{Step|
=== Step 1: Sign in to 44Net Connect ===
{{StepImage|file=Click to Log In.png}}
{{StepText|
* Visit [https://connect.44net.cloud The 44Net Connect dashboard].
* Click the “Log In to Get Started” button.
* Sign in with your 44Net Portal account credentials.

}}
}}

{{Step|
=== Step 2: Create your first tunnel ===
{{StepImage|file=Create Tunnel.png}}
{{StepText|
* On the dashboard page, click the “Create Tunnel” button.
}}
}}

{{Step|
=== Step 3: Choose region and node ===
{{StepImage|file=Choose Region and Node.png}}
{{StepText|
* In the list of regions, click the region closest to you.
* Nodes available in that region will appear.
* Click a node to select it as your endpoint.

You can change endpoints later if needed.
}}
}}

{{Step|
=== Step 4: Name your tunnel ===
{{StepImage|file=Name Tunnel.png}}
{{StepText|
* Enter a name for your tunnel (e.g. “Home Laptop” or “Raspberry Pi”)
}}
}}

{{Step|
=== Step 5: Save your new tunnel ===
{{StepImage|file=Complete Tunnel Creation.png}}
{{StepText|
* Check or uncheck the option to receive tunnel details via email.
* Click the “Create Tunnel” button.
* Review the confirmation dialog and click “Save Changes” to proceed.
}}
}}

== Configure your WireGuard client ==

{{Step|
=== Step 6: Get your configuration ===
{{StepImage|file=Copy Configuration.png|width=260px}}
{{StepText|
* Scroll down to find your tunnel configuration.
* Click the “Copy to Clipboard” button to copy the configuration text.
}}
}}

{{Step|
=== Step 7: Create a new tunnel ===
{{StepImage|file=Paste Configuration.png|width=260px}}
{{StepText|
==== Windows or macOS: ====
* Open your WireGuard client.
* Click the “+ Add Tunnel“ button to add a new tunnel.
* Delete the default template text and paste in your configuration.
* Give your tunnel a name in the “Name” field.
* Click the “Save” button.

==== Linux ====
* Create a new file for your WireGuard configuration, e.g. <code>/etc/wireguard/wg0.conf</code>.
* Paste the configuration text into the file and save it.

==== Other platforms ====
* Use the configuration text with your platform’s WireGuard implementation. Refer to your platform’s documentation for details on how to set up a WireGuard tunnel.

}}
}}

== Activate and connect ==

{{Step|
=== Step 8: Activate your tunnel ===
{{StepImage|file=Activate.png|width=260px}}
{{StepText|
==== Windows or macOS: ====
* In your WireGuard client, select the tunnel you just created.
* Click the “Activate” button to start the tunnel.

==== Linux ====
* Run the command <code>wg-quick up wg0</code> (replace <code>wg0</code> with the name of your configuration file if different).

==== Other platforms ====
* Use your platform’s method for starting the WireGuard tunnel. Refer to your platform’s documentation for details.
}}
}}

{{Step|
=== Step 9: Confirm handshake ===
{{StepImage|file=Confirm.png|width=260px}}
{{StepText|
==== Windows or macOS: ====
* In your WireGuard client, look for the “Handshake” field in your tunnel status.
* If the handshake is successful, you should see a recent timestamp indicating the last successful handshake with the Connect endpoint.

==== Linux ====
* Run the command <code>wg</code> to check the status of your WireGuard interfaces.
* Look for the interface corresponding to your Connect tunnel and check the “latest handshake” timestamp.

==== Other platforms ====
* Use your platform’s method for checking WireGuard tunnel status and confirm that the handshake with the Connect endpoint is successful.

==== In the Connect dashboard ====
* Your tunnel status should show as “Active” with a green indicator.
}}
}}

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

Your device is now reachable on the Internet at its 44Net IP address.
[[Category:Tutorial]]
[[Category:How-To]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]
[[Category:Getting Started]]

44Net Connect/Supported Platforms

2026-05-28T23:01:00Z

KN6DWI: Added platform list section and link to 44Net Connect/Quick Start/Raspberry Pi

{{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]].
* Use [[44Net Connect/pfSense|44Net Connect on pfSense]] for a pfSense firewall or gateway.
* 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.

== Platform List ==
* [[44Net Connect/Quick Start/Raspberry Pi|Raspberry Pi]]

== 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:Explanation]]
[[Category:Participation Methods]]
[[Category:44Net Connect]]

Requesting a block

2026-05-28T17:18:21Z

KN6DWI: Minor punctuation fix

'''ARDC/44Net'''

You '''must''' request an assignment direct from the Portal.
First you must create your account at the [https://portal.ampr.org/ Portal].
Once you do, you must login. <br>

* '''You also must login every 3-6 months even if it's just to check in to keep your assignment active, you have been warned!'''

Once logged in, from the '''top''' home tab, you next select the [https://portal.ampr.org/networks.php Networks]tab on the
row below. You will see a listing of subnets.

In most cases you should then click on the 44.0.0.0/9 NO COUNTRY option (second from the top)

Next you need to select the subnet most appropriate to your use case:

* If you want to join the IPIP Tunnel Mesh, AKA AMPRNet, then select 44.63.0.0/16
* For standalone use / anything else, please select 44.61.0.0/16
* If you want a BGP announced assignment then please select 44.31.0.0/16

After you have clicked on the network of choice, scroll to the bottom of the subsequent page where you will see the message:

'''"If the address range you want is not within any of the subnets above, or the region you are located in is not listed above, you may request an allocation from the parent network by clicking here:"'''

Go ahead and click on the link to the right of this message, this will display a request form for you to complete:

* Choose the size of subnet you would like to request from the dropdown "Netmask requested". Don't be '''greedy'''. Please only request what you will realistically use within 6 to 12 months (you can always request a larger assignment if your project takes off and you find you need more IPs later on).

* In the "Description" field enter a short description of the network if it is assigned - generally your callsign is a good choice here, remember it will be public.

* Leave the "Type" field set to "User" unless you have been instructed to do otherwise.

* In the "Connection Details" section tick the appropriate option(s) for your request. Most folk can ignore the third option "Direct (BGP)" unless you understand what this represents (announcing the subnet direct on the internet).

* In the "Notes" field you an enter any information you feel is relevant to your request, any information you feel would make the coordinators job easier when evaluating your request.

Finally click the "Send" button and wait !

Please bear in mind that the people who process these requests are volunteers and as such your request may not get looked at immediately, please be patient. If you haven't had an initial contact within 3 or 4 weeks then feel free to email postmaster [at] ardc.net explaining the issue (or use the contact-us form on the Portal).

If you are planning on connecting to the IPIP TunnelMesh, AKA AMPRNet, your next step is [https://wiki.ampr.org/wiki/Registering_Your_Gateway Here] to register your Gateway.

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