44Net Connect/Quick Start/Fedora

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 44Net: Get Started for instructions. If you haven't obtained a WireGuard tunnel configuration file from 44Net Connect, get one using the 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 sudo dnf update && sudo dnf upgrade.

Step 2: Install wireguard

Run sudo dnf install wireguard-tools.

Step 3: Verify that systemd-resolved is enabled

systemd-resolved comes installed by default on Fedora. Ensure that it's running by executing systemctl status systemd-resolved 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 systemctl enable systemd-resolved 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 systemctl start systemd-resolved 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 /etc/wireguard/, for example /etc/wireguard/wg0.conf.
• 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.

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 sudo chmod 600 /etc/wireguard/wg0.conf. (Replace wg0 with the name of your file.)

Activate and connect

Activate your tunnel

Run the command wg-quick up wg0 (replace wg0 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.

• The Endpoint 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 curl https://connect.44net.cloud/myip
• Use traceroute to inspect the path between you and some other device, such as traceroute 1.1.1.1. When the tunnel is working, the first hop will be through a 44Net gateway, so its IP will be in the 44.0.0.0/9 or 44.128.0.0/10 subnet.

Starting the Tunnel Automatically

• On Linux distributions that use systemd, creating a systemd unit is the recommended way to automatically start the tunnel.
• Create a unit file in /etc/systemd/system/, for example /etc/systemd/system/44net-tunnel.service.
• Paste the following into the file.

[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

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