Test Results
Every SSH VPN case we ran on 7 and 8 November 2026, with its result on an iPhone and on an Android phone: 49 of 49 cases passed on the iPhone and 49 of 49 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 8b4eb1af, as a Debug build on the iPhone and a debug APK on Android; the rows of the ssh-life-… and ssh-guide-… cases on both phones, and Android's ssh-server-keepalive-idle row, ran on commit 3c4e4def, which follows it; the iPhone's rows of the log cases, ssh-wrong-password and ssh-pass-download come from a Release build of 8b4eb1af's code, the kind TestFlight ships. The server was OpenSSH 9.6 on Ubuntu 24.04, with hev-socks5-server 2.13.1 as the UDP relay, set up as OpenSSH server describes.
- 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 SSH 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, and
ssh-many-connectionsran 16 downloads at once. On Android each transfer case moved two 16 MiB downloads, two 16 MiB uploads, or both, andssh-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, over UDP through the tunnel, for the address the query came from. With UDP Relay on, the answer had to name the SSH server's address; with UDP Relay off, no answer could come.
- The server's view. Each case read the server's sshd log, which shows how the user logged in or why the login failed.
- Server settings. A row that names a server setting put that setting in a file of
/etc/ssh/sshd_config.d/for the case, reloaded sshd, and took it out afterwards. Rows that block a port did it with a firewall rule on the server, on its second SSH port 2222, so the test's own SSH session on port 22 kept working. - 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
ssh-log-…moved 10 seconds of downloads, read the connection log back and checked its lines: Normal must show the connect line, the server's host key, the login and the session line, and no transfer counters, connection lines or packet engine lines; Expert adds the transfer counters; Debug adds a line for each connection and, on the iPhone, the packet engine's own lines (Android does not keep them); and no level may show the password.ssh-wrong-passwordalso checked that the log names the reason the app closed the connection. On the iPhone the log cases,ssh-wrong-passwordandssh-pass-downloadalso ran on a Release build, the kind TestFlight ships; their rows show that run. - Lifecycle. The cases named
ssh-life-…checked On Sleep; a session the server ended (the user's sshd processes stopped); a TCP connection the server reset (ss -K); a dead network path (every packet of the session dropped, without a reset, until the app gave the session up and tried a new connection); a switch to a new network path; port 2222 refusing connections until Retry Times ran out; and port 2222 refusing connections for 8 seconds. 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 open a new 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
- Moving between Wi-Fi and cellular on the iPhone. The iPhone's network case makes the tunnel open a new 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.
- SSH servers other than OpenSSH, such as Dropbear.
- Logins with an SSH key. The app's SSH VPN profiles log in with a password.
- IPv6 inside the tunnel. The app sends only IPv4 through it.
Transfers and UDP
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ssh-pass-download | defaults | download, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY 62.01 Mbit/s Release build the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 6.2 s the server logged a password login |
ssh-pass-full-duplex | defaults | download and upload at once, 90 s | connect | VERIFIED — TESTED SUCCESSFULLY down 76.94 / up 44.77 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 9.3 s the server logged a password login |
ssh-pass-upload | defaults | upload, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY up 70.78 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 9.3 s the server logged a password login |
ssh-many-connections | defaults | 16 downloads at once, 45 s | connect | VERIFIED — TESTED SUCCESSFULLY 87.71 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 40.2 s the server logged a password login |
ssh-udp-download | UDP Relay on | download, 30 s, and a DNS query over UDP | connect | VERIFIED — TESTED SUCCESSFULLY 85.31 Mbit/s the server logged a password login the UDP DNS query was answered, and saw the server's address | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s the server logged a password login the UDP DNS query was answered, and saw the server's address |
ssh-udp-off-probe | defaults | download, 20 s, and a DNS query over UDP | connect | VERIFIED — TESTED SUCCESSFULLY 115.95 Mbit/s the server logged a password login the UDP DNS query got no answer | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s the server logged a password login the UDP DNS query got no answer |
ssh-udp-relay-stopped | UDP Relay on; server: the UDP relay stopped | connect only | refused | VERIFIED — TESTED SUCCESSFULLY the server logged a password login The UDP relay (HEV) is unavailable on the server. Turn UDP Relay off, or ask the administrator to install or start it. | VERIFIED — TESTED SUCCESSFULLY the server logged a password login The UDP relay (HEV) is unavailable on the server. Turn UDP Relay off, or ask the administrator to install or start it. |
ssh-udp-off-relay-stopped | server: the UDP relay stopped | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 105.59 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s the server logged a password login |
ssh-password-login-off | server: PasswordAuthentication no for the user | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server does not take a password for this user (it offers: publickey). | VERIFIED — TESTED SUCCESSFULLY The server does not take a password for this user (it offers: publickey). |
Logins
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ssh-wrong-password | wrong password | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Release build the server logged a wrong password in the log: the connect line, the reason the app closed the connection not in the log: the password Authentication failed. Check the username and password. | VERIFIED — TESTED SUCCESSFULLY the server logged a wrong password in the log: the connect line, the reason the app closed the connection not in the log: the password Authentication failed. Check the username and password. |
ssh-wrong-user | a user the server does not have | connect only | refused | VERIFIED — TESTED SUCCESSFULLY the server logged an unknown user Authentication failed. Check the username and password. | VERIFIED — TESTED SUCCESSFULLY the server logged an unknown user Authentication failed. Check the username and password. |
ssh-special-password | a user whose password has spaces, punctuation and letters outside ASCII | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 72.13 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s the server logged a password login |
ssh-password-login-off | server: PasswordAuthentication no for the user | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server does not take a password for this user (it offers: publickey). | VERIFIED — TESTED SUCCESSFULLY The server does not take a password for this user (it offers: publickey). |
ssh-kbd-interactive-only | server: PasswordAuthentication no and KbdInteractiveAuthentication yes for the user | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 88.5 Mbit/s the server logged a keyboard-interactive login | VERIFIED — TESTED SUCCESSFULLY transfer 6.1 s the server logged a keyboard-interactive login |
ssh-no-forwarding | a user the server does not let forward TCP (AllowTcpForwarding no) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY the server logged a password login The server does not let this user forward TCP connections (AllowTcpForwarding or PermitOpen on the server). | VERIFIED — TESTED SUCCESSFULLY the server logged a password login The server does not let this user forward TCP connections (AllowTcpForwarding or PermitOpen on the server). |
Host Key
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ssh-hostkey-ed25519 | Host Key: the fingerprint of the server's ED25519 key | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 127.07 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 8.3 s the server logged a password login |
ssh-hostkey-ecdsa-not-shown | Host Key: the fingerprint of the server's ECDSA key | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server's host key does not match Host Key. The server presented ED25519 SHA256:<SERVER_ED25519_KEY>. | VERIFIED — TESTED SUCCESSFULLY The server's host key does not match Host Key. The server presented ED25519 SHA256:<SERVER_ED25519_KEY>. |
ssh-hostkey-rsa-not-shown | Host Key: the fingerprint of the server's RSA key | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server's host key does not match Host Key. The server presented ED25519 SHA256:<SERVER_ED25519_KEY>. | VERIFIED — TESTED SUCCESSFULLY The server's host key does not match Host Key. The server presented ED25519 SHA256:<SERVER_ED25519_KEY>. |
ssh-hostkey-wrong | Host Key: a fingerprint of no key of the server | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server's host key does not match Host Key. The server presented ED25519 SHA256:<SERVER_ED25519_KEY>. | VERIFIED — TESTED SUCCESSFULLY The server's host key does not match Host Key. The server presented ED25519 SHA256:<SERVER_ED25519_KEY>. |
ssh-hostkey-keygen-line | Host Key: the whole line ssh-keygen -lf prints for the server's ED25519 key | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 128.13 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 5.9 s the server logged a password login |
Server and Port
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ssh-port-2222 | Port 2222 (the server's second SSH port) | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 94.63 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 7.1 s the server logged a password login |
ssh-port-empty | Port empty | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 65.15 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 7.1 s the server logged a password login |
ssh-port-closed | Port 2223 (nothing listens on it) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server refused the connection on port 2223. Check the Port field. | VERIFIED — TESTED SUCCESSFULLY The server refused the connection on port 2223. Check the Port field. |
ssh-port-other-service | Port 2224 (a service that does not speak SSH answers it) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY SSH handshake failed (Failed getting banner). Check that Port is the server's SSH port. | VERIFIED — TESTED SUCCESSFULLY SSH handshake failed (Failed getting banner). Check that Port is the server's SSH port. |
ssh-port-no-answer | Port 2222 (the server's second SSH port); server: every new connection to port 2222 dropped | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server did not answer on port 2222. Check the Server and Port fields and the network. | VERIFIED — TESTED SUCCESSFULLY The server did not answer on port 2222. Check the Server and Port fields and the network. |
ssh-host-unknown | Server is a name that does not exist | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Cannot find the server. Check the Server field and the network. | VERIFIED — TESTED SUCCESSFULLY Cannot find the server. Check the Server field and the network. |
ssh-host-name | Server is a DNS name of the server | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 107.43 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s the server logged a password login |
Server settings
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ssh-server-hardened | server: KexAlgorithms curve25519-sha256 only, Ciphers chacha20-poly1305 and aes256-gcm, MACs hmac-sha2 ETM only | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 104.81 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s the server logged a password login |
ssh-server-aes-gcm | server: Ciphers aes256-gcm and aes128-gcm only | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 112.52 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s the server logged a password login |
ssh-server-aes-ctr | server: Ciphers aes256-ctr and aes128-ctr only | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 97.21 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 4.9 s the server logged a password login |
ssh-server-chacha | server: Ciphers chacha20-poly1305 only | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 79.63 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 4.9 s the server logged a password login |
ssh-server-hostkey-ed25519 | Host Key: the fingerprint of the server's ED25519 key; server: HostKeyAlgorithms ssh-ed25519 | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 108.79 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 7.1 s the server logged a password login |
ssh-server-hostkey-ecdsa | Host Key: the fingerprint of the server's ECDSA key; server: HostKeyAlgorithms ecdsa-sha2-nistp256 | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 71.48 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s the server logged a password login |
ssh-server-hostkey-rsa | Host Key: the fingerprint of the server's RSA key; server: HostKeyAlgorithms rsa-sha2-512,rsa-sha2-256 | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 85.95 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s the server logged a password login |
ssh-server-banner | server: Banner /etc/issue.net | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 38.97 Mbit/s the server logged a password login | VERIFIED — TESTED SUCCESSFULLY transfer 8.3 s the server logged a password login |
ssh-server-keepalive-idle | server: ClientAliveInterval 5, ClientAliveCountMax 2 | connect, then 40 s without traffic | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login idle for 40 s: traffic worked before and after, and the VPN stayed connected | VERIFIED — TESTED SUCCESSFULLY the server logged a password login idle for 40 s: traffic worked before and after, and the VPN stayed connected |
Log levels
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ssh-log-normal | Log Level Normal | download, 10 s | connect | VERIFIED — TESTED SUCCESSFULLY 32.24 Mbit/s Release build the server logged a password login in the log: the connect line, the server's host key, the login line, the session line not in the log: the transfer counters, a line for each connection, the packet engine's start line, the packet engine's own lines, the password | VERIFIED — TESTED SUCCESSFULLY transfer 4.9 s the server logged a password login in the log: the connect line, the server's host key, the login line, the session line not in the log: the transfer counters, a line for each connection, the packet engine's start line, the packet engine's own lines, the password |
ssh-log-expert | Log Level Expert | download, 10 s | connect | VERIFIED — TESTED SUCCESSFULLY 59.39 Mbit/s Release build the server logged a password login in the log: the connect line, the login line, the session line, the transfer counters not in the log: a line for each connection, the packet engine's start line, the packet engine's own lines, the password | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s the server logged a password login in the log: the connect line, the login line, the session line, the transfer counters not in the log: a line for each connection, the packet engine's start line, the packet engine's own lines, the password |
ssh-log-debug | Log Level Debug | download, 10 s | connect | VERIFIED — TESTED SUCCESSFULLY 56.39 Mbit/s Release build the server logged a password login in the log: the connect line, the session line, the transfer counters, a line for each connection, the packet engine's start line, the packet engine's own lines not in the log: the password | VERIFIED — TESTED SUCCESSFULLY transfer 6.0 s the server logged a password login in the log: the connect line, the session line, the transfer counters, a line for each connection, the packet engine's start line not in the log: the password |
Sleep, lost connections, network switch and Retry Times
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ssh-retry-before-connect | Port 2222 (the server's second SSH port); server: port 2222 refuses connections; Retry Times 2 | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Could not connect after 2 attempts. (The server refused the connection on port 2222. Check the Port field.) | VERIFIED — TESTED SUCCESSFULLY Could not connect after 2 attempts. (The server refused the connection on port 2222. Check the Port field.) |
ssh-life-sleep-modes | On Sleep Stay, Pause and Off, and Off with Auto Reconnect off | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login On Sleep Stay, Auto Reconnect on: connected again after 3.2 s On Sleep Pause, Auto Reconnect off: connected again after 4.0 s On Sleep Off, Auto Reconnect on: connected again after 3.9 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. |
ssh-life-server-ends-reconnect | the server ends the session; Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login connected again after 5.3 s | VERIFIED — TESTED SUCCESSFULLY connected again 2.8 s after the drop; transfer passed |
ssh-life-server-ends-no-reconnect | the server ends the session; Auto Reconnect off | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login ended after 5.0 s with: The server closed the connection (auto reconnect is off). | VERIFIED — TESTED SUCCESSFULLY ended with: The server closed the connection (auto reconnect is off). |
ssh-life-reset-reconnect | the server resets the TCP connection; Log Level Expert; Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login connected again after 5.2 s | VERIFIED — TESTED SUCCESSFULLY connected again 2.8 s after the reset; transfer passed |
ssh-life-reset-no-reconnect | the server resets the TCP connection; Auto Reconnect off | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login ended after 5.0 s with: The connection was reset (auto reconnect is off). | VERIFIED — TESTED SUCCESSFULLY ended with: The connection was reset (auto reconnect is off). |
ssh-life-path-switch | Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login connected again after 0.9 s | VERIFIED — TESTED SUCCESSFULLY moved back to Wi-Fi: 3 sessions in all; transfer passed |
ssh-life-retry-exhausted | Port 2222 (the server's second SSH port); the server ends the session and refuses new connections; Auto Reconnect on; Retry Times 2 | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login ended after 5.4 s with: Could not reconnect after 2 attempts. (The server refused the connection on port 2222. Check the Port field.) | VERIFIED — TESTED SUCCESSFULLY ended with: Could not reconnect after 2 attempts. (The server refused the connection on port 2222. Check the Port field.) |
ssh-life-silent-drop-reconnect | Port 2222 (the server's second SSH port); server: every packet of the session dropped, no reset, until the app tries a new connection; Log Level Expert; Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login the server saw the app's new connection attempt 26 s after the path went dead connected again after 28.4 s | VERIFIED — TESTED SUCCESSFULLY noticed the dead path after 51.0 s, connected again 54.7 s after the drop began; transfer passed |
ssh-life-outage-reconnect | Port 2222 (the server's second SSH port); the server ends the session and refuses new connections for 8 s; Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server logged a password login connected again after 10.0 s | VERIFIED — TESTED SUCCESSFULLY connected again 1.4 s after the server came back, after 4 attempts; transfer passed |
The server as the guide sets it up
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
ssh-guide-udp-download | Host Key: the fingerprint of the server's ED25519 key; UDP Relay on; the user, sshd file and UDP relay that OpenSSH server sets up | download, 30 s, and a DNS query over UDP | connect | VERIFIED — TESTED SUCCESSFULLY 112.79 Mbit/s the server logged a password login the UDP DNS query was answered, and saw the server's address | VERIFIED — TESTED SUCCESSFULLY transfer 10.6 s the server logged a password login the UDP DNS query was answered, and saw the server's address |