44Net Wiki - Recent changes [en]

44Net Connect/Quick Start/OPNsense

KN6DWI — Wed, 08 Jul 2026 17:37:24 GMT

Added Activate Instance section and Troubleshooting section

← Older revision		Revision as of 17:37, 8 July 2026
Line 36:		Line 36:

	Finally, save your peer, go back to the configuration for your instance, and add the peer you just created.		Finally, save your peer, go back to the configuration for your instance, and add the peer you just created.

			=== Activate Instance ===
			On the instances page, ensure your instance is enabled, check the box to enable WireGuard, then apply your changes.

			[[File:opnsense_enable_instance.png\|A screenshot of the OPNsense WireGuard instances page, with the "Enable WireGuard" checkbox and enable instance checkbox highlighted with red rectangles.]]

			Go to <code>WireGuard > Status</code> and ensure that both your instance and your peer display green checkmarks. If they do, you're good to go!

			[[File:opnsense_wireguard_status.png\|A screenshot of the OPNsense WireGuard status page. Both the interface and the peer show green checkmarks in the status column.]]

			== Troubleshooting ==
			=== Peer status displays a question mark ===
			Minor misconfiguration of the peer can cause a question mark in the status page and a nonfunctional tunnel. Double check that the peer's configuration matches the WireGuard config file, and make sure your peer is configured with a /32. 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, but a tunnel will always receive a /32.

File:Opnsense wireguard status.png

KN6DWI — Wed, 08 Jul 2026 17:33:32 GMT

KN6DWI uploaded File:Opnsense wireguard status.png A screenshot of the OPNsense WireGuard status page. Both the interface and the peer show green checkmarks in the status column.

New page

== Summary ==
A screenshot of the OPNsense WireGuard status page. Both the interface and the peer show green checkmarks in the status column.

File:Opnsense enable instance.png

KN6DWI — Wed, 08 Jul 2026 17:26:20 GMT

KN6DWI uploaded File:Opnsense enable instance.png A screenshot of the OPNsense WireGuard instances page, with the "Enable WireGuard" checkbox and enable instance checkbox highlighted with red rectangles.

New page

== Summary ==
A screenshot of the OPNsense WireGuard instances page, with the "Enable WireGuard" checkbox and enable instance checkbox highlighted with red rectangles.

44Net Connect/Routed Subnet/Raspberry Pi

KN6DWI — Tue, 07 Jul 2026 23:31:37 GMT

Added recommendations about priority and using ip rule over ip route

← Older revision		Revision as of 23:31, 7 July 2026
Line 194:		Line 194:
	Next, we need to add a routing rule to allow the clients on the routed subnet to exit via the WireGuard tunnel. The setup steps for creating the tunnel should have created the routing table <code>51820</code> where the default route is via the WireGuard interface, whatever you've named it. Verify that it exists by running the command <code>ip route show table 51820</code>. It should have a single line that says something like <code>default dev wg0 scope link</code>. In this case, <code>wg0</code> is the example WireGuard interface name. Yours may be different.		Next, we need to add a routing rule to allow the clients on the routed subnet to exit via the WireGuard tunnel. The setup steps for creating the tunnel should have created the routing table <code>51820</code> where the default route is via the WireGuard interface, whatever you've named it. Verify that it exists by running the command <code>ip route show table 51820</code>. It should have a single line that says something like <code>default dev wg0 scope link</code>. In this case, <code>wg0</code> is the example WireGuard interface name. Yours may be different.

	Run the command <code>sudo ip rule add from <subnet> table 51820</code>. Replace <code><subnet></code> with your routed subnet in CIDR notation.		Run the command <code>sudo ip rule add from <subnet> table 51820</code>. Replace <code><subnet></code> with your routed subnet in CIDR notation. If you have other rules with desired priority order, set your priority in the above command accordingly. Though it's possible to do the same thing as this rule using <code>ip route</code>, it's much more difficult and is not recommended.

	Verify that your routing is working correctly by running the following command:		Verify that your routing is working correctly by running the following command:

44Net Connect/Quick Start/OPNsense

KN6DWI — Tue, 07 Jul 2026 22:53:36 GMT

Added pictures for populating OPNsense peer page

