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

44Net Connect/Routed Subnet/Raspberry Pi

KN6DWI — Tue, 30 Jun 2026 23:09:10 GMT

Instructed user to check for kea failing to bind to interface when troubleshooting

← Older revision		Revision as of 23:09, 30 June 2026
Line 236:		Line 236:
	Forgetting to delete the default DHCP reservation examples will cause errors, because those are not in your subnet.		Forgetting to delete the default DHCP reservation examples will cause errors, because those are not in your subnet.

	If the DHCP server has started properly, check your <code>kea</code> configuration in <code>/etc/kea/kea-dhcp4.conf</code> and ensure that your interface, router IP, and IP ranges are set properly.		If the DHCP server has started properly, check your <code>kea</code> configuration in <code>/etc/kea/kea-dhcp4.conf</code> and ensure that your interface, router IP, and IP ranges are set properly. Check the logs in <code>systemctl status kea-dhcp4-server</code> for warnings that <code>kea</code> failed to bind to an interface.

	=== Clients cannot find route to hosts ===		=== Clients cannot find route to hosts ===

44Net Connect/Routed Subnet/Debian based distributions

KN6DWI — Tue, 30 Jun 2026 23:08:33 GMT

Pasted in troubleshooting section

← Older revision		Revision as of 23:08, 30 June 2026
(One intermediate revision by the same user not shown)
Line 172:		Line 172:
	// The rest of this config is omitted for brevity.		// The rest of this config is omitted for brevity.
	}</nowiki>		}</nowiki>

			== Setting up Routing ==
			=== Enable IP Forwarding ===
			To allow packets to be forwarded between different network interfaces on your Pi, we must enable IP forwarding in the kernel. Do this by adding the line <code>net.ipv4.ip_forward=1</code> to one of the drop-in files in <code>/etc/sysctl.d/</code>, or create one and add this line. It's customary to prefix drop-in file names with a number indicating their priority.
			Editing or creating the drop-in file will require superuser privileges. For example:

			<code>sudo nano /etc/sysctl.d/98-ipforward.conf</code>

			Next, reload your system configuration from config files by running <code>sudo sysctl --system</code>. Verify that IP forwarding has been successfully enabled
			by running <code>sysctl net.ipv4.ip_forward</code>, which should print <code>net.ipv4.ip_forward = 1</code>. If the number is 0 instead of 1, IP forwarding has not been properly enabled, and you should check your drop-in file for typos.

			=== Add the routing rule ===
			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.

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

			<code>ip route get 1.1.1.1 from <address> iif <subnet interface></code>

			<code><address></code> should be replaced by an address in your subnet, and <code><subnet interface></code> with the interface your routed subnet clients are connected to. This command will attempt to find the route to 1.1.1.1 (Cloudflare's DNS server, an arbitrary test IP) from an IP in the routed subnet. The output should look like this:

			<code>1.1.1.1 from <address> dev wg0 table 51820</code>

			If the output indicates that there is no route to host, or that your route does not proceed via the WireGuard interface, you may have an issue with your routing configuration.

			This routing rule will not persist between reboots. To make it persist, we can add it to the <code>systemd</code> unit created for the tunnel. After the existing <code>ExecStart</code> line, add another that executes the rule we just added. Immediately after that one, before the existing <code>ExecStop</code> line, add an
			<code>ExecStop</code> line that deletes the rule. This is done by running <code>ip rule del</code> rather than <code>ip rule add</code>. Your unit should look something like this:

			<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
			ExecStart=ip rule add from 44.27.45.129/29 lookup 51820
			ExecStop=ip rule del from 44.27.45.129/29 lookup 51820
			ExecStop=wg-quick down /etc/wireguard/wg0.conf

			[Install]
			WantedBy=multi-user.target</nowiki>

			== Troubleshooting ==
			=== Devices connected to the Pi are not receiving DHCP addresses ===
			Verify that the Kea DHCP server is running:

			<code>systemctl status kea-dhcp4-server</code>

			If it's not running, read its logs on the status screen to see if there were any errors in the configuration file.
			Forgetting to delete the default DHCP reservation examples will cause errors, because those are not in your subnet.

			If the DHCP server has started properly, check your <code>kea</code> configuration in <code>/etc/kea/kea-dhcp4.conf</code> and ensure that your interface, router IP, and IP ranges are set properly. Check the logs in <code>systemctl status kea-dhcp4-server</code> for warnings that <code>kea</code> failed to bind to an interface.

			=== Clients cannot find route to hosts ===
			Run <code>ip rule show</code> and ensure that:
			# The rule directing your routed subnet to the 51820 table exists
			# That rule's priority is a lower number (and thus higher priority) than any other rules that would override it, such as the default rule <code>from all lookup main</code>

			Next, inspect the table using <code>ip route show table 51820</code> and ensure that its default route is through the WireGuard interface.

44Net Connect/Routed Subnet/Raspberry Pi

KN6DWI — Tue, 30 Jun 2026 23:01:33 GMT

Added missing space

← Older revision		Revision as of 23:01, 30 June 2026
Line 184:		Line 184:
	=== Enable IP Forwarding ===		=== Enable IP Forwarding ===
	To allow packets to be forwarded between different network interfaces on your Pi, we must enable IP forwarding in the kernel. Do this by adding the line <code>net.ipv4.ip_forward=1</code> to one of the drop-in files in <code>/etc/sysctl.d/</code>. The file <code>98-rpi.conf</code> exists by default, so		To allow packets to be forwarded between different network interfaces on your Pi, we must enable IP forwarding in the kernel. Do this by adding the line <code>net.ipv4.ip_forward=1</code> to one of the drop-in files in <code>/etc/sysctl.d/</code>. The file <code>98-rpi.conf</code> exists by default, so
	add the line to ~~thatfile~~ using your editor of choice. It will require superuser privileges. For example:		add the line to that file using your editor of choice. It will require superuser privileges. For example:

	<code>sudo nano /etc/sysctl.d/98-rpi.conf</code>		<code>sudo nano /etc/sysctl.d/98-rpi.conf</code>

44Net Connect/Routed Subnet/Debian based distributions

KN6DWI — Tue, 30 Jun 2026 18:47:56 GMT

Pasted in section on configuring DHCP

← Older revision		Revision as of 18:47, 30 June 2026
(One intermediate revision by the same user not shown)
Line 51:		Line 51:

	<code>sudo nmcli con up <name of new connection></code>		<code>sudo nmcli con up <name of new connection></code>

			== Optional: Setting Up A Wireless Access Point ==

			If you have wireless only clients, or wish to utilize an existing WiFi interface in lieu of an additional ethernet interface, you can configure the interface as an access point.

			After your subnet is approved, you must attach it to your tunnel. Go to your Tunnels tab on 44Net Connect, and click Edit on the tunnel for your routing device. Go to the "Route additional Networks Through This Tunnel" section, and check the box for the subnet you want to use for this tunnel.

			=== Step 1: Set your wireless regulatory domain ===
			Different countries have different rules about which frequencies and bandwidths devices are allowed to use for WiFi.
			Setting the regulatory domain ensures that your device will use the right ones, making it work best with nearby devices and ensuring regulatory compliance.

			Your regulatory domain may have already been set during OS installation. Run
			<code>sudo iw reg get</code> to check whether it's been set. Look at the country set under <code>global</code>. If it says <code>unset</code>, you have not set the regulatory domain.

			If your regulatory domain has not been set, set it with <code>sudo iw reg set <country code></code> where the country code is your [https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 two letter ISO country code].

			=== Step 2: Configure WiFi settings for your nmcli connection ===
			Set the access point security and password. First, we set the <code>wifi-sec.key-mgmt</code> parameter to <code>wpa-psk</code> to disable the older insecure WEP encryption method. At this point, you will also need to set a password.

			<code>sudo nmcli con modify <connection name> wifi-sec.key-mgmt wpa-psk</code>

			<code>sudo nmcli con modify <connection name> wifi-sec.psk <password> </code>

			For security, leave only WPA2 enabled. By default, the older WPA protocol is enabled for compatibility, but it only supports the less secure TKIP encryption algorithm. Disable it by setting <code>wifi-sec.proto</code> to <code>rsn</code>.

			<code>sudo nmcli con modify <connection name> wifi-sec.proto rsn</code>

			Even after disabling the older WPA protocol, WPA2 supports TKIP for compatibility. As an additional security measure, enable only the CCMP encryption algorithm, disabling TKIP.

			<code>sudo nmcli con modify <connection name> wifi-sec.pairwise ccmp</code>

			Finally, set the connection to access point mode and configure it to use your subnet assignment.

			<code>sudo nmcli con modify <connection name> 802-11-wireless.mode ap 802-11-wireless.band <band> ipv4.method manual ipv4.addr <subnet in CIDR notation></code>

			For the <code>802-11-wireless.band</code> setting, choose either <code>bg</code> for 2.4 GHz or <code>a</code> for 5 GHz.

			Now we need to disable the current <code>nmcli</code> connection and enable our new one. Current connections can be viewed by running <code>nmcli connection</code>. If your device is currently connected to a WiFi network, you'll see something like <code>netplan-wlan0-<name of your wifi network></code>. Disable that connection by running the following command:

			<code>sudo nmcli conn down netplan-wlan0-<name of your wifi network></code>

			Next, enable your new connection by running <code>sudo nmcli conn up <name of connection></code>

			== Setting up DHCP ==
			[https://www.isc.org/kea/ Kea] is the recommended DHCP server for setting up a routed subnet. <code>dhcpd</code> is deprecated as of 2022.

			Install <code>kea</code> by running

			<code>sudo apt install kea</code>.

			After installing, configure its settings by editing <code>/etc/kea/kea-dhcp4.conf</code>. This file uses an extended JSON syntax that supports shell style comments using <code>#</code>, C style single line comments with <code>//</code>, and C style multi-line comments with <code>/* */</code>.

			=== Configure Interface ===
			Inside the <code>Dhcp4</code> struct, under <code>interfaces-config</code>, add the interface you want your DHCP server to operate on to the <code>interfaces</code> list. For example, in a setup using 2 ethernet interfaces, you might have <code>eth0</code> connected to your LAN and <code>eth1</code> connected to your client devices. In this case, you would use <code>eth1</code>. If you're using the built-in wireless card to broadcast an access point, use <code>wlan0</code>.

			<nowiki>
			"Dhcp4": {
			"interfaces-config": {
			"interfaces": [ "eth1" ]
			}
			}
			</nowiki>

			=== Configure DNS ===
			Inside the <code>Dhcp4</code> struct, under <code>option-data</code> set at least one DNS server. Cloudflare's DNS servers are <code>1.1.1.1</code> and <code>1.0.0.1</code>. Google's DNS servers are <code>8.8.8.8</code> and <code>8.8.4.4</code>.

			<nowiki>
			"Dhcp4": {
			"option-data": [
			{
			"name": "domain-name-servers",
			"data": "1.1.1.1, 1.0.0.1, 8.8.8.8, 8.8.4.4"
			},
			],
			}
			</nowiki>

			=== Configure your subnet ===
			<code>subnet4</code> is a list (denoted with brackets) of structures (denoted with curly brackets) where each structure is one subnet. Inside each subnet structure, set the client IP range(s) in <code>pools</code>, and define at least one router in the <code>option-data</code> field. Comment out or delete the example DHCP reservations in the <code>reservations</code> field, since they're for the wrong subnet.

			<nowiki>
			"subnet4": [
			// Put your subnet here in CIDR notation.
			"subnet": "44.27.45.128/29",

			// Define the range of client IP addresses here.
			"pools": [ { "pool": "44.27.45.129 - 44.27.45.133" } ],

			// These options are subnet specific. You must configure at least one router.
			"option-data": [
			{
			"name": "routers",
			"data": "44.27.45.129"
			}
			],
			"reservations": [
			// Comment out or delete the examples in this list, since they are for the wrong subnet.
			]
			]
			</nowiki>

			=== Ethernet Hot Plugging Workaround ===
			At present, <code>kea</code> does not support hot plugging interfaces. This means that ethernet devices must have at least one client at the time the DHCP server starts, otherwise it will not properly bind to the interface. If you plan on hot plugging ethernet devices on your Pi, this can be worked around by configuring <code>service-sockets-max-retries</code> to an extremely large number such as 9223372036854775807, the upper limit of a signed 64-bit integer. You may also wish to increase <code>service-sockets-retry-wait-time</code>, which specifies the retry time in milliseconds, though the default time of 5000 ms is typically fine. These options should go in the <code>interfaces-config</code> section at the top of your <code>Dhcp4</code> section in <code>/etc/kea/kea-dhcp4.conf</code>. Here is an example:

			<nowiki>
			"Dhcp4": {
			// Add names of your network interfaces to listen on.
			"interfaces-config": {
			// See section 8.2.4 for more details. You probably want to add just
			// interface name (e.g. "eth0" or specific IPv4 address on that
			// interface name (e.g. "eth0/192.0.2.1").
			"interfaces": ["eth1" ],

			// max retries is set to int64 max as a workaround for kea not supporting
			// hot plugging of interfaces.
			"service-sockets-max-retries": 9223372036854775807,
			"service-sockets-retry-wait-time": 2000
			},

			// The rest of this config is omitted for brevity.
			}</nowiki>

44Net Connect/Routed Subnet/Raspberry Pi

KN6DWI — Tue, 30 Jun 2026 18:29:02 GMT

Grammatical fix

← Older revision		Revision as of 18:29, 30 June 2026
Line 59:		Line 59:
	== Optional: Setting Up A Wireless Access Point ==		== Optional: Setting Up A Wireless Access Point ==

	~~However, if~~ you have wireless only clients or wish not to purchase additional hardware, the Raspberry Pi's WiFi interface can be configured as an access point.		If you have wireless only clients or wish not to purchase additional hardware, the Raspberry Pi's WiFi interface can be configured as an access point.

	After your subnet is approved, you must attach it to your tunnel. Go to your Tunnels tab on 44Net Connect, and click Edit on the tunnel for your routing device. Go to the "Route additional Networks Through This Tunnel" section, and check the box for the subnet you want to use for this tunnel.		After your subnet is approved, you must attach it to your tunnel. Go to your Tunnels tab on 44Net Connect, and click Edit on the tunnel for your routing device. Go to the "Route additional Networks Through This Tunnel" section, and check the box for the subnet you want to use for this tunnel.

44Net Connect/Routed Subnet/Debian based distributions

KN6DWI — Tue, 30 Jun 2026 18:28:04 GMT

Removed extra new line

← Older revision		Revision as of 18:28, 30 June 2026
Line 23:		Line 23:
	== Setting Up The Network Interface ==		== Setting Up The Network Interface ==
	The recommended way to set up the router for your subnet is with two ethernet interfaces. The second can be provided by a USB ethernet adapter if necessary. This section has the steps that are required regardless of whether you're using ethernet or WiFi. If you're using WiFi, you'll also need the steps in the following section. Otherwise, you can skip them.		The recommended way to set up the router for your subnet is with two ethernet interfaces. The second can be provided by a USB ethernet adapter if necessary. This section has the steps that are required regardless of whether you're using ethernet or WiFi. If you're using WiFi, you'll also need the steps in the following section. Otherwise, you can skip them.


	=== Step 1: Create a new connection in nmcli ===		=== Step 1: Create a new connection in nmcli ===

44Net Connect/Routed Subnet/Debian based distributions

KN6DWI — Tue, 30 Jun 2026 18:27:39 GMT

Copied in prerequisite section through network interface setup

New page

== Prerequisites ==
Set up a [[44Net_Connect/Quick_Start/Debian_based_distributions | single-device tunnel to your machine]].
Note the IP and name of your WireGuard interface. The name of your WireGuard interface is the same as the name
of your config file. For example, if your config file is <code>/etc/wireguard/wg0.conf</code>, then your
interface name is <code>wg0</code>. The IP of your WireGuard interface can be obtained from running <code>ifconfig <interface></code> and finding the IP listed under the interface in the <code>inet</code> field.

Below is some example output of <code>ifconfig wg0</code>.

<nowiki>
wg0: flags=209<UP,POINTOPOINT,RUNNING,NOARP> mtu 1380
inet 44.27.133.190 netmask 255.255.255.255 destination 44.27.133.190
inet6 fe80::f728:a0b0:3af5:b5c6 prefixlen 128 scopeid 0x20<link>
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 17331 bytes 5865364 (5.5 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 13389 bytes 2146828 (2.0 MiB)
TX errors 0 dropped 1 overruns 0 carrier 0 collisions 0</nowiki>

== Request a Subnet ==
Go to the [https://connect.44net.cloud/networks Network tab] of 44Net Connect, and request a network. Requests up to a /28 (16 IPs) are automatically approved. It's recommended to request at least a /29 (8 IPs), since at least 2 of your IPs must be set aside for network and broadcast addresses. That way, you have at least 6 usable addresses for your hosts.

== Setting Up The Network Interface ==
The recommended way to set up the router for your subnet is with two ethernet interfaces. The second can be provided by a USB ethernet adapter if necessary. This section has the steps that are required regardless of whether you're using ethernet or WiFi. If you're using WiFi, you'll also need the steps in the following section. Otherwise, you can skip them.

=== Step 1: Create a new connection in nmcli ===
<code>nmcli</code> is the CLI interface for NetworkManager, which is the high level network configuration tool included in most Debian-based distributions by default. These configuration steps can be completed using the NetworkManager GUI, but many people operate a "headless" machine (without a screen or keyboard) and use SSH to remotely configure it. Thus, this tutorial uses a CLI tool to accommodate that use case.
An <code>nmcli</code> "connection" is an abstraction representing a network configuration attached to a device. Create a new connection by running

<code>sudo nmcli con add conn-name <name> ifname <interface name> type <type></code>.

You can name the connection whatever you like, but it's recommended to name it something descriptive. For example, if you're configuring a 44net routed subnet for <code>eth1</code>, you might name it <code>44net-eth1</code>. The interface name is the name of the interface you're using, as described by <code>ifconfig</code>. The type is either <code>wifi</code> or <code>ethernet</code>. For a WiFi interface, you must also specify the BSSID (network name) by adding the parameter <code>ssid <BSSID></code> at the end.

=== Step 2: Configure the IP ===
Set the IPv4 method to manual using the following command:

<code>sudo nmcli con modify <name> ipv4.method manual</code>

Next, set the IP range for this interface.

<code>sudo nmcli con modify <name> ipv4.address <subnet></code>

Your subnet should be specified in CIDR notation. At this point, if you're configuring an ethernet interface, you're ready to start it up. If you're configuring a WiFi interface, don't start your interface yet, and move on to the next section for additional configuration.

=== Step 3: Starting the Interface ===
First, disable the existing connection, which is likely named <code>netplan-<interface></code>. If you're using <code>eth1</code> for your 44net clients, it may look like <code>netplan-eth1</code>. If you are configuring your Debian machine over SSH, be careful not to deactivate the connection over which your SSH is traveling.

<code>sudo nmcli con down <name of existing connection></code>

After deactivating the regular connection, activate your new connection. If this succeeds, you're good to go.

<code>sudo nmcli con up <name of new connection></code>

44Net Connect/Routed Subnet

KN6DWI — Tue, 30 Jun 2026 17:51:38 GMT

Added link to Debian-based distros page

← Older revision		Revision as of 17:51, 30 June 2026
Line 11:		Line 11:
	== Tutorials ==		== Tutorials ==
	* [[44Net_Connect/Routed_Subnet/Raspberry_Pi \| Raspberry Pi]]		* [[44Net_Connect/Routed_Subnet/Raspberry_Pi \| Raspberry Pi]]
			* [[44Net_Connect/Routed_Subnet/Debian_based_distributions \| Debian-based distributions]]

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

44Net Connect/Quick Start/Fedora

KN6DWI — Tue, 30 Jun 2026 16:46:41 GMT

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
(One intermediate revision by the same user not shown)
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.

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

44Net Connect/Quick Start/Fedora

KN6DWI — Mon, 29 Jun 2026 18:52:50 GMT

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

44Net Connect/Single Device Tunnel

KN6DWI — Mon, 29 Jun 2026 18:50:13 GMT

Added link to Fedora quick start page

← Older revision		Revision as of 18:50, 29 June 2026
Line 19:		Line 19:
	* [[44Net_Connect/Quick_Start/Debian_based_distributions\|44Net Connect Quick Start: Debian-based distributions]]		* [[44Net_Connect/Quick_Start/Debian_based_distributions\|44Net Connect Quick Start: Debian-based distributions]]
	* [[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]]

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

44Net Connect/Routed Subnet/Raspberry Pi

KN6DWI — Fri, 26 Jun 2026 20:12:37 GMT

Fixed heading formatting issue

Show changes

Talk:44Net Connect/Routed Subnet/Raspberry Pi

KN6DWI — Fri, 26 Jun 2026 17:06:28 GMT

Mentioned open kea GitLab issue for hot plugging network interfaces

New page

At present, the <code>kea</code> DHCP server does not support "hot plugging" network interfaces. This is a problem if you want to start <code>kea</code> operating on an ethernet interface before clients are plugged into it. There is [https://gitlab.isc.org/isc-projects/kea/-/work_items?sort=created_date&state=all&search=hot+plug+&first_page_size=20&show=eyJpaWQiOiIzMTg4IiwiZnVsbF9wYXRoIjoiaXNjLXByb2plY3RzL2tlYSIsImlkIjoyMzU2MH0%3D an open GitLab issue] about this.

44Net Connect/Routed Subnet/Raspberry Pi

KN6DWI — Wed, 24 Jun 2026 22:17:26 GMT

Added troubleshooting steps for when clients cannot find route to hosts

Show changes