VLESS (no outer layer) (additional-vless-none.json)

There is no outer layer: the application protocol goes over the network as it is.

VERIFIED — TESTED SUCCESSFULLY  Tested on 9 November 2026 on the current app build against WaterWall 1.5.42, the official release, unchanged.

Result

OutcomePassed: every check succeeded.
Test length93 seconds
Downloaded1,980 MB (171 Mbit/s on average)
Uploaded1,275 MB (110 Mbit/s on average)
Transfers118 downloads and 76 uploads of 16 MiB; 8/8 streams finished at the end
Errorsnone
Timeouts0
Through the tunnelYes: 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 tunnelPing: 259 ms; Ping: 136 ms
UDPnot-run: This run measured TCP only

Test setup

PhoneiPhone 12 with iOS 27.2 (build 24B119), on Wi-Fi
AppSRP VPN Connect 1.2.0 (build 41), a Release build of commit e44cf11d, 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 machineUbuntu 24.04.5 LTS, VMware virtual machine with 2 vCPUs and 2 GB RAM
Server programOur permanent waterwall.service: the official WaterWall 1.5.42 release program, unchanged, installed as described in Installation, with /etc/waterwall/core.json
Server DNS lookups5 tries, WaterWall 1.5.42's default; /etc/waterwall/core.json does not set it
Server portThe configuration's own port, open to the internet
CertificateLet's Encrypt ECDSA certificate for <SERVER_HOST>
TrafficAn 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
NetworkOur office broadband line, over the public internet
iPhone 12 with SRP VPN Connect
      |
      |  Wi-Fi, office broadband, internet
      v
<SERVER_HOST>
  waterwall.service, the configuration's port
      |
      |  inside the same machine
      v
  HTTPS test server, port 28483            download file and upload checker

Server configuration

This is the configuration file from /etc/waterwall/configs/ on our server, loaded by waterwall.service, exactly as it ran. Only the server name, the UUID and the passwords are replaced with placeholders.

{
  "name": "additional-vless-none",
  "author": "SRP",
  "config-version": 1,
  "core-minimum-version": 0,
  "nodes": [
    {
      "name": "public-in",
      "type": "TcpListener",
      "settings": {
        "address": "0.0.0.0",
        "port": 18461,
        "nodelay": true,
        "initial-idle-timeout-ms": 15000,
        "active-idle-timeout-ms": 300000
      },
      "next": "vless"
    },
    {
      "name": "vless",
      "type": "VlessServer",
      "settings": {
        "uuid": "<UUID>",
        "connect": true,
        "udp": true,
        "verbose": true
      },
      "next": "outbound"
    },
    {
      "name": "outbound",
      "type": "TcpUdpConnector",
      "settings": {
        "address": "dest_context->address",
        "port": "dest_context->port",
        "nodelay": true
      }
    }
  ]
}

App settings

On the WaterWall configuration screen:

RowValue
ModeChain
InputConnections
ApplicationVLESS
MUXOff
ObfuscatorOff
HTTPOff
BGP4 FramingOff
OuterNone
CarrierTCP

In the profile editor:

Server<SERVER_HOST>, the server's domain name
PortThe listener port in the server file
SNI (optional)Empty, so the app sends the Server field (<SERVER_HOST>)
TLS Server VerificationOn
UUID or PasswordThe value from the server file
Reality PasswordThe value from the server file, for Reality
Auto ReconnectOff, so that a reconnect cannot hide a failure
On SleepStay
Log LevelNormal
Remote DNS (Fake IP)On
Direct LAN RoutingOn

How it was tested

  1. 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.
  2. The test connected the VPN and waited until iOS reported it connected.
  3. It ran the app's own HTTPS check through the tunnel: a request to https://gstatic.com/generate_204, which must answer 204.
  4. 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.
  5. 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

Evidence

Test caseprod-additional-vless-none
Why it was selectedProduction configuration additional-vless-none.json
Run2026-11-09T23:49:12Z to 2026-11-10T01:02:46Z (UTC)
Case log times2026-11-10 03:24:32 to 2026-11-10 03:26:09 (phone time, UTC+3)
App sourcecommit e44cf11d
Server programWaterWall 1.5.42, the official release, unchanged, SHA-256 38631081bd10347d…
Evidence filewaterwall-production-20261109T2349Z.json