44Net Connect/Single Device Tunnel - Revision history

KN6DWI: Added categories

2026-06-04T21:23:48Z

Added categories

← Older revision		Revision as of 21:23, 4 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]]


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

KN6DWI: Added topology diagram

2026-06-04T21:22:08Z

Added topology diagram

← Older revision		Revision as of 21:22, 4 June 2026
Line 8:		Line 8:
	== What is a single device tunnel? ==		== What is a single device tunnel? ==
	A single device tunnel is a configuration where one device can send and receive traffic from its 44Net address via one of ARDC's endpoint nodes. This is done using a WireGuard tunnel, with a configuration file issued by [[44Net Connect]]. Each device connected in this manner is issued a single IPv4 address and a single IPv6 address, and it does not depend on a local gateway for connection to 44Net. A host using a single device tunnel may choose whether or not to route non-44Net traffic via the tunnel. Routing only 44Net traffic over the tunnel is a common configuration, and is called a "split tunnel."		A single device tunnel is a configuration where one device can send and receive traffic from its 44Net address via one of ARDC's endpoint nodes. This is done using a WireGuard tunnel, with a configuration file issued by [[44Net Connect]]. Each device connected in this manner is issued a single IPv4 address and a single IPv6 address, and it does not depend on a local gateway for connection to 44Net. A host using a single device tunnel may choose whether or not to route non-44Net traffic via the tunnel. Routing only 44Net traffic over the tunnel is a common configuration, and is called a "split tunnel."

			[[File:Single_device_tunnel.png\|600px]]

	== When should I use a single device tunnel? ==		== When should I use a single device tunnel? ==

KN6DWI: Terminology change suggested by John KI5QKX, one does not "connect to" 44Net

2026-06-04T18:08:33Z

Terminology change suggested by John KI5QKX, one does not "connect to" 44Net

← Older revision		Revision as of 18:08, 4 June 2026
Line 7:		Line 7:

	== What is a single device tunnel? ==		== What is a single device tunnel? ==
	A single device tunnel is a configuration where one device ~~connects to~~ 44Net via one of ARDC's endpoint nodes. This is done using a WireGuard tunnel, with a configuration file issued by [[44Net Connect]]. Each device connected in this manner is issued a single IPv4 address and a single IPv6 address, and it does not depend on a local gateway for connection to 44Net. A host using a single device tunnel may choose whether or not to route non-44Net traffic via the tunnel. Routing only 44Net traffic over the tunnel is a common configuration, and is called a "split tunnel."		A single device tunnel is a configuration where one device can send and receive traffic from its 44Net address via one of ARDC's endpoint nodes. This is done using a WireGuard tunnel, with a configuration file issued by [[44Net Connect]]. Each device connected in this manner is issued a single IPv4 address and a single IPv6 address, and it does not depend on a local gateway for connection to 44Net. A host using a single device tunnel may choose whether or not to route non-44Net traffic via the tunnel. Routing only 44Net traffic over the tunnel is a common configuration, and is called a "split tunnel."

	== When should I use a single device tunnel? ==		== When should I use a single device tunnel? ==

KN6DWI: Added links to existing single device tunnel tutorials

2026-06-03T23:21:28Z

Added links to existing single device tunnel tutorials

← Older revision		Revision as of 23:21, 3 June 2026
Line 13:		Line 13:

	Devices that cannot run WireGuard, such as some embedded devices, do not support a single device tunnel. These should be placed in a [[44Net_Connect/Routed_Subnet\|routed subnet]] where the router connects them to 44Net.		Devices that cannot run WireGuard, such as some embedded devices, do not support a single device tunnel. These should be placed in a [[44Net_Connect/Routed_Subnet\|routed subnet]] where the router connects them to 44Net.

			== Tutorials ==
			* [[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]]

KN6DWI: Minor phrasing edits

2026-06-03T22:31:18Z

Minor phrasing edits

← Older revision		Revision as of 22:31, 3 June 2026
Line 10:		Line 10:

	== When should I use a single device tunnel? ==		== When should I use a single device tunnel? ==
	If you are not comfortable with router and firewall configuration~~, you only have a few devices to manage~~, or you're not sure where to start, a single device tunnel is a good choice. Mobile devices, such as phones and laptops, cannot rely on always being behind an appropriate gateway, so they work best with a single device tunnel.		If you only have a few devices to manage, you are not comfortable with router and firewall configuration, or you're not sure where to start, a single device tunnel is a good choice. Mobile devices, such as phones and laptops, cannot rely on always being behind an appropriate gateway or router, so they work best with a single device tunnel.

	Devices that cannot run WireGuard, such as some embedded devices, do not support a single device tunnel. These should be placed in a [[44Net_Connect/Routed_Subnet\|routed subnet]] where the router connects them to 44Net.		Devices that cannot run WireGuard, such as some embedded devices, do not support a single device tunnel. These should be placed in a [[44Net_Connect/Routed_Subnet\|routed subnet]] where the router connects them to 44Net.

KN6DWI: Created section "When should I use a single device tunnel?"

2026-06-01T22:52:32Z

Created section "When should I use a single device tunnel?"

← Older revision		Revision as of 22:52, 1 June 2026
Line 7:		Line 7:

	== What is a single device tunnel? ==		== What is a single device tunnel? ==
	A single device tunnel is a configuration where one device connects to 44Net via one of ARDC's endpoint nodes. This is done using a WireGuard tunnel, with a configuration file issued by [[44Net Connect]]. Each device connected in this manner is issued a single IPv4 address and a single IPv6 address, and it does not depend on a local gateway for connection to 44Net.		A single device tunnel is a configuration where one device connects to 44Net via one of ARDC's endpoint nodes. This is done using a WireGuard tunnel, with a configuration file issued by [[44Net Connect]]. Each device connected in this manner is issued a single IPv4 address and a single IPv6 address, and it does not depend on a local gateway for connection to 44Net. A host using a single device tunnel may choose whether or not to route non-44Net traffic via the tunnel. Routing only 44Net traffic over the tunnel is a common configuration, and is called a "split tunnel."

			== When should I use a single device tunnel? ==
			If you are not comfortable with router and firewall configuration, you only have a few devices to manage, or you're not sure where to start, a single device tunnel is a good choice. Mobile devices, such as phones and laptops, cannot rely on always being behind an appropriate gateway, so they work best with a single device tunnel.

			Devices that cannot run WireGuard, such as some embedded devices, do not support a single device tunnel. These should be placed in a [[44Net_Connect/Routed_Subnet\|routed subnet]] where the router connects them to 44Net.

KN6DWI: Create Single Device Tunnel page

2026-06-01T22:38:34Z

Create Single Device Tunnel page

New page

<div class="toclimit-3">
__TOC__
</div>
{{DISPLAYTITLE:Single Device Tunnel - 44Net Connect}}

This page discusses the single device tunnel configuration for connecting a device to 44Net via 44Net Connect.

== What is a single device tunnel? ==
A single device tunnel is a configuration where one device connects to 44Net via one of ARDC's endpoint nodes. This is done using a WireGuard tunnel, with a configuration file issued by [[44Net Connect]]. Each device connected in this manner is issued a single IPv4 address and a single IPv6 address, and it does not depend on a local gateway for connection to 44Net.