Direwolf - Revision history

KN6DWI: Mentioned AGW clients in intro paragraph

2026-09-10T00:25:04Z

Mentioned AGW clients in intro paragraph

← Older revision		Revision as of 00:25, 10 September 2026
Line 1:		Line 1:
	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.		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 or AGW client. This is a tutorial on setting up Direwolf for remote access via a 44Net Connect tunnel.

	Prerequisites:		Prerequisites:

KN6DWI: Formatting fix

2026-09-09T18:09:20Z

Formatting fix

← Older revision		Revision as of 18:09, 9 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 {{Term:AllowedIPs}} 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: Changed long display of term AllowedIPs to inline only

2026-09-09T18:00:14Z

Changed long display of term AllowedIPs to inline only

← Older revision		Revision as of 18:00, 9 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 {{Term\|AllowedIPs}} 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: Formatting fix for inline code

2026-09-09T17:59:48Z

Formatting fix for inline code

← Older revision		Revision as of 17:59, 9 September 2026
Line 14:		Line 14:

	=== Configure sound card ===		=== Configure sound card ===
	Next, plug in your USB sound card if you're using one. (This section applies whether you're using a USB sound card or a built-in one.) then open a terminal and run `arecord -l` to list your audio devices. The output will look like this:		Next, plug in your USB sound card if you're using one. (This section applies whether you're using a USB sound card or a built-in one.) then open a terminal and run <code>arecord -l</code> to list your audio devices. The output will look like this:
	<nowiki>		<nowiki>
	** List of CAPTURE Hardware Devices **		** List of CAPTURE Hardware Devices **

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]