VLESS + TLS with GeoIP direct routing for IR, TR and the DNS resolver Through the VPN
The DNS resolver looks up the name of each connection on the phone before routing. Through the VPN asks the listed DNS server through the VPN, so our DNS test server must hear the questions from the WaterWall server. GeoIP routing for the chosen countries stays on, and the downloads from our server, which is in Turkey (TR), must go straight from the phone.
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 | 93 seconds |
| Downloaded | 1,996 MB (172 Mbit/s on average) |
| Transfers | 119 downloads of 16 MiB; 4/4 streams finished at the end |
| Errors | none |
| Timeouts | 0 |
| GeoIP routing | passed: expected straight from the phone; the reference server saw 119 downloads from the phone's own address and 0 through WaterWall |
| DNS questions | passed: our DNS test server got 12, 0 from the phone's network and 12 from the WaterWall server; the test site's name was among them |
| HTTPS check through the tunnel | Ping: 196 ms; Ping: 135 ms |
| UDP | passed: 900 datagrams sent and 900 echoed back in 91 seconds; round trip 23 ms on average, 128 ms at most |
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 |
| UDP echo | A UDP echo server on the same machine, port 28481. The GeoIP case, whose UDP leaves outside the tunnel, used the test harness's own echo on port 28482 instead, opened in the firewall only for our office address while the case ran |
| DNS test server | A DNS forwarder on the same machine, UDP port 28453, that answers each question by asking 8.8.8.8 and logs the address each question came from. The profile's DNS Servers row named it; it was opened in the firewall only for our office address while the cases ran |
| GeoIP reference | An HTTPS server on the same machine, port 28480, that logs the address each download comes from |
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
UDP echo server, port 28481 UDP check
HTTPS reference server, port 28480 GeoIP case
DNS test server, UDP port 28453 where the resolver's questions come from
With GeoIP direct routing, downloads from the reference server go straight from the phone
to port 28480, without WaterWall.
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": "geoip-resolver-chain-peer",
"nodes": [
{
"name": "listener",
"type": "TcpListener",
"settings": {
"address": "<SERVER_IP>",
"port": 4097
},
"next": "tls"
},
{
"name": "tls",
"type": "TlsServer",
"settings": {
"cert-file": "/tmp/srp-device-matrix/cert.pem",
"key-file": "/tmp/srp-device-matrix/key.pem",
"verbose": true,
"select-alpns": [
"http/1.1"
]
},
"next": "vless"
},
{
"name": "vless",
"type": "VlessServer",
"settings": {
"uuid": "<UUID>",
"verbose": true
},
"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 | Chain |
| Input | Connections |
| Application | VLESS |
| MUX | Off |
| Obfuscator | Off |
| HTTP | Off |
| BGP4 Framing | Off |
| Outer | TLS |
| Carrier | TCP |
| GeoIP Routing | On |
| Countries | IR, TR |
| Resolver | Through the VPN |
| Addresses | Default (IPv4 First) |
| DNS Servers | <SERVER_IP>:28453 |
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": "VLESS + TLS",
"nodes": [
{
"settings": {},
"name": "ne",
"type": "NEPacketDevice",
"next": "ptc"
},
{
"settings": {
"max-total-pending-bytes": 16777216,
"mtu": 1420,
"fake-dns": {
"address": "198.18.0.2",
"netmask": "255.192.0.0",
"enabled": true,
"port": 53,
"ttl": 60,
"cache-size": 10000,
"network": "100.64.0.0"
},
"max-pending-bytes": 65536
},
"name": "ptc",
"type": "PacketsToConnection",
"next": "resolver"
},
{
"settings": {
"port": "dest_context->port",
"address": "dest_context->address",
"protocol": "dest_context->protocol",
"uuid": "<UUID>"
},
"name": "vless",
"type": "VlessClient",
"next": "tls"
},
{
"settings": {
"geoip-db-path": "<LOCAL_PATH> VPN Connect Tests/app-ww1542/WaterWall/GeoIP/GeoLite2-Country.mmdb",
"rules": [
{
"target": "vless",
"resolver-dns": true
},
{
"target": "direct-local",
"destination-ip": [
"geoip:ir"
]
},
{
"target": "direct-local",
"destination-ip": [
"geoip:tr"
]
}
]
},
"name": "router",
"type": "Router",
"next": "vless"
},
{
"settings": {
"mode": "chain",
"servers": [
"<SERVER_IP>:28453"
]
},
"name": "resolver",
"type": "DomainResolver",
"next": "router"
},
{
"name": "direct-local",
"type": "TcpUdpConnector",
"settings": {
"port": "dest_context->port",
"dns-behaviour": {
"resolve": true,
"strategy": "prefer-ipv4"
},
"nodelay": true,
"address": "dest_context->address"
}
},
{
"settings": {
"sni": "localhost",
"verify": false,
"alpns": [
"http/1.1"
]
},
"name": "tls",
"type": "TlsClient",
"next": "connector"
},
{
"name": "connector",
"type": "TcpUdpConnector",
"settings": {
"address": "127.0.0.1",
"nodelay": true,
"port": 4097
}
}
]
}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 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 of 16 MiB at the same time, over and over. They used the test server's name, so each new connection made the DNS resolver look it up. The GeoIP case downloaded from the reference server on port 28480; the others from the HTTPS test server.
- It then sent small UDP datagrams to the echo server for 90 seconds, at least 10 a second, and waited for each one to come back.
- It ran the HTTPS check again and disconnected.
- The harness then read the DNS test server's log for the time of the case: Native must leave no question there, Direct must leave questions from our office address only, and Through the VPN questions from the WaterWall server only. For Direct and Through the VPN, the test server's name must be among them. For the GeoIP case it also read the reference server's log, as in the GeoIP routing cases.
A case passes only if the VPN stayed connected, the downloads ran the full 90 seconds with no errors or timeouts, both HTTPS checks succeeded, every UDP datagram came back, the DNS questions came from where the resolver's setting sends them, and, for the GeoIP case, every download went straight from the phone. The cases without GeoIP were also checked to arrive through the tunnel.
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.
- The DNS check counts where the questions came from; it does not check the answers, which 8.8.8.8 gave.
- The UDP check sends small datagrams and waits for each echo; it shows that UDP works through the chain, not how fast it is.
- Each case ran once, with one phone on one network.
Evidence
| Test case | geoip-resolver-chain |
|---|---|
| Run | 2026-11-10T10:51:39Z to 2026-11-10T10:55:24Z (UTC) |
| Case log times | 2026-11-10 13:53:28 to 2026-11-10 13:55:04 (phone time, UTC+3) |
| App source | commit e69cb668 |
| Server program | WaterWall 1.5.42, the official release, unchanged, SHA-256 38631081bd10347d… |
| Evidence file | waterwall-dns-resolver-20261110T1051Z.json |