WireGuard mode
WireGuard mode connects the app's WireGuard client to a WireGuard server run by WaterWall.
VERIFIED — TESTED SUCCESSFULLY Tested on 10 November 2026 on the current app build against WaterWall 1.5.42, the official release, unchanged.
Result
| Outcome | Passed: every check succeeded. |
|---|---|
| Test length | 113 seconds |
| Downloaded | 688 MB (49 Mbit/s on average) |
| Uploaded | 403 MB (29 Mbit/s on average) |
| Transfers | 41 downloads and 24 uploads of 16 MiB; 8/8 streams finished at the end |
| Errors | none |
| Timeouts | 0 |
| Through the tunnel | Yes: the HTTPS test server saw these transfers come from <SERVER_IP>, and it would have seen the phone's own network if they had left outside the tunnel |
| HTTPS check through the tunnel | Ping: 382 ms; Ping: 186 ms |
| UDP | not-applicable: The full-duplex test exercises TCP only |
Test setup
| Phone | iPhone 12 with iOS 27.2 (build 24B119), on Wi-Fi |
|---|---|
| App | SRP VPN Connect 1.2.0 (build 41), a Release build of commit e69cb668, installed by Xcode for the test. TestFlight build 41 is commit e44cf11d, with the same app code: the commits after it change only the tests and the change log |
| Server machine | Ubuntu 24.04.5 LTS, VMware virtual machine with 2 vCPUs and 2 GB RAM |
| Server program | The official WaterWall 1.5.42 release program, unchanged, the same program as our permanent test server, run as a separate test copy for each case |
| Server DNS lookups | 5 tries, WaterWall 1.5.42's default; the test copy's core.json does not set it |
| Server port | 4097, opened in the firewall only for our office address while the case ran |
| Traffic | An HTTPS test server on the same machine, port 28483, that serves a 16 MiB file and checks each upload. On Raw IPv4 and native WireGuard chains the phone reaches it at the server's private address 10.44.0.1, because iOS sends traffic for the server's own public address outside the tunnel; the test then trusts its certificate by comparing it with a copy, since the name in it is not that address |
| Network | Our office broadband line, over the public internet |
iPhone 12 with SRP VPN Connect
|
| Wi-Fi, office broadband, internet
v
Test server <SERVER_IP>
WaterWall test copy, port 4097 the chain under test
|
| inside the same machine
v
HTTPS test server, port 28483 download file and upload checker
Server configuration
The test harness wrote this file for the case and started our WaterWall program with it. It is shown as it ran; only the server address, the UUID and the passwords are replaced with placeholders. The certificate files are a self-signed test certificate made for the run. On your own server, use your own port, certificate and secrets, as described in Installation.
{
"name": "wireguard-native-peer",
"nodes": [
{
"name": "udp",
"type": "UdpStatelessSocket",
"settings": {
"listen-address": "<SERVER_IP>",
"source-ip": "<SERVER_IP>",
"listen-port": 4097,
"address": "<SERVER_IP>"
},
"next": "wg"
},
{
"name": "wg",
"type": "WireGuardDevice",
"settings": {
"privatekey": "<PRIVATEKEY>",
"peers": [
{
"publickey": "GhU3dznGB+Kw0aVcWpVaMutlC2bfd/Uo2+00kStJeX0=",
"allowedips": "10.99.0.2/32",
"endpoint": "127.0.0.1:9",
"persistentkeepalive": 0
},
{
"publickey": "EekArnXEwguWdWQQ9HSMgqKTnEl9cbr5gxdDpAbvZyE=",
"allowedips": "10.99.0.3/32",
"endpoint": "127.0.0.1:9",
"persistentkeepalive": 0
}
]
},
"next": "ptc"
},
{
"name": "ptc",
"type": "PacketsToConnection",
"settings": {
"mtu": 1420,
"max-pending-bytes": 65536,
"max-total-pending-bytes": 4194304
},
"next": "router"
},
{
"name": "router",
"type": "Router",
"settings": {},
"next": "out"
},
{
"name": "out",
"type": "TcpUdpConnector",
"settings": {
"address": "dest_context->address",
"port": "dest_context->port",
"dns-behaviour": {
"resolve": true,
"strategy": "prefer-ipv4"
},
"nodelay": true
}
}
]
}
The test copy's core.json
{
"misc": {
"workers": 1,
"ram-profile": "minimal",
"splice": false,
"try-enabling-bbr": false,
"tcp-tune": false
},
"configs": [
"/tmp/srp-device-matrix/peer.json"
]
}App settings
On the WaterWall configuration screen:
| Row | Value |
|---|---|
| Mode | WireGuard |
In the profile editor:
| Server | <SERVER_IP>, the test server's address |
|---|---|
| Port | 4097 |
| SNI (optional) | localhost, for chains with TLS, Reality or QUIC |
| TLS Server Verification | Off, because the test certificate is self-signed |
| UUID or Password | <UUID>, a test value |
| Reality or AEAD Password | <OUTER_PASSWORD>, a test value, when the chain uses one |
| Auto Reconnect | Off, so that a reconnect cannot hide a failure |
| On Sleep | Stay |
| Log Level | Normal |
| Remote DNS (Fake IP) | On |
| Direct LAN Routing | On |
The client chain the app built (for reference)
{
"name": "wireguard",
"nodes": [
{
"next": "wg",
"name": "udp",
"settings": {
"listen-port": 0,
"listen-address": "0.0.0.0",
"verbose": true
},
"type": "UdpStatelessSocket"
},
{
"settings": {
"peers": [
{
"persistentkeepalive": 0,
"endpoint": "127.0.0.1:4097",
"publickey": "GbU7M7Tlrg9l2NFr0kkoBkfb0QUSEBZCgP+a2VcUBHk=",
"allowedips": "0.0.0.0/0"
}
],
"privatekey": "<PRIVATEKEY>"
},
"name": "wg",
"type": "WireGuardDevice",
"next": "ne"
},
{
"name": "ne",
"type": "NEPacketDevice",
"settings": {}
}
]
}How it was tested
- Xcode installed the app's test build on the phone, and the test created the profile shown above in memory. It was not added to the app's profile list.
- The test connected the VPN and waited until iOS reported it connected.
- It ran the app's own HTTPS check through the tunnel: a request to
https://gstatic.com/generate_204, which must answer 204. - For at least 90 seconds it ran 4 downloads and 4 uploads at the same time, over and over. Each download fetched a 16 MiB file from the HTTPS test server. Each upload sent 16 MiB, and the server answered with the size and SHA-256 it received, which the test compared with what it sent.
- It ran the HTTPS check again and disconnected.
A case passes only if the VPN stayed connected, the test ran the full 90 seconds, every transfer finished, there were no errors and no timeouts, data moved in both directions, both HTTPS checks succeeded, and the HTTPS test server saw the transfers come through the tunnel (Direct mode and the GeoIP cases leave outside it by design and are not checked).
Gaps and limits
- TLS Server Verification was off and the SNI was localhost, because the test server used a self-signed certificate made for the run.
- For Reality, the cover site was a second TLS server on the test machine itself, not a public website.
- The test measured TCP traffic. The UDP row in the result says whether UDP was tested; in this run it was not.
- Each case ran once, for about 90 seconds, with one phone on one network.
- The test copy of WaterWall used the harness's own small core.json with one worker, not our production core.json.
Evidence
| Test case | wireguard-native |
|---|---|
| Why it was selected | advanced/special |
| Run | 2026-11-10T11:39:10Z to 2026-11-10T15:17:28Z (UTC) |
| Case log times | 2026-11-10 17:18:28 to 2026-11-10 17:20:27 (phone time, UTC+3) |
| App source | commit e69cb668 |
| Server program | WaterWall 1.5.42, the official release, unchanged, SHA-256 38631081bd10347d… |
| Evidence file | waterwall-matrix-20261110T1139Z.json |