44Net Connect/Quick Start/Raspberry Pi - Revision history

KN6DWI: Replace directly written text with transclusion of Debian-based distribution article

2026-06-03T22:13:57Z

Replace directly written text with transclusion of Debian-based distribution article

← Older revision		Revision as of 22:13, 3 June 2026
Line 14:		Line 14:
	If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted\|44Net: Get Started]] for instructions. If you haven't obtained a WireGuard tunnel configuration file from 44Net Connect, get one using the [[44Net_Connect/Quick_Start\|the 44Net Connect quick start guide]]		If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted\|44Net: Get Started]] for instructions. If you haven't obtained a WireGuard tunnel configuration file from 44Net Connect, get one using the [[44Net_Connect/Quick_Start\|the 44Net Connect quick start guide]]

	~~== Install Dependencies ==~~		{{:44Net_Connect/Quick_Start/Debian_based_distributions}}

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

	~~== Configure your WireGuard client ==~~
	* 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 computer 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]]~~

KN6DWI: Use more device agnostic language in WireGuard config section

2026-06-03T22:00:14Z

Use more device agnostic language in WireGuard config section

← Older revision		Revision as of 22:00, 3 June 2026
Line 29:		Line 29:

	== Configure your WireGuard client ==		== 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>.		* 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.		* 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.		* Paste the configuration text in from 44Net Connect, or if you prefer to use the file that was emailed to you, upload that one.
Line 38:		Line 38:

	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.)		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 and connect ==

KN6DWI: Use more device agnostic language

2026-06-03T21:59:24Z

Use more device agnostic language

← Older revision		Revision as of 21:59, 3 June 2026
Line 43:		Line 43:
	=== Activate your tunnel ===		=== 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).		* 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>.		* 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 computer after installing <code>systemd-resolved</code>.

	=== Confirm Connection in the Connect dashboard ===		=== Confirm Connection in the Connect dashboard ===

KN6DWI: Moved location of link to 44Net Connect quick start guide

2026-06-01T21:58:57Z

Moved location of link to 44Net Connect quick start guide

← Older revision		Revision as of 21:58, 1 June 2026
Line 8:		Line 8:
	* A 44Net Portal account		* A 44Net Portal account
	* A verified amateur radio callsign		* A verified amateur radio callsign
	* A configuration file from 44Net Connect ~~(obtain one using [[44Net_Connect/Quick_Start\|the 44Net Connect quick start guide]])~~		* A configuration file from 44Net Connect
	* A Raspberry Pi with a working Raspberry Pi OS installation		* A Raspberry Pi with a working Raspberry Pi OS installation
	* Some sort of Internet access		* 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.		If you haven't set up your Portal account or verified your callsign yet, see [[GetStarted\|44Net: Get Started]] for instructions. If you haven't obtained a WireGuard tunnel configuration file from 44Net Connect, get one using the [[44Net_Connect/Quick_Start\|the 44Net Connect quick start guide]]

	== Install Dependencies ==		== Install Dependencies ==

KN6DWI: Removed section on creating connect tunnel and replaced it with a link to the 44Net Connect quick start page

2026-06-01T21:57:29Z

Removed section on creating connect tunnel and replaced it with a link to the 44Net Connect quick start page

@@ Line 8: / Line 8: @@
 * A 44Net Portal account
 * A verified amateur radio callsign
 * A Raspberry Pi with a working Raspberry Pi OS installation
 * Some sort of Internet access
@@ Line 26: / Line 27: @@
 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.
 == Configure your WireGuard client ==

KN6DWI: Added section on starting automatically with systemd

2026-05-29T22:31:38Z

Added section on starting automatically with systemd

@@ Line 89: / Line 89: @@
 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.)
@@ Line 110: / Line 104: @@
 * 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.

KN6DWI: Added "Other Ways to Confirm Connection" section

2026-05-29T21:53:35Z

Added "Other Ways to Confirm Connection" section

← Older revision		Revision as of 21:53, 29 May 2026
Line 106:		Line 106:
	[[File:wireguard_tunnel_connected.png\|500px]]		[[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.		* 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.

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

2026-05-29T21:24:02Z

Added instruction to set chmod 600 permissions for WireGuard config file

← Older revision		Revision as of 21:24, 29 May 2026
Line 87:		Line 87:

	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.		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:Tutorial]]

KN6DWI: Started "Activate and Connect" section

2026-05-29T19:00:32Z

Started "Activate and Connect" section

← Older revision		Revision as of 19:00, 29 May 2026
Line 93:		Line 93:
	[[Category:44Net Connect]]		[[Category:44Net Connect]]
	[[Category:Getting Started]]		[[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.

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

2026-05-29T17:42:56Z

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

← Older revision		Revision as of 17:42, 29 May 2026
Line 80:		Line 80:

	== Configure your WireGuard client ==		== Configure your WireGuard client ==
	* ~~Create~~ a new file for your WireGuard configuration in <code>/etc/wireguard/</code>, for example <code>/etc/wireguard/wg0.conf</code>.		* 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.		* 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.		* 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.

	[[Category:Tutorial]]		[[Category:Tutorial]]