To interconnect your sites, mobile users or clouds, WANUP relies on WireGuard®, the next-generation VPN protocol. Faster than IPsec, simpler than OpenVPN, and perfectly suited to modern SD-WAN.
WireGuard is a modern VPN protocol natively integrated into our WANUP SD-WAN solution. Unlike IPsec (a 1990s technology), WireGuard delivers ultra-high-performance encrypted tunnels that are simple to configure and perfectly suited to multi-site, remote working and cloud access.
WANUP uses WireGuard to:
Automatically create encrypted tunnels between your sites (full mesh or hub & spoke)
Connect remote users (remote working, maintenance, contractors)
Secure traffic to your public clouds (AWS, Azure, OVHcloud…)
WireGuard uses very little CPU, enables throughput of up to 1–2 Gb/s on standard hardware, and reduces latency. Where IPsec often limits tunnels to between 200 and 600 Mb/s, WireGuard makes full use of French fibre (FTTH, FTTO, FTTE).
No complicated configurations (IKEv2, MTU, NAT-T…). A few keys, one interface, and the tunnel is up and running. Reconnection is instant after an outage — ideal for remote sites or 4G/5G.
ChaCha20 encryption, Curve25519, no obsolete cipher suites, no lengthy negotiations: it is the modern standard recommended by many security agencies.
Each tunnel integrates with the Wanup SD-WAN engine: application rules, prioritisation, automatic cutover from one operator to another, network segmentation and more.
| WireGuard | IPsec | |
|---|---|---|
| Real throughput on standard CPU (Intel i5/i7) | 1 to 2 Gbit/s with no loss of performance | 200 to 600 Mbit/s depending on model, sometimes <300 Mb/s with IPS/SSL enabled |
| Latency added by the tunnel | 1 to 3 ms (virtually transparent) | 5 to 15 ms (depending on encapsulation + IKE negotiation) |
| Encryption algorithms | ChaCha20, Poly1305, Curve25519 (modern cryptography) | AES-CBC, AES-GCM, DH modp (1990s–2000s tech) |
| Configuration complexity | 5 to 10 lines of config, public/private keys only | IKEv2, PSK, MTU, NAT-T, lifetimes, PFS configuration, etc. |
| Automatic reconnection after outage / network change | Instant (<1 second), ideal for 4G/5G & remote working | Full authentication, session loss (up to 10-30 sec) |
| Suited to multi-carrier SD-WAN | Yes, native (stateless, very lightweight) | No, requires failover or dual IPsec tunnels |
| Visibility for QoS / SD-WAN segmentation | Native integration with WANUP rules (app-aware QoS) | Opaque tunnel, hard to prioritise / classify |
| Zero Trust / ZTNA compatibility | Yes, direct integration with device + user authentication | Designed for site-to-site, poorly suited to user Zero Trust |
| Maintenance / monitoring | Few logs, no IKE renegotiation, very stable | Many IKE logs, SA errors, frequent desynchronisation |
| Obsolescence / future | Modern protocol (2017), geared to cloud / edge computing | Legacy standard (1995), maintained through inertia |
Discover how our solution
is implemented in the field.