Skip to content

How VPNs work: complete guide (business & personal)

Tunnelling, encryption protocols, and the design difference between business and personal VPNs.

How a VPN packet flows
Your device → VPN client (encrypt & tunnel) → internet (encrypted tunnel) → VPN server (decrypt & forward) → destination. The destination sees the VPN server, not you.

Core VPN concepts

1. Tunnelling: the foundation

Tunnelling is the process of encapsulating one network protocol inside another. VPNs create virtual "tunnels" through existing networks by wrapping your data in additional headers that define the tunnel endpoints.

Original data: [Your web request to bank.com]
        ↓
VPN tunnelling: [VPN Header][Encryption][Your web request][VPN Footer]
        ↓
Internet transport: [Internet Header][VPN Tunnel with encrypted data][Internet Footer]
        ↓
VPN server: removes VPN tunnel, forwards original request to bank.com

2. Encryption: protecting the tunnel

Modern VPNs use strong encryption algorithms to ensure that even if someone intercepts your tunnelled data, they can't read it without the decryption keys.

Common encryption standards:

  • AES-256 — military-grade encryption standard.
  • AES-128 — faster, still very secure.
  • ChaCha20 — modern alternative, good for mobile.
  • 3DES — older standard, still used in legacy systems.

Key exchange methods:

  • RSA — traditional public key method.
  • ECDH — elliptic curve, more efficient.
  • Diffie–Hellman — classic key agreement.
  • PSK — pre-shared keys for simple setups.

3. Authentication: verifying identity

Before establishing tunnels, VPNs must verify that both endpoints are legitimate. This prevents unauthorised access and man-in-the-middle attacks.

Enterprise VPN architecture

Enterprise VPNs are designed to extend corporate networks securely across the internet, enabling remote access and site-to-site connectivity.

Site-to-site VPNs

Connect multiple office locations as if they were on the same physical network.

Headquarters network:

  • Network: 10.1.0.0/16
  • VPN gateway: enterprise firewall
  • Services: domain controllers, file servers
  • Public IP: static IP for VPN endpoint

Branch office network:

  • Network: 10.2.0.0/16
  • VPN gateway: branch router / firewall
  • Services: local printers, workstations
  • Connection: always-on IPsec tunnel

Routing configuration. Both sites maintain routing tables that direct traffic for remote networks through the VPN tunnel:

# Headquarters routing
10.2.0.0/16 via VPN_TUNNEL (to branch office)

# Branch office routing
10.1.0.0/16 via VPN_TUNNEL (to headquarters)

Remote access VPNs

IPsec with IKEv2. Industry standard for enterprise remote access. Excellent security and performance, built into most operating systems. Strong authentication, automatic reconnection, mobile device support, certificate-based auth.

SSL/TLS VPN. Browser-based or thin client access. Easier deployment, works through firewalls, good for contractors. No client installation, granular access control, web-based management, application-level access.

Enterprise authentication integration

Enterprise VPNs typically integrate with existing authentication systems:

  • LDAP / Active Directory — user credentials and group policies.
  • RADIUS — centralised authentication, accounting, authorisation.
  • Certificate Authority — X.509 certificates for device authentication.
  • Multi-Factor Authentication — token-based or SMS verification.

Consumer VPN technology

Consumer VPNs prioritise ease of use, privacy protection, and geographic flexibility over enterprise network integration.

Modern consumer VPN protocols

WireGuard. Next-generation VPN protocol. Extremely fast, secure, and simple. Becoming the new standard for consumer VPNs.

  • Pros: very fast, battery efficient, modern crypto, simple codebase.
  • Cons: relatively new, static IP assignment, limited commercial deployment.

OpenVPN. Mature, proven protocol. Highly configurable, works in restrictive environments, widely supported by VPN providers.

  • Pros: proven security, highly configurable, firewall-friendly, open source.
  • Cons: more resource intensive, complex configuration, slower than WireGuard.

Consumer VPN privacy features

Kill switch. Automatically blocks internet traffic if VPN connection drops, preventing IP leaks.

DNS leak protection. Routes DNS queries through VPN tunnel to prevent ISP from seeing visited domains.

Split tunnelling. Allows some apps to use VPN while others connect directly to internet.

No-logs policy. VPN provider doesn't store records of user activity or connection logs.

Multi-hop. Routes traffic through multiple VPN servers for additional privacy layers.

Obfuscation. Disguises VPN traffic as regular HTTPS to bypass VPN blocking.

VPN protocols technical comparison

ProtocolUse caseSecuritySpeedCompatibilityConfiguration
IPsec/IKEv2Enterprise, mobileExcellentVery goodNative OS supportModerate
OpenVPNConsumer, flexibilityExcellentGoodRequires clientComplex
WireGuardModern consumerExcellentExcellentGrowing supportSimple
SSL/TLSBrowser-based accessGoodModerateAny browserSimple
PPTPLegacy onlyPoorFastUniversalSimple
L2TP/IPsecEnterprise legacyGoodModerateGoodModerate

Implementation considerations

Factors that affect VPN speed

  • Distance to server — physical distance adds latency.
  • Encryption overhead — stronger encryption = more processing.
  • Server load — overloaded servers slow performance.
  • Protocol choice — WireGuard fastest, OpenVPN slower.
  • ISP throttling — some ISPs deprioritise VPN traffic.
  • Device capability — older devices may struggle with encryption.

Optimisation strategies

  • Choose nearby servers — minimise geographical distance.
  • Use modern protocols — WireGuard or IKEv2 for speed.
  • Hardware acceleration — use devices with crypto acceleration.
  • Bandwidth allocation — ensure adequate internet speeds.
  • Protocol tuning — optimise MTU size and keepalives.
  • Load balancing — distribute traffic across multiple servers.

Security considerations

Potential vulnerabilities
  • DNS leaks — queries bypass VPN tunnel.
  • IPv6 leaks — IPv6 traffic not tunnelled.
  • WebRTC leaks — browser reveals real IP.
  • Kill switch failures — traffic flows during disconnection.
  • Weak protocols — PPTP, weak encryption.

Best practices:

  • Test for leaks — regularly verify IP/DNS protection (try our IP check).
  • Use strong protocols — WireGuard, OpenVPN, IKEv2.
  • Enable kill switch — prevent traffic leaks.
  • Disable IPv6 if not supported by VPN.
  • Verify certificates to prevent MITM attacks.

Future of VPN technology

Technology evolution:

  • Post-quantum cryptography — preparing for quantum computers.
  • Zero Trust architecture — VPNs as part of comprehensive security.
  • Cloud-native VPNs — serverless, auto-scaling infrastructure.
  • AI-powered optimisation — intelligent server selection and routing.

Market changes:

  • 5G integration — VPNs optimised for mobile networks.
  • IoT protection — VPNs for smart devices and sensors.
  • Regulatory compliance — VPNs adapting to privacy laws.
  • Mesh networking — decentralised VPN architectures.

Related reading: What is a VPN? · VPN vs Proxy vs Tor