Direwolf - Revision history

KN6DWI: Added reference for APRS-IS servers

2026-09-03T22:36:16Z

Added reference for APRS-IS servers

← Older revision		Revision as of 22:36, 3 September 2026
Line 35:		Line 35:

	=== Configure iGate login ===		=== Configure iGate login ===
	To enable iGate functionality, you must configure your iGate server and login. The server is configured using the line starting with <code>IGSERVER</code>. Select your server from the following:		To enable iGate functionality, you must configure your iGate server and login. The server is configured using the line starting with <code>IGSERVER</code>. Select your server from the following:<ref>https://www.aprs-is.net/APRSServers.aspx</ref>

	* Worldwide: <code>rotate.aprs2.net</code>		* Worldwide: <code>rotate.aprs2.net</code>

KN6DWI: Changed AllowedIPs to term

2026-09-03T22:03:44Z

Changed AllowedIPs to term

← Older revision		Revision as of 22:03, 3 September 2026
Line 59:		Line 59:

	== Step 5: Verify IP whitelist configuration ==		== Step 5: Verify IP whitelist configuration ==
	To verify that the WireGuard configuration is correctly blocking access from unauthorized parties, try connecting to Direwolf from an IP address that's not whitelisted. If your typical connection method uses another 44Net Connect tunnel on the client device, try turning it off. If you've whitelisted a static IP tied to your current network, you could go to a cafe and use their internet. Use <code>curl connect.44net.cloud/myip</code> to verify that your IP has changed, then attempt to connect. You should ''not'' be able to connect from a non-whitelisted IP. If you are able to connect, your WireGuard ~~<code>~~AllowedIPs~~</code>~~ may not be correctly configured.		To verify that the WireGuard configuration is correctly blocking access from unauthorized parties, try connecting to Direwolf from an IP address that's not whitelisted. If your typical connection method uses another 44Net Connect tunnel on the client device, try turning it off. If you've whitelisted a static IP tied to your current network, you could go to a cafe and use their internet. Use <code>curl connect.44net.cloud/myip</code> to verify that your IP has changed, then attempt to connect. You should ''not'' be able to connect from a non-whitelisted IP. If you are able to connect, your WireGuard {{Term\|AllowedIPs}} may not be correctly configured.

	== Troubleshooting ==		== Troubleshooting ==

KN6DWI: Fixed typo

2026-09-03T18:36:25Z

Fixed typo

← Older revision		Revision as of 18:36, 3 September 2026
Line 66:		Line 66:
	* If you are unsure whether your client is behind a firewall whose egress filtering is preventing connection, you can open listeners on ports 8000 and 8001 to see if your connection is making it there at all.		* If you are unsure whether your client is behind a firewall whose egress filtering is preventing connection, you can open listeners on ports 8000 and 8001 to see if your connection is making it there at all.
	** This will require closing Direwolf for the duration of the test.		** This will require closing Direwolf for the duration of the test.
	** Open a listener with <code>netcat</code> using the following command: <code>nc -l -p <~~port></~~port></code>		** Open a listener with <code>netcat</code> using the following command: <code>nc -l -p <port></code>
	** After opening the listeners on ports 8000 and 8001, attempt to connect with your client. If the listeners don't show any activity, your connection attempt is not making it to the server.		** After opening the listeners on ports 8000 and 8001, attempt to connect with your client. If the listeners don't show any activity, your connection attempt is not making it to the server.

	=== Direwolf isn't receiving any packets ===		=== Direwolf isn't receiving any packets ===

KN6DWI: Fixed typo

2026-09-03T18:35:23Z

Fixed typo

