Test Results
Every SSL VPN case we ran on 7 November 2026, with its result on an iPhone and on an Android phone: 49 of 49 cases passed on the iPhone and 48 of 48 on Android.
The phones were an iPhone 12 with iOS 27.2 and a Samsung Galaxy A55 with Android 17, with the app built from commit 23ec28b1, TestFlight build 37's code, as a Debug build on the iPhone, and with the code of commit 4aae66d7 as a debug APK on Android; the iPhone's rows of the log cases, ocv-wrong-password and ocv-pass-download come from a Release build of 23ec28b1, the kind TestFlight ships; the ocv-path rows come from commit ec77a882, which adds Path, on both phones. The server was ocserv 1.2.4 on Ubuntu 24.04, set up as ocserv (AnyConnect server) describes, with the profiles' Server Type AnyConnect unless a row says otherwise.
- 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 on the internet. That server logged where each request came from, and every case that moves traffic checked that it came from the VPN server's address, 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. On Android each transfer case moved two 16 MiB downloads, two 16 MiB uploads, or both, and the row shows how long that took.
- The server's view. While a case ran,
occtl show userread the phone's session on the server: its TLS version, and whether the VPN's packets went over DTLS (and which kind) or over TLS alone. Where a row shows how the ClientHello was sent, the server recorded the sizes of the phone's first TCP segments to port 443. - Server settings. A row that names a server setting changed that one setting in
ocserv.conffor the case, restarted ocserv, and put the setting back afterwards. Our server ran withmax-ban-score = 0for every other case, so that the cases with wrong passwords would not block our address. - Path. The cases named
ocv-path-…turned on ocserv'scamouflagewith a secret for the case and put?and the secret, or a wrong one, in the profile's Path. They ran on a later commit than the other cases, the one that adds Path, on both phones. - Refusals. A case whose expected result is refused passed when the app did not connect and ended with the message shown in its row, or with the certificate warning declined.
- Log levels. The cases named
ocv-log-…read the connection log back and checked its lines: Normal must show the connect and session lines and none of OpenConnect's progress lines; Expert adds those and the routes; Debug adds the server's headers, with the server's cookies written as<elided>; and no level may show a TLS or DTLS secret.ocv-wrong-passwordalso checked that the log names the reason the app closed the connection. On the iPhone these four cases ran on a Release build, the kind TestFlight ships, as well as on the Debug build. - Lifecycle. The cases named
ocv-life-…checked On Sleep; a session the server ended (occtl disconnect user); a TCP connection the server reset while it kept the session (ss -K); a switch to a new network path; ocserv stopped until Retry Times ran out; and ocserv stopped for 8 seconds and started again. On Android the screen was really turned off and Wi-Fi was really switched off and on; on the iPhone the On Sleep case tells the tunnel that the phone slept, and the network case makes the tunnel move its session as it does when Wi-Fi appears.
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
- F5 BIG-IP and Palo Alto GlobalProtect servers. We had none; those Server Types were only tried against our AnyConnect server, which refuses them.
- Cisco's own AnyConnect servers. Every AnyConnect case ran against ocserv.
- Moving between Wi-Fi and cellular on the iPhone. The iPhone's network case makes the tunnel move its session 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 ranges the server keeps outside it (
no-route).
Transfers over DTLS and TLS
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ocv-pass-download | defaults | download, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY 202.04 Mbit/s Release build TLS 1.2 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 4.9 s TLS 1.2 data over DTLS 1.2 (PSK) |
ocv-pass-full-duplex | defaults | download and upload at once, 90 s | connect | VERIFIED — TESTED SUCCESSFULLY down 167.86 / up 27.49 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 10.5 s TLS 1.2 data over DTLS 1.2 (PSK) |
ocv-pass-upload | defaults | upload, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY down 0.0 / up 149.23 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 8.3 s TLS 1.2 data over DTLS 1.2 (PSK) |
ocv-tls-only-download | server: UDP 443 blocked (no DTLS) | download, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY 173.94 Mbit/s TLS 1.2 data over TLS (no DTLS) | VERIFIED — TESTED SUCCESSFULLY transfer 5.8 s TLS 1.2 data over TLS (no DTLS) |
ocv-tls-only-full-duplex | server: UDP 443 blocked (no DTLS) | download and upload at once, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY down 48.61 / up 131.03 Mbit/s TLS 1.2 data over TLS (no DTLS) | VERIFIED — TESTED SUCCESSFULLY transfer 12.4 s TLS 1.2 data over TLS (no DTLS) |
Logins
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ocv-cert-download | Method Certificate | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 193.77 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) logged in as the certificate's user | VERIFIED — TESTED SUCCESSFULLY transfer 4.9 s TLS 1.2 data over DTLS 1.2 (PSK) logged in as the certificate's user |
ocv-cert-other-username | Method Certificate; Username of another user | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 182.03 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) logged in as the certificate's user | VERIFIED — TESTED SUCCESSFULLY transfer 4.9 s TLS 1.2 data over DTLS 1.2 (PSK) logged in as the certificate's user |
ocv-wrong-password | wrong password | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Release build in the log: the connect line, the reason the app closed the connection not in the log: TLS secrets, the DTLS secret Authentication failed. Check the username and password. | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the reason the app closed the connection not in the log: TLS secrets, the DTLS secret Authentication failed. Check the username and password. |
ocv-wrong-user | a user the server does not have | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username and password. | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username and password. |
ocv-cert-rogue-ca | Method Certificate (a certificate from another authority) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The TLS handshake with the server failed. The server may refuse the client certificate, or block this address for a while after wrong passwords. | VERIFIED — TESTED SUCCESSFULLY The TLS handshake with the server failed. The server may refuse the client certificate, or block this address for a while after wrong passwords. |
ocv-cert-missing | Method Certificate without a certificate | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username and password. | VERIFIED — TESTED SUCCESSFULLY The client certificate could not be read. Re-import it in the profile. |
Certificate check, names and ports
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ocv-verify-ip-declined | Server is the server's IP address | connect only | refused | VERIFIED — TESTED SUCCESSFULLY the certificate warning was declined | VERIFIED — TESTED SUCCESSFULLY the certificate warning was declined |
ocv-verify-ip-accepted | Server is the server's IP address | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 190.47 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) the certificate warning was accepted | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s TLS 1.2 data over DTLS 1.2 (PSK) |
ocv-allow-untrusted-ip | Server is the server's IP address; TLS Server Verification off | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 193.12 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s TLS 1.2 data over DTLS 1.2 (PSK) |
ocv-port-8443 | Port 8443 (redirected to 443 on the server) | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 194.61 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 5.0 s TLS 1.2 data over DTLS 1.2 (PSK) |
ocv-port-closed | Port 4443 (nothing listens on it) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Cannot connect to the server on this port. Check the Server and Port fields and the network. | VERIFIED — TESTED SUCCESSFULLY Cannot connect to the server on this port. Check the Server and Port fields and the network. |
ocv-port-other-service | Port 22 (the server's SSH answers it) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server did not answer with TLS on this port. Check the Port field. | VERIFIED — TESTED SUCCESSFULLY The server did not answer with TLS on this port. Check the Port field. |
ocv-host-unknown | Server is a name that does not exist | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server name could not be found. Check the Server field. | VERIFIED — TESTED SUCCESSFULLY The server name could not be found. Check the Server field. |
Server Type
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ocv-type-f5-on-anyconnect | Server Type F5 BIG-IP (the server speaks AnyConnect) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server did not answer as an F5 BIG-IP server. Check the Server Type and the Server field. | VERIFIED — TESTED SUCCESSFULLY The server did not answer as an F5 BIG-IP server. Check the Server Type and the Server field. |
ocv-type-gp-on-anyconnect | Server Type Palo Alto GP (the server speaks AnyConnect) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server did not answer as a GlobalProtect server. Check the Server Type and the Server field. | VERIFIED — TESTED SUCCESSFULLY The server did not answer as a GlobalProtect server. Check the Server Type and the Server field. |
Server settings
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ocv-split-group | a user of the split-tunnel group; Log Level Expert | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 188.33 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) routes ['TEST_SERVER_IP/255.255.255.255', '1.1.1.1/255.255.255.255', '8.8.8.8/255.255.255.255'] in the log: the routes line not in the log: a full-tunnel routes line, TLS secrets, the DTLS secret | VERIFIED — TESTED SUCCESSFULLY transfer 6.1 s TLS 1.2 data over DTLS 1.2 (PSK) routes ['TEST_SERVER_IP/255.255.255.255', '1.1.1.1/255.255.255.255', '8.8.8.8/255.255.255.255'] in the log: the routes line not in the log: a full-tunnel routes line, TLS secrets, the DTLS secret |
ocv-server-tls13 | server: TLS 1.3 allowed in tls-priorities | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 184.15 Mbit/s TLS 1.3 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 4.8 s TLS 1.3 data over DTLS 1.2 (PSK) |
ocv-server-dtls-no-psk | server: dtls-psk = false | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 194.58 Mbit/s TLS 1.2 data over DTLS 1.2 (ECDHE-RSA) | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s TLS 1.2 data over DTLS 1.2 (ECDHE-RSA) |
ocv-server-compression | server: compression = true | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 159.93 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s TLS 1.2 data over DTLS 1.2 (PSK) |
ocv-server-tls11-only | Port 4443; a server on another port that offers only TLS 1.1 | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server offers only TLS 1.1 or older; the app needs TLS 1.2 or later. | VERIFIED — TESTED SUCCESSFULLY The server offers only TLS 1.1 or older; the app needs TLS 1.2 or later. |
ocv-server-ban | server: max-ban-score = 1 | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The TLS handshake with the server failed. The server may refuse the client certificate, or block this address for a while after wrong passwords. | VERIFIED — TESTED SUCCESSFULLY The TLS handshake with the server failed. The server may refuse the client certificate, or block this address for a while after wrong passwords. |
ocv-server-camouflage | server: camouflage on, with a secret; Path empty | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server did not answer as an AnyConnect server. Check the Server Type and the Server field. | VERIFIED — TESTED SUCCESSFULLY The server did not answer as an AnyConnect server. Check the Server Type and the Server field. |
ocv-path-camouflage | server: camouflage on; Path ?secret | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 181.04 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 5.0 s TLS 1.2 data over DTLS 1.2 (PSK) |
ocv-path-camouflage-wrong-secret | server: camouflage on; Path with a wrong secret | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server did not answer as an AnyConnect server. Check the Server Type and the Server field. | VERIFIED — TESTED SUCCESSFULLY The server did not answer as an AnyConnect server. Check the Server Type and the Server field. |
ocv-path-camouflage-log | server: camouflage on; Path ?secret; the log checked for the secret; Log Level Debug | connect only | connect | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the Path's secret as its length not in the log: the Path's secret | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the Path's secret as its length not in the log: the Path's secret |
ocv-path-camouflage-reset-resume | server: camouflage on; Path ?secret; the server resets the TCP connection, Auto Reconnect on; Log Level Expert | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 5.3 s | VERIFIED — TESTED SUCCESSFULLY resumed the same session 0.2 s after the reset; transfer passed |
TLS Fragmentation
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ocv-frag-off-capture | TLS Server Verification off; TLS Fragmentation Off | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 185.29 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) ClientHello sent as 517 bytes | VERIFIED — TESTED SUCCESSFULLY transfer 5.9 s TLS 1.2 data over DTLS 1.2 (PSK) ClientHello sent as 1557 bytes |
ocv-frag-auto-capture | TLS Server Verification off; TLS Fragmentation Auto | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 188.82 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) ClientHello sent as 43 + 256 + 218 bytes | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s TLS 1.2 data over DTLS 1.2 (PSK) ClientHello sent as 43 + 256 + 256 + 256 + 256 + 256 + 234 bytes |
ocv-frag-manual-20-100-capture | TLS Server Verification off; TLS Fragmentation Manual 20/100 | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 177.93 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) ClientHello sent as 20 + 100 + 100 + 100 + 100 + 97 bytes | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s TLS 1.2 data over DTLS 1.2 (PSK) ClientHello of 1557 bytes; its first 720 bytes sent as 20 + 100 + 100 + 100 + 100 + 100 + 100 + 100 (the server recorded the first 8 pieces) |
ocv-frag-auto-verified | TLS Fragmentation Auto | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 183.86 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s TLS 1.2 data over DTLS 1.2 (PSK) |
ocv-frag-manual-verified | TLS Fragmentation Manual 20/100 | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 160.84 Mbit/s TLS 1.2 data over DTLS 1.2 (PSK) | VERIFIED — TESTED SUCCESSFULLY transfer 4.9 s TLS 1.2 data over DTLS 1.2 (PSK) |
Log levels
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ocv-log-normal | Log Level Normal | connect only | connect | VERIFIED — TESTED SUCCESSFULLY Release build in the log: the connect line, the session line not in the log: libopenconnect's progress lines, the routes line, the server's tunnel headers, TLS secrets, the DTLS secret | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the session line not in the log: libopenconnect's progress lines, the routes line, the server's tunnel headers, TLS secrets, the DTLS secret |
ocv-log-expert | Log Level Expert | connect only | connect | VERIFIED — TESTED SUCCESSFULLY Release build in the log: the connect line, libopenconnect's progress lines, the routes line not in the log: the server's tunnel headers, TLS secrets, the DTLS secret | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, libopenconnect's progress lines, the routes line not in the log: the server's tunnel headers, TLS secrets, the DTLS secret |
ocv-log-debug | Log Level Debug | connect only | connect | VERIFIED — TESTED SUCCESSFULLY Release build in the log: the connect line, libopenconnect's progress lines, the server's tunnel headers, the session cookie, hidden, the context cookie, hidden not in the log: TLS secrets, the DTLS secret | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, libopenconnect's progress lines, the server's tunnel headers, the session cookie, hidden, the context cookie, hidden not in the log: TLS secrets, the DTLS secret |
Sleep, lost connections, network switch and Retry Times
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ocv-retry-before-connect | server: ocserv stopped; Retry Times 2 | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Could not connect after 2 attempts. (Cannot connect to the server on this port. Check the Server and Port fields and the network.) | VERIFIED — TESTED SUCCESSFULLY Could not connect after 2 attempts. (Cannot connect to the server on this port. Check the Server and Port fields and the network.) |
ocv-life-sleep-modes | 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.2 s On Sleep Pause, Auto Reconnect off: connected again after 3.6 s On Sleep Off, Auto Reconnect on: connected again after 3.4 s On Sleep Off, Auto Reconnect off: ended after 3.5 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. |
ocv-life-server-ends-reconnect | Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 5.2 s | VERIFIED — TESTED SUCCESSFULLY connected again 2.8 s after the drop; transfer passed |
ocv-life-server-ends-no-reconnect | Auto Reconnect off | connect only | connect | VERIFIED — TESTED SUCCESSFULLY ended after 5.0 s with: The server ended the session (auto reconnect is off). | VERIFIED — TESTED SUCCESSFULLY ended with: The server ended the session (auto reconnect is off). |
ocv-life-reset-resume | Log Level Expert; Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 5.2 s | VERIFIED — TESTED SUCCESSFULLY resumed the same session 0.2 s after the reset; transfer passed |
ocv-life-reset-no-reconnect | Auto Reconnect off | connect only | connect | VERIFIED — TESTED SUCCESSFULLY ended after 5.0 s with: Connection lost (auto reconnect is off). | VERIFIED — TESTED SUCCESSFULLY ended with: Connection lost (auto reconnect is off). |
ocv-life-path-switch | Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY path-switch: connected again after 0.3 s | VERIFIED — TESTED SUCCESSFULLY moved to Wi-Fi again: resumed the same session, 1 login(s); transfer passed |
ocv-life-path-switch-no-reconnect | Auto Reconnect off | connect only | connect | VERIFIED — TESTED SUCCESSFULLY path-switch: connected again after 0.3 s | NOT VERIFIED |
ocv-life-retry-exhausted | Auto Reconnect on; Retry Times 2 | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server was stopped: ended after 5.0 s with: Could not reconnect after 2 attempts. | VERIFIED — TESTED SUCCESSFULLY ended with: Could not reconnect after 2 attempts. |
ocv-life-outage-reconnect | Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 15.2 s | VERIFIED — TESTED SUCCESSFULLY connected again 1.4 s after the server came back, after 4 attempts; transfer passed |