New: a threat-model-first guide to choosing your network defence, plus the nym-smoldvpn dVPN package and nym-swizzle sender hygiene.
Network
Threat Model
Configurations
dVPN · single exit

dVPN · single exit

✅IP hidden · P1@L2❌Req-unlink · P2@L2❌Local net · P1@L3L❌Global net · P1@L3G✅Fast
L2The destination✅P1❌P2

Sees

  • Exit gateway IP
  • All requests and contents

Can't see

  • Client IP

Residual / countermeasure

  • P2 fails within a session: the tunnel delivers one NATed flow. Across sessions, linkage depends on crowding at the exit IP.
  • Rotate the exit per request to restore P2. See the multi-exit configuration.
L3LLocal network observer

Sees

  • Activity fingerprint: WireGuard adds no cover and preserves packet timing
L3GGlobal network observer

Sees

  • End-to-end flow correlation

Residual / countermeasure

  • The 2-hop route stops a single gateway linking client to destination, but both gateways colluding, or a global observer, can still correlate.

Pros

  • Fast
  • Deployable today

Cons / mitigations

  • A fixed exit is a linking key: rotate per request

Fit

  • The minimum: hides IP; add exit rotation and baseline hygiene

Verdicts and the latency implied by the path are an illustrative model, not measured values.

VPNdVPN · multi-exit