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

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

KN6DWI: Fixed typo in code tag

2026-05-29T17:29:23Z

Fixed typo in code tag

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

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

KN6DWI: Filled out section on configuring WireGuard client

2026-05-29T17:28:30Z

Filled out section on configuring WireGuard client

← Older revision		Revision as of 17:28, 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>.
			* 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.

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

KN6DWI: Copied categories from 44Net Connect/Quick Start

2026-05-29T17:14:10Z

Copied categories from 44Net Connect/Quick Start

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

	== Configure your WireGuard client ==		== Configure your WireGuard client ==

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

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

2026-05-29T17:12:12Z

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

← Older revision		Revision as of 17:12, 29 May 2026
Line 28:		Line 28:


	== Create your Connect tunnel ==		== 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 ==		== Configure your WireGuard client ==

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

2026-05-28T23:55:12Z

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

← Older revision		Revision as of 23:55, 28 May 2026
Line 26:		Line 26:
	The third line, beginning with "Active," should indicate that the unit is active (running).		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.		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 ==

			== Configure your WireGuard client ==