44Net Connect/Quick Start/PFsense - Revision history

KN6DWI: Wrote Enable WireGuard section

2026-07-09T19:21:32Z

Wrote Enable WireGuard section

← Older revision		Revision as of 19:21, 9 July 2026
Line 26:		Line 26:

	Fill in the Allowed IPs section at the bottom using the values from the config file, which by default is <code>0.0.0.0/0</code> and <code>::/0</code>. This configuration allows all addresses, and will let you pass all traffic through the tunnel. If you want only traffic to and from your 44Net IP to go through the tunnel, change your AllowedIPs to <code>44.0.0.0/9</code> and <code>44.128.0.0/10</code>.		Fill in the Allowed IPs section at the bottom using the values from the config file, which by default is <code>0.0.0.0/0</code> and <code>::/0</code>. This configuration allows all addresses, and will let you pass all traffic through the tunnel. If you want only traffic to and from your 44Net IP to go through the tunnel, change your AllowedIPs to <code>44.0.0.0/9</code> and <code>44.128.0.0/10</code>.

			== Enable WireGuard ==
			Go to <code>VPN > WireGuard > Settings</code> and check the <code>Enable WireGuard</code> box, then save your changes. If prompted with a banner at the top to save your WireGuard settings before applying, do so. Check the status of your tunnel by going to <code>Status > WireGuard</code>, clicking the arrow next to your tunnel to expand its section, and verifying that it's performed a handshake with the endpoint.

KN6DWI: Wrote section on adding peer

2026-07-09T19:18:44Z

Wrote section on adding peer

← Older revision		Revision as of 19:18, 9 July 2026
Line 23:		Line 23:

	== Add Peer ==		== Add Peer ==
			Click the <code>Add Peer</code> button. Uncheck the <code>Dynamic Endpoint</code> box, as this will allow us to fill in a static IP and port for the endpoint. Fill in the endpoint IP and port from the <code>[Peer]</code> section of the WireGuard config file. Also copy in MTU, Keep Alive interval, the peer's public key, and if applicable, the pre-shared key.

			Fill in the Allowed IPs section at the bottom using the values from the config file, which by default is <code>0.0.0.0/0</code> and <code>::/0</code>. This configuration allows all addresses, and will let you pass all traffic through the tunnel. If you want only traffic to and from your 44Net IP to go through the tunnel, change your AllowedIPs to <code>44.0.0.0/9</code> and <code>44.128.0.0/10</code>.

KN6DWI: Wrote section on filling in interface

2026-07-09T18:51:48Z

Wrote section on filling in interface

← Older revision		Revision as of 18:51, 9 July 2026
Line 17:		Line 17:
	In the <code>Public Key</code> field, paste the public key generated in PFsense, then click <code>Create Tunnel</code> to save. Retain the wg-quick WireGuard config for use in later steps.		In the <code>Public Key</code> field, paste the public key generated in PFsense, then click <code>Create Tunnel</code> to save. Retain the wg-quick WireGuard config for use in later steps.

	== ~~Create a~~ tunnel in 44Net Connect ==		== Fill in interface ==
			Copy the interface addresses from your config file into the Interface Addresses section in your PFsense WireGuard tunnel configuration. Adding the IPv6 address is optional but recommended. If you're doing so, click the <code>Add Address</code> button to add another IP address field. For all entries, use the drop-down menu to configure the subnet. For the IPv4 address it should be /32, and for the IPv6 address it should be /64. There are some places on 44Net Connect that are labeled in a confusing way, and could be interpreted as your tunnel being allocated a /24 for IPv4, but a tunnel will always receive a /32 for IPv4.

	== ~~Copy tunnel details into PFsense~~ ==		Click <code>Save Tunnel</code>. PFsense won't let you add peers until you save the tunnel. In the next step, we'll edit the tunnel to add a peer.

			== Add Peer ==

KN6DWI: Wrote section on generating keypair and creating tunnel

2026-07-09T18:01:23Z

Wrote section on generating keypair and creating tunnel

← Older revision		Revision as of 18:01, 9 July 2026
Line 12:		Line 12:
	WireGuard is not installed by default on PFsense, so we need to install it. Go to <code>System > Package Manager > Available Packages</code> and install WireGuard.		WireGuard is not installed by default on PFsense, so we need to install it. Go to <code>System > Package Manager > Available Packages</code> and install WireGuard.

	== Generate a keypair in PFsense ==		== Generate keypair and create tunnel ==
			After installing WireGuard, go to <code>VPN > WireGuard > Tunnels</code> and click the <code>Add Tunnel</code> button.
			Click the <code>Generate</code> button to generate a new keypair. Then, open your [https://connect.44net.cloud/tunnels tunnels page in 44Net Connect], request a new tunnel, and select your preferred server.
			In the <code>Public Key</code> field, paste the public key generated in PFsense, then click <code>Create Tunnel</code> to save. Retain the wg-quick WireGuard config for use in later steps.

	== Create a tunnel in 44Net Connect ==		== Create a tunnel in 44Net Connect ==

	== Copy tunnel details into PFsense ==		== Copy tunnel details into PFsense ==

KN6DWI: Created Install WireGuard section

2026-07-09T17:56:20Z

Created Install WireGuard section

← Older revision		Revision as of 17:56, 9 July 2026
Line 8:		Line 8:

	Unlike other Quick Start guides, we aren't starting with a configuration file from 44Net Connect. Instead, we will be creating one during the course of this tutorial.		Unlike other Quick Start guides, we aren't starting with a configuration file from 44Net Connect. Instead, we will be creating one during the course of this tutorial.

			== Install the WireGuard Package ==
			WireGuard is not installed by default on PFsense, so we need to install it. Go to <code>System > Package Manager > Available Packages</code> and install WireGuard.

	== Generate a keypair in PFsense ==		== Generate a keypair in PFsense ==

KN6DWI: Created page

2026-07-09T17:17:10Z

Created page

New page

=== What you need ===
* A 44Net Portal account
* A verified amateur radio callsign
* A machine running PFsense
* 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]]

Unlike other Quick Start guides, we aren't starting with a configuration file from 44Net Connect. Instead, we will be creating one during the course of this tutorial.

== Generate a keypair in PFsense ==

== Create a tunnel in 44Net Connect ==

== Copy tunnel details into PFsense ==