← Older revision		Revision as of 22:53, 7 July 2026
Line 28:		Line 28:
	Go to <code>VPN > WireGuard > Peers</code> in your OPNsense Web UI, and click the orange <code>+</code> button in the bottom right to create a new peer. Give it a name, and paste the <code>PublicKey</code> value from the <code>[Peer]</code> section of your config file into the peer's <code>Public key</code> field. If you configured a pre-shared key when creating your tunnel, enter it in		Go to <code>VPN > WireGuard > Peers</code> in your OPNsense Web UI, and click the orange <code>+</code> button in the bottom right to create a new peer. Give it a name, and paste the <code>PublicKey</code> value from the <code>[Peer]</code> section of your config file into the peer's <code>Public key</code> field. If you configured a pre-shared key when creating your tunnel, enter it in
	the <code>Pre-shared key</code> field. Also copy in <code>Allowed IPs</code>, <code>Endpoint address</code>, <code>Endpoint port</code>, and <code>Keepalive interval</code> from the <code>[Peer]</code> section of your config file.		the <code>Pre-shared key</code> field. Also copy in <code>Allowed IPs</code>, <code>Endpoint address</code>, <code>Endpoint port</code>, and <code>Keepalive interval</code> from the <code>[Peer]</code> section of your config file.

			[[File:opnsense_populate_peer_endpoint.png\|A side by side screenshot of the OPNsense peer configuration dialogue next to a WireGuard configuration file. Two red arrows indicate where to copy the endpoint IP and port from the config file to the OPNsense configuration dialogue.]]

			[[File:opnsense_populate_peer_keepalive_addresses.png\|A side by side screenshot of the OPNsense peer configuration dialogue next to a WireGuard configuration file. Red arrows indicate where to copy the public key, keepalive interval, and allowed IPs from the config file to the OPNsense configuration dialogue.]]

	In the <code>Instances</code> field, use the drop-down menu to select the instance you created earlier in this tutorial.		In the <code>Instances</code> field, use the drop-down menu to select the instance you created earlier in this tutorial.

	Finally, save your peer, go back to the configuration for your instance, and add the peer you just created.		Finally, save your peer, go back to the configuration for your instance, and add the peer you just created.

File:Opnsense populate peer keepalive addresses.png

KN6DWI — Tue, 07 Jul 2026 22:52:43 GMT

KN6DWI uploaded File:Opnsense populate peer keepalive addresses.png A side by side screenshot of the OPNsense peer configuration dialogue next to a WireGuard configuration file. Red arrows indicate where to copy the public key, keepalive interval, and allowed IPs from the config file to the OPNsense configuration dialogue.

New page

== Summary ==
A side by side screenshot of the OPNsense peer configuration dialogue next to a WireGuard configuration file. Red arrows indicate where to copy the public key, keepalive interval, and allowed IPs from the config file to the OPNsense configuration dialogue.

File:Opnsense populate peer endpoint.png

KN6DWI — Tue, 07 Jul 2026 22:29:23 GMT

KN6DWI uploaded File:Opnsense populate peer endpoint.png A side by side screenshot of the OPNsense peer configuration dialogue next to a WireGuard configuration file. Two red arrows indicate where to copy the endpoint IP and port from the config file to the OPNsense configuration dialogue.

New page

== Summary ==
A side by side screenshot of the OPNsense peer configuration dialogue next to a WireGuard configuration file. Two red arrows indicate where to copy the endpoint IP and port from the config file to the OPNsense configuration dialogue.

44Net Connect/Quick Start/OPNsense

KN6DWI — Tue, 07 Jul 2026 21:59:33 GMT

Added image for filling out instance

← Older revision		Revision as of 21:59, 7 July 2026
Line 22:		Line 22:
	=== Fill out instance ===		=== Fill out instance ===
	Go back to your OPNsense Web UI. Give your instance a name, and fill out the <code>Tunnel address</code> field with the addresses from the <code>[Interface]</code> section of the config. Check the <code>Disable routes</code> checkbox, then save your instance.		Go back to your OPNsense Web UI. Give your instance a name, and fill out the <code>Tunnel address</code> field with the addresses from the <code>[Interface]</code> section of the config. Check the <code>Disable routes</code> checkbox, then save your instance.

			[[File:opnsense_populate_instance.png\| A screenshot with a side by side view of a WireGuard config file and an OPNsense WireGuard instance configuration page. A red arrow indicates how to copy the tunnel addresses from the config file to the OPNsense configuration page. A red rectangle indicates that the user should check the "Disable Routes" box.]]

	=== Fill out peer ===		=== Fill out peer ===

File:Opnsense populate instance.png

KN6DWI — Tue, 07 Jul 2026 21:57:57 GMT

KN6DWI uploaded File:Opnsense populate instance.png A screenshot with a side by side view of a WireGuard config file and an OPNsense WireGuard instance configuration page. A red arrow indicates how to copy the tunnel addresses from the config file to the OPNsense configuration page. A red rectangle indicates that the user should check the "Disable Routes" box.

New page

== Summary ==
A screenshot with a side by side view of a WireGuard config file and an OPNsense WireGuard instance configuration page. A red arrow indicates how to copy the tunnel addresses from the config file to the OPNsense configuration page. A red rectangle indicates that the user should check the "Disable Routes" box.

