vpn-software.info · technical notes

VPN software — apps, protocols and the settings that matter

VPN Software Compared

Provider app vs manual config, WireGuard vs OpenVPN, and the switches that actually protect you.

Quick answer: for most people the provider's own app is the right choice — it handles kill switches, key rotation and server selection correctly. Power users can use manual WireGuard/OpenVPN configs for transparency, but take responsibility for leak protection themselves.

Protocol comparison

ProtocolSpeedAudit statusBest for
WireGuardFastest (~4k lines of code)Multiple audits, kernel-integrated on LinuxEverything — default choice now
OpenVPNSlower but stableBattle-tested 20+ yearsCompatibility, obfuscated setups
IKEv2/IPSecFast, mobile-friendlySolid but closed implementations varyMobile devices reconnecting networks
Proprietary (NordLynx, Lightway…)Very fastWireGuard-based, open-source clientsFine if code is auditable
PPTP/L2TP—Broken/weakAvoid — deprecated

Settings that actually matter

Manual config vs provider apps

Provider appManual config
Setup effortZeroModerate
Kill switch/leak protectionBuilt-inYour responsibility
TransparencyTrust the appYou control everything
Key rotation, updatesAutomaticManual
Who it's forMost usersAdvanced users, routers, custom setups

How to verify your VPN is actually working

  1. ipleak.net — check IP, DNS servers, WebRTC leaks.
  2. dnsleaktest.com — extended test for DNS leaks.
  3. Kill-switch test — download a large file, disconnect VPN, watch traffic die.
  4. tracert/traceroute to a known host — confirm the first hop is the VPN, not your ISP.

Sources

VPN software — the protocol wars and what survived

The software layer tells the real story. OpenVPN (2001) won two decades on configurability — but its ~100k+ lines made audits expensive and throughput modest. WireGuard (announced 2015, kernel-merged 2020) rebuilt the stack around ~4,000 auditable lines, modern crypto and near-instant handshakes; provider implementations (NordLynx, Lightway) filled its static-IP gaps.

The settings that actually protect you are fewer than apps suggest. The kill switch is the only non-negotiable — everything else is preference. App vs manual config is a trust question: provider apps add leak protection but also their own telemetry; manual WireGuard configs remove the provider's software entirely.

Counted and measured

ItemReality
Protocol code auditabilityWireGuard ~4k LOC vs OpenVPN ~100k+ vs IKEv2 closed stacks
Real-world throughput deltaWireGuard typically 2-4× OpenVPN on same link
Kill switch failure modesmost leaks happen on reconnect/roaming, not steady state
App telemetrymost provider apps phone home usage stats — check the privacy policy for 'diagnostics'
DNS leak ratemost common real-world failure — force provider DNS or verified resolvers

The settings checklist that matters: kill switch on, protocol = WireGuard unless a network blocks UDP, DNS forced through the tunnel, app auto-start off on untrusted machines. That covers ~95% of real-world leak scenarios; the rest is theatre.

What the install base teaches

The download numbers across platforms show where the real usage is: mobile clients now account for the majority of installs, but desktop remains where the protocol engineering shows — WireGuard's 4,000-line kernel implementation versus OpenVPN's sprawling codebase is the canonical example of how design simplicity became a security feature, not just a performance one.

Choosing between the generations

The practical 2026 matrix: WireGuard-class protocols (including NordLynx, Lightway and friends) for anything latency-sensitive; OpenVPN remains the fallback where network filtering is hostile — it survives places WireGuard doesn't because it can masquerade as ordinary TLS. Protocol choice now matters more than provider branding in most use cases.

The install-and-forget test that separates software tiers: does the client reconnect cleanly after sleep/network-switch, does the kill switch survive edge cases, and can you read the source or the audit? Everything else is skin.

Expert context · 2026

“The protocol matters less than the implementation — a misconfigured WireGuard leaks less than a misconfigured OpenVPN only because there's less to misconfigure.”

— Jon Callas, cryptographer, EFF · eff.org