Test Results
Every WireGuard case we ran on 8 November 2026, with its result on an iPhone and on an Android phone: 40 of 40 cases passed on the iPhone and 35 of 35 on Android.
The phones were an iPhone 12 with iOS 27.2 and a Samsung Galaxy A55 with Android 17, with the code of commit 3731b356 on the iPhone, as a Debug build, and of c1410582, which follows it, on Android, as a debug APK; the iPhone's rows of the wg-release-… cases come from a Release build of 3731b356's code, the kind TestFlight ships. The server was WireGuard in the Linux kernel 6.8 on Ubuntu 24.04, with wireguard-tools 1.0.20210914: a wg0 like the one WireGuard server sets up, on port 51821, with a peer of its own for each phone and for the files without a preshared key and with the wrong one.
- Each case saved a profile with the settings in its row, connected, and moved the traffic in its row through the tunnel to a test server that runs on the WireGuard server itself. That test server logged where each request came from, and every case that moves traffic checked that it came from the phone's own address in the tunnel, so it went through the tunnel.
- Traffic. On the iPhone four 16 MiB transfers at a time ran for the time shown, as downloads, uploads or both, and
wg-many-connectionsran 16 downloads at once. On Android each transfer case moved two 16 MiB downloads, two 16 MiB uploads, or both, andwg-many-connections16 downloads at once; the row shows how long that took. - UDP. In the cases with a DNS query over UDP, the phone asked a public DNS server for the address the query came from: through the tunnel the answer has to name the server's address, and in the split tunnel the phone's own network.
- The server's view. While a case was connected, it asked the server's WireGuard (
wg show) when its peer last had a handshake. - Refusals. A case whose expected result is refused passed when the app did not connect and ended with the message shown in its row.
- Log levels. The cases named
wg-log-…moved 40 seconds of downloads (4 seconds at Debug), read the connection log back and checked its lines; no level may show a key. The cases namedwg-release-…ran on a Release build of the iPhone app, the kind TestFlight ships. - Lifecycle. The cases named
wg-life-…checked On Sleep; the server's WireGuard restarting (wg-quick), stopped for 8 seconds, stopped for 150 seconds without Auto Reconnect and for 120 seconds with Retry Times 2; a dead path (every packet of the session dropped, without a reset); and a change of network. On Android the screen was really turned off and Wi-Fi was really switched off and on, with pings through the tunnel to the server's tunnel address answered over mobile data in between (for that case the server's firewall also accepted the phone's mobile address), and a ping from the phone's shell kept traffic going while the server was away; on the iPhone the On Sleep case tells the tunnel that the phone slept, and the network case makes the tunnel move its sockets as it does when the network changes. - The guide's server. The cases named
wg-guide-…ran last: the test setup was taken down, the server was set up again with the steps of WireGuard server as the page shows them, and the phones used the page's own files forphone1and the removedphone2.
How to read the results
| Label | Meaning |
|---|---|
| VERIFIED — TESTED SUCCESSFULLY | The case did what its row expects: it connected and moved its traffic through the tunnel, or it was refused with the message shown. |
| TESTED — FAILED | The case did not do what its row expects; the row says what happened. |
| NOT VERIFIED | The case did not run on that phone. |
Speeds are averages over the whole transfer on our office line. They show that traffic moved, and are not a benchmark. When both directions ran at once on the iPhone, the downloads took most of the line.
Not tested in this round
- Moving between Wi-Fi and cellular on the iPhone. The iPhone's network case makes the tunnel move its sockets without a real change of network.
- Real sleep on the iPhone. The iPhone's On Sleep case tells the tunnel that the phone slept; the phone did not really sleep.
- IPv6 inside the tunnel, and an IPv6 endpoint. Our server has no IPv6 address.
- Servers other than the kernel's WireGuard, such as a router's or a commercial service's.
- Importing a file through the app's screens on the iPhone. The cases gave the app the file's text as an import does; the import's checks were tested in the apps' unit tests, and on Android a Release build imported a file through the system's file picker.
Transfers and UDP
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
wg-download | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s | download, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY 194.17 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer ios1 7 s before it was asked | VERIFIED — TESTED SUCCESSFULLY transfer 3.7 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer android1 13 s before it was asked |
wg-upload | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s | upload, 45 s | connect | VERIFIED — TESTED SUCCESSFULLY the transfers came through the tunnel (the stress server saw only the phone's tunnel address) up 77.92 Mbit/s the server had a handshake with the peer ios1 7 s before it was asked | VERIFIED — TESTED SUCCESSFULLY transfer 14.0 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer android1 13 s before it was asked |
wg-full-duplex | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s | download and upload at once, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY down 158.8 / up 39.18 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer ios1 7 s before it was asked | VERIFIED — TESTED SUCCESSFULLY transfer 10.5 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer android1 13 s before it was asked |
wg-many-connections | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s | 16 downloads at once, 45 s | connect | VERIFIED — TESTED SUCCESSFULLY 205.46 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer ios1 7 s before it was asked | VERIFIED — TESTED SUCCESSFULLY transfer 26.1 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer android1 13 s before it was asked |
wg-udp-probe | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s | download, 15 s, and a DNS query over UDP | connect | VERIFIED — TESTED SUCCESSFULLY 184.19 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer ios1 7 s before it was asked the UDP DNS query was answered, and saw the server's address | VERIFIED — TESTED SUCCESSFULLY transfer 3.9 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer android1 16 s before it was asked the UDP DNS query was answered, and saw the server's address |
The configuration
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
wg-no-psk | a file and peer without a preshared key | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 190.74 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer nopsk 7 s before it was asked | VERIFIED — TESTED SUCCESSFULLY transfer 4.9 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer nopsk 13 s before it was asked |
wg-no-keepalive | the phone's file without PersistentKeepalive | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 194.52 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer ios1 7 s before it was asked | VERIFIED — TESTED SUCCESSFULLY transfer 3.8 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer android1 12 s before it was asked |
wg-mtu-1280 | the phone's file with MTU = 1280 | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 183.44 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer ios1 7 s before it was asked | VERIFIED — TESTED SUCCESSFULLY transfer 3.8 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer android1 13 s before it was asked |
wg-endpoint-ip | the phone's file with the server's address as Endpoint | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server had a handshake with the peer ios1 1 s before it was asked held for 6 s | VERIFIED — TESTED SUCCESSFULLY the server had a handshake with the peer android1 4 s before it was asked held for 6 s |
wg-split-tunnel | the phone's file with AllowedIPs = 10.66.66.0/24 | download, 15 s, and a DNS query over UDP | connect | VERIFIED — TESTED SUCCESSFULLY 194.05 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer ios1 8 s before it was asked the UDP DNS query was answered, and saw the phone's own network | VERIFIED — TESTED SUCCESSFULLY the server had a handshake with the peer android1 18 s before it was asked the UDP DNS query was answered, and saw the phone's own network the server's tunnel address answered a ping: 3 packets transmitted, 3 received, 0% packet loss, time 2005ms |
wg-manual-configuration | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the same values entered under Manual Configuration instead of a file | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server had a handshake with the peer ios1 1 s before it was asked held for 6 s | VERIFIED — TESTED SUCCESSFULLY the server had a handshake with the peer android1 4 s before it was asked held for 6 s |
Server and Port
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
wg-port-field-overrides-profile | the phone's file with Endpoint port 51829 (nothing listens); Port 51821 | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server had a handshake with the peer ios1 1 s before it was asked held for 6 s | VERIFIED — TESTED SUCCESSFULLY the server had a handshake with the peer android1 3 s before it was asked held for 6 s |
wg-server-field-overrides-profile | the phone's file with an Endpoint name that does not exist; Server: the server's name | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server had a handshake with the peer ios1 1 s before it was asked held for 6 s | VERIFIED — TESTED SUCCESSFULLY the server had a handshake with the peer android1 2 s before it was asked held for 6 s |
Refusals and damaged files
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
wg-wrong-server-key | the phone's file with a server public key of nobody | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 11.1 s The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed. | VERIFIED — TESTED SUCCESSFULLY The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed. |
wg-unknown-client-key | the phone's file with a private key the server does not have | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 11.1 s The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed. | VERIFIED — TESTED SUCCESSFULLY The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed. |
wg-wrong-psk | a file whose preshared key is not the server's for its peer | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 11.1 s The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed. | VERIFIED — TESTED SUCCESSFULLY The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed. |
wg-closed-port | the phone's file with Endpoint port 51829 (nothing listens) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 11.2 s The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51829 may be closed. | VERIFIED — TESTED SUCCESSFULLY The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51829 may be closed. |
wg-unknown-host | the phone's file with an Endpoint name that does not exist | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 0.4 s The WireGuard endpoint no-such-host.srp.invalid could not be resolved. | VERIFIED — TESTED SUCCESSFULLY The WireGuard endpoint no-such-host.srp.invalid could not be resolved. |
wg-bad-key | the phone's file with a damaged private key | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 0.6 s Invalid WireGuard config: a key is not valid base64 (32 bytes). | VERIFIED — TESTED SUCCESSFULLY Invalid WireGuard config: a key is not valid base64 (32 bytes). |
wg-bad-preshared-key | the phone's file with a damaged preshared key | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 0.4 s Invalid WireGuard config: the PresharedKey is not valid base64 (32 bytes). | VERIFIED — TESTED SUCCESSFULLY Invalid WireGuard config: the PresharedKey is not valid base64 (32 bytes). |
wg-retry-before-connect | the phone's file with Endpoint port 51829 (nothing listens); Port 51829; Retry Times 2 | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 31.3 s Could not connect after 3 attempts. (The server did not answer the WireGuard handshake.) | VERIFIED — TESTED SUCCESSFULLY Could not connect after 3 attempts. (The server did not answer the WireGuard handshake.) |
wg-no-address | the phone's file without Address | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 0.4 s Invalid WireGuard config: The config has no [Interface] Address. | VERIFIED — TESTED SUCCESSFULLY Invalid WireGuard config: The config has no [Interface] Address. |
wg-garbage-config | a file with [Interface] and [Peer] but no values | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 0.5 s Invalid WireGuard config: The config has no [Interface] PrivateKey. | VERIFIED — TESTED SUCCESSFULLY Invalid WireGuard config: The config has no [Interface] PrivateKey. |
Log levels
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
wg-log-normal | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; Log Level Normal | download, 40 s | connect | VERIFIED — TESTED SUCCESSFULLY 198.72 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) in the log: the session line not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key, the 30-second handshake and byte line | VERIFIED — TESTED SUCCESSFULLY transfer 3.8 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) held for 40 s in the log: the session line not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key, the 30-second handshake and byte line |
wg-log-expert | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; Log Level Expert | download, 40 s | connect | VERIFIED — TESTED SUCCESSFULLY 208.41 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) in the log: the session line, the 30-second handshake and byte line not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key | VERIFIED — TESTED SUCCESSFULLY transfer 3.7 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) held for 40 s in the log: the session line, the 30-second handshake and byte line not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key |
wg-log-debug | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; Log Level Debug | download, 4 s | connect | VERIFIED — TESTED SUCCESSFULLY 148.42 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) in the log: the session line, WireGuard's own lines not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key | VERIFIED — TESTED SUCCESSFULLY transfer 3.9 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) in the log: the session line, WireGuard's own lines not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key |
wg-release-log-normal | a file of the server; Log Level Normal | download, 40 s | connect | VERIFIED — TESTED SUCCESSFULLY 207.37 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) Release build in the log: the session line not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key, the 30-second handshake and byte line | NOT VERIFIED |
wg-release-log-expert | a file of the server; Log Level Expert | download, 40 s | connect | VERIFIED — TESTED SUCCESSFULLY 199.84 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) Release build in the log: the session line, the 30-second handshake and byte line not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key | NOT VERIFIED |
wg-release-log-debug | a file of the server; Log Level Debug | download, 4 s | connect | VERIFIED — TESTED SUCCESSFULLY 143.04 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) Release build in the log: the session line, WireGuard's own lines not in the log: a private key line, a preshared key line, the engine's private key, the engine's preshared key | NOT VERIFIED |
wg-release-download | a file of the server | download, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY 198.21 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) Release build the server had a handshake with the peer iosrel 6 s before it was asked | NOT VERIFIED |
wg-release-wrong-server-key | a file of the server; Log Level Expert | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Release build ended after 11.1 s The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed. | NOT VERIFIED |
Sleep, a server that goes away, network changes and Retry Times
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
wg-life-sleep-modes | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; On Sleep Stay, Pause and Off, and Off with Auto Reconnect off | connect only | connect | VERIFIED — TESTED SUCCESSFULLY On Sleep Stay, Auto Reconnect on: connected again after 3.4 s On Sleep Pause, Auto Reconnect off: connected again after 3.2 s On Sleep Off, Auto Reconnect on: connected again after 3.3 s On Sleep Off, Auto Reconnect off: ended after 3.4 s with: The connection was closed while the device slept. | VERIFIED — TESTED SUCCESSFULLY stayed connected through 10 s of sleep; transfer after wake passed paused at sleep, connected again at wake; transfer passed closed at sleep, connected again at wake; transfer passed ended at wake: The connection was closed while the device slept. |
wg-life-server-restart | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the server's WireGuard restarts (wg-quick); Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 17.0 s | VERIFIED — TESTED SUCCESSFULLY traffic passed again 17.3 s after the restart; transfer passed |
wg-life-outage-reconnect | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the server's WireGuard stops for 8 s; Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 16.2 s | VERIFIED — TESTED SUCCESSFULLY traffic passed again 25.4 s after the server stopped; transfer passed |
wg-life-dead-path-reconnects | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; every packet of the session dropped for 45 s; Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 48.1 s | VERIFIED — TESTED SUCCESSFULLY noticed the dead path after 33.0 s, connected again 46.6 s after the drop began; transfer passed |
wg-life-server-down-no-reconnect | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the server's WireGuard stops for 150 s; Auto Reconnect off | connect only | connect | VERIFIED — TESTED SUCCESSFULLY ended after 35.1 s with: The server stopped answering: nothing came back for 30 seconds (auto reconnect is off). | VERIFIED — TESTED SUCCESSFULLY ended 37.7 s after the server stopped with: The server stopped answering: nothing came back for 30 seconds (auto reconnect is off). |
wg-life-retry-exhausted | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the server's WireGuard stops for 120 s; Auto Reconnect on; Retry Times 2 | connect only | connect | VERIFIED — TESTED SUCCESSFULLY ended after 55.3 s with: Could not reconnect after 2 attempts. (The server did not answer the WireGuard handshake.) | VERIFIED — TESTED SUCCESSFULLY ended 58.2 s after the server stopped with: Could not reconnect after 2 attempts. (The server did not answer the WireGuard handshake.) |
wg-life-path-switch | the phone's file: all IPv4 traffic, preshared key, keepalive 25 s; the connection moved to the current network | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 0.3 s | VERIFIED — TESTED SUCCESSFULLY followed the network to mobile data and back to Wi-Fi (2 changes); on mobile data 5 of 5 pings to the server's tunnel address were answered; transfer passed |
The server as the guide sets it up
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
wg-guide-udp | the guide's phone1.conf | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 197.29 Mbit/s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer phone1 26 s before it was asked | VERIFIED — TESTED SUCCESSFULLY transfer 3.9 s the transfers came through the tunnel (the stress server saw only the phone's tunnel address) the server had a handshake with the peer phone1 20 s before it was asked |
wg-guide-removed | the guide's phone2.conf, phone2 removed as part 5 says | connect only | refused | VERIFIED — TESTED SUCCESSFULLY ended after 11.1 s The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed. | VERIFIED — TESTED SUCCESSFULLY The server did not answer the WireGuard handshake: the server's public key or the preshared key may not match, the server may not have this profile's public key as a peer, or UDP port 51821 may be closed. |