44Net Connect/Quick Start/Fedora - Revision history

KN6DWI: Updated automatic start instructions to use automatically generated systemd unit

2026-08-20T17:42:58Z

Updated automatic start instructions to use automatically generated systemd unit

@@ Line 50: / Line 50: @@
 == 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.
+* On Linux distributions that use <code>systemd</code>, using the <code>systemd</code> unit automatically generated by <code>wg-quick</code> is the recommended way to automatically start the tunnel. These are automatically created for any config file in <code>/etc/wireguard</code>.
-* Create a unit file in <code>/etc/systemd/system/</code>, for example <code>/etc/systemd/system/44net-tunnel.service</code>.
+* The automatically created unit is called <code>wg-quick@<config file name>.service</code>, so a file <code>/etc/wireguard/wg0.conf</code> would make <code>wg-quick@wg0.service</code>.
-* Paste the following into the file.
+* Enable and start the service by running <code>sudo systemctl enable --now wg-quick@<config file></code>, where <code><config file></code> is replaced with the name of your config file without the extension.
- <nowiki>
+* Verify that the service has started by running <code>systemctl status wg-quick@<config file></code> and checking that it says enabled and active, the same way we previously checked that systemd-resolved was working.
 [[Category:Tutorial]]

KN6DWI: Pasted instructions from Debian-based distributions page and removed irrelevant parts referring to systemd-resolved installation

2026-06-30T16:46:41Z

Pasted instructions from Debian-based distributions page and removed irrelevant parts referring to systemd-resolved installation

← Older revision		Revision as of 16:46, 30 June 2026
Line 22:		Line 22:
	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.

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


			=== 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: Wrote install dependencies section

2026-06-29T18:58:38Z

Wrote install dependencies section

← Older revision		Revision as of 18:58, 29 June 2026
Line 8:		Line 8:

	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 ==
			=== Step 1: Ensure your OS is up to date ===
			Update your system packages using either your GUI tool of choice, or by opening
			a terminal and running <code>sudo dnf update && sudo dnf upgrade</code>.

			=== Step 2: Install wireguard ===
			Run <code>sudo dnf install wireguard-tools</code>.

			=== Step 3: Verify that systemd-resolved is enabled ===
			<code>systemd-resolved</code> comes installed by default on Fedora. Ensure that it's running by executing <code>systemctl status systemd-resolved</code> in your terminal. If the unit is running without issues, there will be a green 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 Fedora machine 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.

KN6DWI: Created page and what you need section

2026-06-29T18:52:50Z

Created page and what you need section

New page

=== What you need ===

* A 44Net Portal account
* A verified amateur radio callsign
* A configuration file from 44Net Connect
* A device running Fedora Linux
* 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 obtained a WireGuard tunnel configuration file from 44Net Connect, get one using the [[44Net_Connect/Quick_Start|the 44Net Connect quick start guide]]