44Net Connect/Routed Subnet: Difference between revisions
Added categories and diagram |
m Fixed category links |
||
| Line 9: | Line 9: | ||
In some applications, it is important that all traffic associated with a service appear to come from the same public address. In those cases, a full-tunnel configuration or a gateway model may be more appropriate than per-host split tunneling. | In some applications, it is important that all traffic associated with a service appear to come from the same public address. In those cases, a full-tunnel configuration or a gateway model may be more appropriate than per-host split tunneling. | ||
[[ | [[Category:Topology]] | ||
[[ | [[Category:Participation Methods]] | ||
Revision as of 21:27, 4 June 2026
What is a routed subnet?
A routed subnet is a group of devices that are placed behind a router which provides them access to 44Net. The router is provided with a WireGuard tunnel configuration that connects it to one of ARDC's nodes. In a typical routed subnet, all traffic from the devices in the subnet is routed through 44Net via the router. Devices do not have individual control over which traffic is proxied through the 44Net node. The router with the tunnel is in control of this.
When should I use a routed subnet?
If you have many devices to manage, or one of your devices is not capable of running WireGuard, a routed subnet is a good choice. A routed subnet eliminates the complexity of managing configuration for many individual devices, since there is only the router's configuration.
In some applications, it is important that all traffic associated with a service appear to come from the same public address. In those cases, a full-tunnel configuration or a gateway model may be more appropriate than per-host split tunneling.