Tailscale vs. OpenWRT: The War for Perfect VPN Tunneling
Achieving multi-layered VPN routing demands specialized tools. Users cite OpenWRT with custom firmware as the necessary platform for chaining protocols like WireGuard through multiple providers.
The field splits sharply between absolute simplicity and total control. Advocates for ease use Tailscale or RDP tools like Rustdesk for non-technical remote access. Conversely, experts like SpacePirate argue that complex chains require deep router configuration. Scott suggests RethinkDNS for software-level control, while stratself points to Tailscale's Exit Nodes for managed complex routing.
The consensus demands technical specialization: simple remote access favors managed tools, but advanced, overlapping VPN functionality necessitates deep OS/firmware hacking. The major friction point remains balancing the 'ease of use' promised by consumer tools against the 'control' offered by self-hosted setups like Headscale.
Key Points
OpenWRT is required for complex VPN chaining.
SpacePirate asserts that chaining Phone -> WireGuard -> OpenWRT -> VPN Provider demands specialized router firmware.
Tailscale is the easiest option for non-technical remote access.
ji_reilly strongly recommends Tailscale or Rustdesk for users needing simplicity.
Using RethinkDNS manages simultaneous VPN connections.
Scott suggests specialized apps like RethinkDNS for software-based connection management.
Android OS limits VPN usage on mobile devices.
The technical insight notes Android prevents multiple VPNs simultaneously, forcing Work Profiles or deep routing workarounds.
Split tunneling prevents performance degradation.
N0x0n mandates using split tunneling (allowed_ips) for WireGuard instead of routing all traffic (0.0.0.0/0).
Source Discussions (3)
This report was synthesized from the following Lemmy discussions, ranked by community score.