Skip to content

Linux VPS network gateway

A Linux VPS is a good The Gateway node when you need a stable public endpoint, a remote egress, or a partner for a local gateway. It is not automatically more private: the hosting provider still controls the underlying server and network.

  • A supported 64-bit Linux VPS with root access.
  • A provider that permits the intended VPN, forwarding, and bandwidth use.
  • A public IP or another deliberate reachability path.
  • Firewall rules that expose only the required management and tunnel ports.
  • A recovery route through the provider console in case routing changes lock out SSH.

Use the vps profile from the installation guide. Before applying a default-route or firewall change, keep a second provider-console session available.

Recommended sequence:

  1. Install and confirm service health without changing the SSH path.
  2. Restrict management access to a trusted network or mesh.
  3. Configure one tunnel or bridge and test it from a non-critical client.
  4. Add the local gateway to the mesh or federation.
  5. Validate fail-closed behaviour and recovery before moving production devices.
  • Stable inbound access for a home lab behind CGNAT.
  • Remote bridge or egress in a chosen region.
  • Federation primary for several small sites.
  • A test node that mirrors policy without sharing the local hardware failure domain.
  • The VPS operator can observe metadata and control the host beneath your VM.
  • Public management interfaces increase attack surface.
  • Bandwidth limits and provider policies can matter more than CPU.
  • A routing error can remove SSH access; provider-console recovery is essential.
  • Region does not by itself guarantee a privacy or legal outcome.

Verify the public exit, DNS path, exposed ports, tunnel recovery, and provider bandwidth accounting. Use the reproducible method on Performance evidence & release verification rather than assuming the advertised VPS port speed is sustained throughput.