44Net Connect/Routed Subnet/Raspberry Pi - Revision history

KN6DWI: Created troubleshooting section on not receiving DHCP addresses

2026-06-19T00:15:23Z

Created troubleshooting section on not receiving DHCP addresses

← Older revision		Revision as of 00:15, 19 June 2026
Line 141:		Line 141:

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

KN6DWI: Wrote section on enabling IP forwarding

2026-06-19T00:09:37Z

Wrote section on enabling IP forwarding

← Older revision		Revision as of 00:09, 19 June 2026
Line 137:		Line 137:

	== Setting up Routing ==		== Setting up Routing ==
			=== Enable IP Forwarding ===
			Enable IP forwarding in the kernel by running <code>sudo sysctl -w net.ipv4.ip_forward=1</code>. Verify that this worked by running <code>sysctl net.ipv4.ip_forward</code> and it should read back <code>net.ipv4.ip_forward = 1</code>.

	== Troubleshooting ==		== Troubleshooting ==

KN6DWI: Described how to disable current WiFi connection and enable new one

2026-06-18T18:13:29Z

Described how to disable current WiFi connection and enable new one

← Older revision		Revision as of 18:13, 18 June 2026
Line 71:		Line 71:

	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.		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 Pi 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 ==		== Setting up DHCP ==

KN6DWI: Added missing sudo to iw command

2026-06-18T17:37:47Z

Added missing sudo to iw command

← Older revision		Revision as of 17:37, 18 June 2026
Line 39:		Line 39:
	If you didn't set the regulatory domain in the imager configuration, set it now by running		If you didn't set the regulatory domain in the imager configuration, set it now by running
	<code>sudo raspi-config</code> and going to <code>Localisation Options > WLAN Country</code>. Select your country, confirm, and exit. If you're not sure whether you set the		<code>sudo raspi-config</code> and going to <code>Localisation Options > WLAN Country</code>. Select your country, confirm, and exit. If you're not sure whether you set the
	wireless regulatory domain, run the command <code>iw reg get</code>. Look at the country		wireless regulatory domain, run the command <code>sudo iw reg get</code>. Look at the country
	set under <code>global</code>. If it says <code>unset</code>, you have not set the regulatory domain.		set under <code>global</code>. If it says <code>unset</code>, you have not set the regulatory domain.

KN6DWI: Wrote configure interface section

2026-06-17T23:06:09Z

Wrote configure interface section

← Older revision		Revision as of 23:06, 17 June 2026
Line 82:		Line 82:

	=== Configure Interface ===		=== 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 ===		=== Configure DNS ===

KN6DWI: Wrote sections on configuring DNS and configuring subnet

2026-06-17T22:45:36Z

Wrote sections on configuring DNS and configuring subnet

@@ Line 73: / Line 73: @@
 == Setting up DHCP ==
 == Setting up Routing ==
 == Troubleshooting ==

KN6DWI: Created section on requesting a subnet

2026-06-17T00:06:00Z

Created section on requesting a subnet

← Older revision		Revision as of 00:06, 17 June 2026
Line 21:		Line 21:
	TX packets 13389 bytes 2146828 (2.0 MiB)		TX packets 13389 bytes 2146828 (2.0 MiB)
	TX errors 0 dropped 1 overruns 0 carrier 0 collisions 0</nowiki>		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.

	== Optional: Setting Up An Access Point ==		== Optional: Setting Up An Access Point ==
	The recommended way to use a Raspberry Pi as the router for your subnet is with two ethernet interfaces. The second can be provided by a USB ethernet adapter or an ethernet hat.		The recommended way to use a Raspberry Pi as the router for your subnet is with two ethernet interfaces. The second can be provided by a USB ethernet adapter or an ethernet hat.
	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.		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.

			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 ===		=== Step 1: Set your wireless regulatory domain ===
Line 60:		Line 65:

	<code>sudo nmcli con modify <connection name> wifi-sec.pairwise ccmp</code>		<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.

	== Setting up DHCP ==		== Setting up DHCP ==

KN6DWI: Added missing line breaks

2026-06-16T23:47:44Z

Added missing line breaks

← Older revision		Revision as of 23:47, 16 June 2026
Line 48:		Line 48:

	Next, set the access point security and password.		Next, set the access point security and password.

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

Line 53:		Line 54:

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

	<code>sudo nmcli con modify <connection name> wifi-sec.proto 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.		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>		<code>sudo nmcli con modify <connection name> wifi-sec.pairwise ccmp</code>

KN6DWI: Started writing section on creating the AP

2026-06-16T22:29:48Z

Started writing section on creating the AP

@@ Line 37: / Line 37: @@
 set under <code>global</code>. If it says <code>unset</code>, you have not set the regulatory domain.
-=== Step 2: Create a new WiFi interface in nmcli ===
+=== Step 2: Create a new WiFi connection in nmcli ===
 == Setting up DHCP ==

KN6DWI: Edited example phrasing

2026-06-16T19:02:21Z

Edited example phrasing

← Older revision		Revision as of 19:02, 16 June 2026
Line 10:		Line 10:
	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.		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.

	~~This~~ is ~~what the~~ output of <code>ifconfig wg0</code> ~~looks like~~.		Below is some example output of <code>ifconfig wg0</code>.

	<nowiki>		<nowiki>