← Older revision		Revision as of 18:35, 3 September 2026
Line 51:		Line 51:

	== Step 3: Set up 44Net Connect tunnel ==		== Step 3: Set up 44Net Connect tunnel ==
	Set up a single device tunnel on the machine that will host your ~~Minecraft~~ server. Go to the [https://wiki.ampr.org/wiki/44Net_Connect/Single_Device_Tunnel#Tutorials list of single device tunnel tutorials] and follow the one for your operating system. Before starting the tunnel, you'll need to modify your configuration. Modify the <code>AllowedIPs</code> line so that it contains only the static IPs of your clients, each followed by <code>/32</code> to indicate that this is a single IP rather than a subnet. This is the method by which access to your Direwolf instance is controlled. Example:		Set up a single device tunnel on the machine that will host your Direwolf server. Go to the [https://wiki.ampr.org/wiki/44Net_Connect/Single_Device_Tunnel#Tutorials list of single device tunnel tutorials] and follow the one for your operating system. Before starting the tunnel, you'll need to modify your configuration. Modify the <code>AllowedIPs</code> line so that it contains only the static IPs of your clients, each followed by <code>/32</code> to indicate that this is a single IP rather than a subnet. This is the method by which access to your Direwolf instance is controlled. Example:

	<nowiki>AllowedIPs = 44.27.133.290/32</nowiki>		<nowiki>AllowedIPs = 44.27.133.290/32</nowiki>

KN6DWI: Added term link for APRS

2026-09-03T18:15:25Z

Added term link for APRS

← Older revision		Revision as of 18:15, 3 September 2026
Line 1:		Line 1:
	Direwolf is a piece of software used to decode and encode APRS packets, commonly called a terminal node controller (TNC). A computer running Direwolf can be paired with a transceiver to transmit, receive, and digipeat APRS packets on the air. It can be used on its own or with a KISS client. This is a tutorial on setting up Direwolf for remote access via a 44Net Connect tunnel.		Direwolf is a piece of software used to decode and encode {{Term\|APRS}} packets, commonly called a terminal node controller (TNC). A computer running Direwolf can be paired with a transceiver to transmit, receive, and digipeat APRS packets on the air. It can be used on its own or with a KISS client. This is a tutorial on setting up Direwolf for remote access via a 44Net Connect tunnel.

	Prerequisites:		Prerequisites:

KN6DWI: Separated footnotes from general references

2026-09-03T17:34:50Z

Separated footnotes from general references

← Older revision		Revision as of 17:34, 3 September 2026
Line 76:		Line 76:

	== References ==		== References ==
			=== Footnotes ===
			<references />

			=== Other References ===
	* [https://github.com/wb2osz/direwolf/tree/master/doc Direwolf documentation]		* [https://github.com/wb2osz/direwolf/tree/master/doc Direwolf documentation]
	* [https://themodernham.com/easy-aprs-igate-and-digipeater-setup-with-direwolf/ Easy APRS iGate and Digipeater Setup with Direwolf - themodernham]		* [https://themodernham.com/easy-aprs-igate-and-digipeater-setup-with-direwolf/ Easy APRS iGate and Digipeater Setup with Direwolf - themodernham]

KN6DWI: Removed redundant sub-bullet point

2026-09-03T17:33:38Z

Removed redundant sub-bullet point

← Older revision		Revision as of 17:33, 3 September 2026
Line 79:		Line 79:
	* [https://themodernham.com/easy-aprs-igate-and-digipeater-setup-with-direwolf/ Easy APRS iGate and Digipeater Setup with Direwolf - themodernham]		* [https://themodernham.com/easy-aprs-igate-and-digipeater-setup-with-direwolf/ Easy APRS iGate and Digipeater Setup with Direwolf - themodernham]
	* [https://n3emc.com/aprs-digipeater-and-igate-with-direwolf/ APRS Digitpeater and iGate with Direwolf]		* [https://n3emc.com/aprs-digipeater-and-igate-with-direwolf/ APRS Digitpeater and iGate with Direwolf]
	** If your Direwolf installation does not create a default configuration file, this site has an example config you can use.


	[[Category:Use Cases]]		[[Category:Use Cases]]
	[[Category:How-To]]		[[Category:How-To]]

KN6DWI: Added missing closing code tag

2026-09-03T17:32:50Z

Added missing closing code tag

← Older revision		Revision as of 17:32, 3 September 2026
Line 66:		Line 66:
	* If you are unsure whether your client is behind a firewall whose egress filtering is preventing connection, you can open listeners on ports 8000 and 8001 to see if your connection is making it there at all.		* If you are unsure whether your client is behind a firewall whose egress filtering is preventing connection, you can open listeners on ports 8000 and 8001 to see if your connection is making it there at all.
	** This will require closing Direwolf for the duration of the test.		** This will require closing Direwolf for the duration of the test.
	** Open a listener with <code>netcat</code> using the following command: <code>nc -l -p <port></port>		** Open a listener with <code>netcat</code> using the following command: <code>nc -l -p <port></port></code>
	** After opening the listeners on ports 8000 and 8001, attempt to connect with your client. If the listeners don't show any activity, your connection attempt is not making it to the server.		** After opening the listeners on ports 8000 and 8001, attempt to connect with your client. If the listeners don't show any activity, your connection attempt is not making it to the server.

KN6DWI: Wrote troubleshooting section

2026-09-02T22:31:50Z

Wrote troubleshooting section

@@ Line 57: / Line 57: @@
 == Step 4: Set up client ==
 Install a KISS or AGW client of your choice, such as [https://github.com/vash909/PyttiAPRS PyttiAPRS] or [https://github.com/Xastir/Xastir Xastir], and point it at the 44Net IPv4 address of the device running Direwolf. You can obtain this address from the <code>[Interface]</code> section of that device's WireGuard config, or you can run the <code>ifconfig</code> command on that device and look for the WireGuard interface. If it asks for port configuration, use port 8000 for AGW and port 8001 for KISS.
 == References ==
@@ Line 63: / Line 80: @@
 * [https://n3emc.com/aprs-digipeater-and-igate-with-direwolf/ APRS Digitpeater and iGate with Direwolf]
 ** If your Direwolf installation does not create a default configuration file, this site has an example config you can use.
 [[Category:Use Cases]]
 [[Category:How-To]]

KN6DWI: Added GitHub links for PyttiAPRS and Xastir

2026-09-02T21:35:50Z

Added GitHub links for PyttiAPRS and Xastir

← Older revision		Revision as of 21:35, 2 September 2026
Line 56:		Line 56:

	== Step 4: Set up client ==		== Step 4: Set up client ==
	Install a KISS or AGW client of your choice, such as PyttiAPRS or Xastir, and point it at the 44Net IPv4 address of the device running Direwolf. You can obtain this address from the <code>[Interface]</code> section of that device's WireGuard config, or you can run the <code>ifconfig</code> command on that device and look for the WireGuard interface. If it asks for port configuration, use port 8000 for AGW and port 8001 for KISS.		Install a KISS or AGW client of your choice, such as [https://github.com/vash909/PyttiAPRS PyttiAPRS] or [https://github.com/Xastir/Xastir Xastir], and point it at the 44Net IPv4 address of the device running Direwolf. You can obtain this address from the <code>[Interface]</code> section of that device's WireGuard config, or you can run the <code>ifconfig</code> command on that device and look for the WireGuard interface. If it asks for port configuration, use port 8000 for AGW and port 8001 for KISS.

	== References ==		== References ==