44Net Connect/Single Device Tunnel: Difference between revisions
Created section "When should I use a single device tunnel?" |
Added categories |
||
| (4 intermediate revisions by the same user not shown) | |||
| 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 | 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? == | ||
If you are not comfortable with router and firewall configuration | 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. | ||
== 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]] | |||
[[Category:Topology]] | |||
[[Category:Participation Methods]] | |||
Latest revision as of 21:23, 4 June 2026
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 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?
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 routed subnet where the router connects them to 44Net.