44Net Connect/Quick Start/OPNsense

KN6DWI — Tue, 07 Jul 2026 18:45:53 GMT

Added caption to image

← Older revision		Revision as of 18:45, 7 July 2026
(One intermediate revision by the same user not shown)
Line 15:		Line 15:

	== Create a tunnel in 44Net Connect ==		== Create a tunnel in 44Net Connect ==
	Open your [https://connect.44net.cloud/tunnels tunnels page in 44Net Connect] and click <code>Request a Tunnel</code>. Select your preferred server. In the <code>Public Key</code> field, paste the public key generated in OPNsense, then <code>Create Tunnel</code>. Save the wg-quick WireGuard config for use in later steps.		Open your [https://connect.44net.cloud/tunnels tunnels page in 44Net Connect] and click <code>Request a Tunnel</code>. Select your preferred server. In the <code>Public Key</code> field, paste the public key generated in OPNsense, then <code>Create Tunnel</code>. Save the wg-quick WireGuard config for use in later steps.

			[[File:request_tunnel_44net_connect.png\|A screenshot of the 44Net Connect tunnel page header with the Request Tunnel button highlighted in a red box]]

	== Copy the tunnel details into OPNsense ==		== Copy the tunnel details into OPNsense ==

File:Request tunnel 44net connect.png

KN6DWI — Tue, 07 Jul 2026 18:44:47 GMT

KN6DWI uploaded File:Request tunnel 44net connect.png Screenshot of the 44Net Connect tunnel page header with the Request Tunnel button highlighted in a red box.

New page

== Summary ==
Screenshot of the 44Net Connect tunnel page header with the Request Tunnel button highlighted in a red box.

44Net Connect/Quick Start/OPNsense

KN6DWI — Tue, 07 Jul 2026 18:00:00 GMT

Added screenshot for keypair generation

← Older revision		Revision as of 18:00, 7 July 2026
Line 11:		Line 11:
	== Generate a keypair in OPNsense ==		== Generate a keypair in OPNsense ==
	Navigate to <code>VPN > WireGuard > Instances</code> in your OPNsense web GUI and create a new instance. Click the gear button to generate a public key/private key keypair.		Navigate to <code>VPN > WireGuard > Instances</code> in your OPNsense web GUI and create a new instance. Click the gear button to generate a public key/private key keypair.

			[[File:opnsense_keypair_generation.png\|500px\|A screenshot of the OPNsense edit instance dialogue, with the gear button next to the public key field circled in red.]]

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

File:Opnsense keypair generation.png

KN6DWI — Tue, 07 Jul 2026 17:50:55 GMT

KN6DWI uploaded File:Opnsense keypair generation.png A screenshot of the OPNsense Edit Instance dialogue with the button for generating a WireGuard keypair circled in red.

New page

== Summary ==
A screenshot of the OPNsense Edit Instance dialogue with the button for generating a WireGuard keypair circled in red.

44Net Connect/Quick Start/OPNsense

KN6DWI — Fri, 03 Jul 2026 00:50:42 GMT

Wrote section on copying tunnel details into OPNsense

@@ Line 9: / Line 9: @@
 Unlike the 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.
-== Create a WireGuard instance ==
+== Generate a keypair in OPNsense ==
 Navigate to <code>VPN > WireGuard > Instances</code> in your OPNsense web GUI and create a new instance. Click the gear button to generate a public key/private key keypair.

44Net Connect/Quick Start/OPNsense

KN6DWI — Thu, 02 Jul 2026 23:35:32 GMT

Created page and what you need section

New page

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

== Create a WireGuard instance ==
Navigate to <code>VPN > WireGuard > Instances</code> in your OPNsense web GUI and create a new instance. Click the gear button to generate a public key/private key keypair.

44Net Connect/Single Device Tunnel

KN6DWI — Thu, 02 Jul 2026 23:27:46 GMT

Added link to OPNsense quick start page

← Older revision		Revision as of 23:27, 2 July 2026
Line 20:		Line 20:
	* [[44Net_Connect/Quick_Start/Raspberry_Pi\|44Net Connect Quick Start: Raspberry Pi]]		* [[44Net_Connect/Quick_Start/Raspberry_Pi\|44Net Connect Quick Start: Raspberry Pi]]
	* [[44Net_Connect/Quick_Start/Fedora\|44Net Connect Quick Start: Fedora]]		* [[44Net_Connect/Quick_Start/Fedora\|44Net Connect Quick Start: Fedora]]
			* [[44Net_Connect/Quick_Start/OPNsense\|44Net Connect Quick Start: OPNsense]]

	[[Category:Topology]]		[[Category:Topology]]
	[[Category:Participation Methods]]		[[Category:Participation Methods]]