Explore WireGuard support for double-hop #176
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Split from #88. Double-hop is OpenVPN-only today, and the research on #88 concluded the feature's value lives in cross-provider chaining — WireGuard support is what would make it matter to new users, since a WG-first user currently can't use it at all.
The current implementation is OpenVPN-specific: routing is driven by
--up/--downhooks callingscripts/hop.sh/hop_down.sh, so WireGuard needs its own routing path, not a port of those hooks.Prerequisite: the WireGuard tunnel path has to be validated at all first (#152, step 1 — it has never been exercised live, even single-hop).
Sequencing note: #208 (one catalog entry per server, tunnel as a connect-time choice) is deliberately queued behind this issue - both rework the same tunnel-selection seams (connect_dict, tunnel.work() dispatch, per-provider protocol choice), and this one goes first. The AirVPN/Windscribe WireGuard imports (#209/#210) then land on the unified model.