Networking: VPNs (Virtual Private Networks)
What a VPN Does
A VPN creates a secure, encrypted communication path over a public or otherwise untrusted network (most often the internet), so that traffic passing between two endpoints can't be read or tampered with by anyone observing the underlying network in between. This is one of the security tools already referenced generally in IP Networking in Two-Way Radio Systems for protecting site-to-site radio system backhaul.
Site-to-Site vs. Remote-Access VPNs
VPNs generally fall into two deployment models, and it's worth being clear on which one a given situation calls for:
- Site-to-site VPN connects two entire networks — for example, a repeater site's local network and a central dispatch/core network — through a persistent encrypted tunnel, so devices on either side can communicate as if they were on the same local network, without individually configuring a VPN client on every device. This is the relevant model for linking radio infrastructure across sites over a shared or public IP path (an alternative or supplement to a dedicated private microwave link or leased circuit).
The underlying tunneling/encryption technology can be the same for both models (IPsec, WireGuard, or an SSL/TLS-based VPN can all be configured either way); what differs is whether one endpoint of the tunnel is a whole network's gateway/router or a single client device.
IPsec
IPsec (Internet Protocol Security) is the most common protocol suite underlying site-to-site VPNs: it authenticates and encrypts IP traffic before it leaves the source network and decrypts it on arrival at the destination. IPsec typically uses the Internet Key Exchange (IKE) protocol — built on the Diffie-Hellman algorithm — to securely establish a shared secret key between the two sites before any actual data is encrypted with it, and is often paired with other tunneling protocols like L2TP.
WireGuard: A Newer Alternative
WireGuard is a newer VPN protocol built around a smaller, simpler, more modern codebase than IPsec, generally offering easier configuration and better throughput — see that page for a full comparison, including its cryptokey-routing peer-authorization model and roaming behavior. It's increasingly used for simpler site-to-site and remote-access tunnels, though IPsec remains dominant in large, established enterprise deployments.
SSL/TLS VPNs
A third common category uses SSL/TLS (the same encryption technology behind HTTPS web traffic) rather than IPsec or WireGuard as the tunnel's basis — sometimes delivered as a dedicated VPN client, and sometimes as a "clientless" web-portal style connection reachable from an ordinary browser. SSL/TLS VPNs are frequently favored for remote-access scenarios specifically because the underlying protocol (TLS over TCP port 443) looks like ordinary web traffic to most firewalls, making it less likely to be blocked by restrictive network policies than an unusual VPN protocol/port might be — a practical, non-cryptographic advantage in getting through firewalls a user doesn't control. Note that "SSL" in casual use almost always actually means its modern successor TLS, but the older "SSL" name has stuck around colloquially.
Split Tunneling vs. Full Tunneling
Once a remote-access VPN is connected, its configuration determines which traffic actually goes through the tunnel:
- Full tunnel — all of the client's network traffic, including ordinary internet browsing, is routed through the VPN and out the far end. More secure/controllable (everything is subject to the remote network's policies and visibility) but means all traffic, even traffic unrelated to the private network, takes the extra hop.
- Split tunnel — only traffic actually destined for the private network's address ranges goes through the tunnel; everything else (general internet browsing) goes directly out the client's own local internet connection as normal. More efficient and often better performance for non-tunneled traffic, at the cost of less centralized visibility/control over the client's overall traffic.
Not knowing which mode is configured is a common source of confusing symptoms: on a full tunnel, a user might find their general internet browsing suddenly slower or blocked by the remote network's own content filtering while connected; on a split tunnel, a user might be surprised that something they expected to be routed through the secured tunnel (and subject to its protections) actually wasn't.
Common Misunderstandings
- "A VPN makes everything about my connection anonymous/secure" — a VPN only protects the tunnel itself (the path between the two VPN endpoints); it does nothing about security at either endpoint, and (especially for a commercial/consumer VPN service) the VPN provider itself can typically see the traffic passing through it. For radio-system use, a VPN's job is specifically to protect data in transit across an untrusted network segment, not to provide blanket anonymity or endpoint security.
- "Any two VPN products/protocols will interoperate" — they generally will not. An IPsec endpoint cannot establish a tunnel with a WireGuard-only endpoint, and most VPN products require both ends to speak the same protocol (often the same vendor's implementation) — check compatibility before assuming two different products/sites can simply be pointed at each other.
- "MTU/fragmentation problems mean the VPN is broken" — VPN encapsulation overhead reduces the usable packet size before fragmentation issues appear; this produces a very specific, non-obvious symptom set (small packets/pings work fine, larger transfers or page loads silently hang) that looks like a broken VPN but is actually an MTU/MSS tuning issue — see Troubleshooting RoIP and Gateway Connectivity and Latency, Jitter, and Packet Loss in Voice Networks for this exact failure signature and how to test for it.
Related Pages
- IP Networking in Two-Way Radio Systems
- Networking: IPv6
- Troubleshooting RoIP and Gateway Connectivity
- Latency, Jitter, and Packet Loss in Voice Networks
- Port Forwarding and Remote Access
References
This article is part of the CTI Products Knowledge Base. Questions about RadioPro or MCN products? Call +1 (513) 595-5900 or email info@ctiproducts.com.
Informational only. This article is general background and is not engineering, safety, legal or regulatory advice. Verify requirements with the equipment manufacturer and the applicable authority before relying on it. Product names and trademarks belong to their respective owners.