Test Results
Every SoftEther VPN case we ran on 7 November 2026, with its result on an iPhone and on an Android phone: 60 of 60 cases passed on the iPhone and 60 of 60 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 013f04fb, as a Debug build on the iPhone and a debug APK on Android; the iPhone's rows of the log cases and sev-wrong-password come from a Release build of commit 7708f7a3, the kind TestFlight ships. The server was SoftEther VPN Server 4.44 Build 9807 on Ubuntu 24.04, set up as SoftEther VPN Server describes, with the users of each login method in the hubs DEFAULT and TEST-HUB.
- 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. Where a row names TCP connections, UDP acceleration or NAT-T, the server's
SessionGetshowed it for the phone's session while the case ran. In the cases that set Connections it was read about 10 seconds into the transfer; the app adds one connection per second, so with 32 the server counted fewer at that moment. Where a row shows how the ClientHello was sent, the server recorded the sizes of the phone's first TCP segments to port 443. - 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
sev-log-…read the connection log back and checked its lines: Normal must show the connect and session lines and neither the virtual adapter's DHCP line nor the core's own lines; Expert adds the DHCP line; Debug adds the core's lines; and no level may show a TLS session secret.sev-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 of commit7708f7a3, the kind TestFlight ships, and again on a Debug build of the same commit, with the same result. - Proxies. The proxy cases went through HTTP CONNECT and SOCKS5 proxies and PAC files on a computer in our office network, with and without a username and password.
- Lifecycle. The cases named
sev-life-…checked On Sleep, a session the server disconnected (SessionDisconnect), the SoftEther service stopped until Retry Times ran out, and the service stopped for 8 seconds and started again. On Android the screen was really turned off; the iPhone's On Sleep case tells the tunnel that the phone slept.
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 uploads took most of the line.
Not tested in this round
- Moving between Wi-Fi and cellular. Every case ran on Wi-Fi; no test changed the network under a connected tunnel.
- 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. The hubs' SecureNAT hands out IPv4 addresses only.
- NT Domain login. It needs SoftEther VPN Server on Windows; our server runs on Linux, and the RADIUS / NT Domain method was tested with RADIUS.
Logins and hubs
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
sev-pass-download | defaults | download, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY 126.06 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-pass-full-duplex | defaults | download and upload at once, 90 s | connect | VERIFIED — TESTED SUCCESSFULLY down 5.25 / up 56.39 Mbit/s 2 TCP connections | VERIFIED — TESTED SUCCESSFULLY transfer 15.0 s 2 TCP connections |
sev-pass-upload | defaults | upload, 60 s | connect | VERIFIED — TESTED SUCCESSFULLY down 0.0 / up 61.38 Mbit/s 2 TCP connections | VERIFIED — TESTED SUCCESSFULLY transfer 8.3 s 2 TCP connections |
sev-radius-download | Method RADIUS / NT Domain | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 130.31 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-anon-download | Method Anonymous | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 123.32 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 8.4 s 2 TCP connections |
sev-cert-signed-download | Method Certificate (signed certificate user) | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 117.91 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-cert-individual-download | Method Certificate (individual certificate user) | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 122.61 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.3 s 2 TCP connections |
sev-hub-test-hub | Virtual Hub TEST-HUB | download, 30 s | connect | VERIFIED — TESTED SUCCESSFULLY 121.87 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.3 s 2 TCP connections |
sev-wrong-password | wrong password | connect only | refused | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the reason the app closed the connection not in the log: TLS secrets Authentication failed. Check the username, password and authentication method. | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the reason the app closed the connection not in the log: TLS secrets Authentication failed. Check the username, password and authentication method. |
sev-wrong-hub | Virtual Hub NO-SUCH-HUB | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Virtual Hub not found. Check the Virtual Hub field. | VERIFIED — TESTED SUCCESSFULLY Virtual Hub not found. Check the Virtual Hub field. |
sev-radius-user-standard-method | RADIUS user | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username, password and authentication method. | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username, password and authentication method. |
sev-radius-wrong-password | Method RADIUS / NT Domain; wrong password | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username, password and authentication method. | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username, password and authentication method. |
sev-anon-on-password-user | Method Anonymous; password user | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username, password and authentication method. | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username, password and authentication method. |
sev-cert-rogue-ca | Method Certificate (a certificate from another authority) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username, password and authentication method. | VERIFIED — TESTED SUCCESSFULLY Authentication failed. Check the username, password and authentication method. |
sev-cert-missing | Method Certificate without a certificate | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Certificate authentication requires a client certificate in the profile. | VERIFIED — TESTED SUCCESSFULLY The client certificate could not be read. Re-import it in the profile. |
Certificate check, Hostname and ports
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
sev-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 |
sev-verify-ip-accepted | Server is the server's IP address | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 125.21 Mbit/s the certificate warning was accepted | VERIFIED — TESTED SUCCESSFULLY transfer 7.3 s 2 TCP connections |
sev-hostname-override-ip | Server is the server's IP address; Hostname <SERVER_HOST> | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 117.89 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.3 s 2 TCP connections |
sev-hostname-override-wrong | Hostname a name the certificate is not for | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The server certificate name does not match the server. Check the Hostname field. | VERIFIED — TESTED SUCCESSFULLY the certificate warning was declined |
sev-allow-untrusted-ip | Server is the server's IP address; TLS Server Verification off | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 118.93 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-port-992 | Port 992 | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 115.7 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-port-5555 | Port 5555 | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 113.19 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.1 s 2 TCP connections |
sev-port-other-service | Port 22 (the server's SSH answers it) | connect only | refused | VERIFIED — TESTED SUCCESSFULLY The TLS handshake with the server failed. Check the Server and Port fields. | VERIFIED — TESTED SUCCESSFULLY The TLS handshake with the server failed. Check the Server and Port fields. |
Connections and UDP acceleration
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
sev-conns-2 | Connections 2 | download and upload at once, 40 s | connect | VERIFIED — TESTED SUCCESSFULLY down 10.92 / up 54.6 Mbit/s 2 TCP connections | VERIFIED — TESTED SUCCESSFULLY transfer 14.0 s 2 TCP connections |
sev-conns-8 | Connections 8 | download and upload at once, 40 s | connect | VERIFIED — TESTED SUCCESSFULLY down 17.45 / up 49.86 Mbit/s 8 TCP connections | VERIFIED — TESTED SUCCESSFULLY transfer 15.0 s 8 TCP connections |
sev-conns-32 | Connections 32 | download and upload at once, 40 s | connect | VERIFIED — TESTED SUCCESSFULLY down 42.95 / up 40.27 Mbit/s 12 TCP connections | VERIFIED — TESTED SUCCESSFULLY transfer 16.2 s 13 TCP connections |
sev-udp-accel | UDP acceleration on | download and upload at once, 40 s | connect | VERIFIED — TESTED SUCCESSFULLY down 9.81 / up 49.04 Mbit/s 2 TCP connections UDP acceleration active | VERIFIED — TESTED SUCCESSFULLY transfer 13.9 s 2 TCP connections UDP acceleration active |
sev-udp-accel-conns-4 | Connections 4; UDP acceleration on | download and upload at once, 40 s | connect | VERIFIED — TESTED SUCCESSFULLY down 10.29 / up 48.9 Mbit/s 4 TCP connections UDP acceleration active | VERIFIED — TESTED SUCCESSFULLY transfer 16.1 s 4 TCP connections UDP acceleration active |
NAT traversal
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
sev-natt-closed-tcp-port | Port 5557 (nothing listens on it); NAT-T on | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 84.51 Mbit/s over NAT-T | VERIFIED — TESTED SUCCESSFULLY transfer 8.3 s 2 TCP connections over NAT-T |
sev-natt-off-closed-tcp-port | Port 5557 (nothing listens on it); NAT-T off | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection. | VERIFIED — TESTED SUCCESSFULLY Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection. |
sev-natt-hint-server | NAT-T on, hint the server's own address | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 93.28 Mbit/s over NAT-T | VERIFIED — TESTED SUCCESSFULLY transfer 8.3 s 2 TCP connections over NAT-T |
sev-natt-hint-wrong | NAT-T on, hint an address no server has | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection. | VERIFIED — TESTED SUCCESSFULLY Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection. |
Proxies and PAC files
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
sev-proxy-http | HTTP proxy | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 114.2 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 8.3 s 2 TCP connections |
sev-proxy-http-auth | HTTP proxy with username and password | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 126.62 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-proxy-http-wrong-auth | HTTP proxy with a wrong password | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Proxy authentication failed. | VERIFIED — TESTED SUCCESSFULLY Proxy authentication failed. |
sev-proxy-socks5 | SOCKS5 proxy | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 123.08 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-proxy-socks5-auth | SOCKS5 proxy with username and password | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 114.17 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-proxy-socks5-wrong-auth | SOCKS5 proxy with a wrong password | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Proxy authentication failed. | VERIFIED — TESTED SUCCESSFULLY Proxy authentication failed. |
sev-proxy-unreachable | proxy port nothing listens on | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Cannot connect to the proxy server. | VERIFIED — TESTED SUCCESSFULLY Cannot connect to the proxy server. |
sev-pac-http | PAC file: PROXY | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 108.43 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-pac-http-auth | PAC file: PROXY with username and password | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 123.59 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-pac-socks5 | PAC file: SOCKS5 | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 121.35 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-pac-socks | PAC file: SOCKS | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 109.21 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-pac-socks5-auth | PAC file: SOCKS5 with username and password | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 104.77 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-pac-direct | PAC file: DIRECT | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 110.47 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-pac-fallback | PAC file: an unreachable PROXY, then a working one | download, 20 s | connect | VERIFIED — TESTED SUCCESSFULLY 103.96 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-pac-missing | PAC file: a PAC URL that answers 404 | connect only | refused | VERIFIED — TESTED SUCCESSFULLY Unable to download PAC configuration | VERIFIED — TESTED SUCCESSFULLY Unable to download PAC configuration |
TLS Fragmentation
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
sev-frag-off-capture | TLS Server Verification off; TLS Fragmentation Off | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 116.78 Mbit/s ClientHello sent as 324 bytes | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections ClientHello sent as 1440 + 111 bytes |
sev-frag-auto-capture | TLS Server Verification off; TLS Fragmentation Auto | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 112.02 Mbit/s ClientHello sent as 43 + 256 + 25 bytes | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections ClientHello sent as 43 + 256 + 256 + 256 + 256 + 256 + 228 bytes |
sev-frag-manual-20-100-capture | TLS Server Verification off; TLS Fragmentation Manual 20/100 | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 112.32 Mbit/s ClientHello sent as 20 + 100 + 100 + 100 + 4 bytes | VERIFIED — TESTED SUCCESSFULLY transfer 6.1 s 2 TCP connections ClientHello of 1551 bytes; its first 720 bytes sent as 20 + 100 + 100 + 100 + 100 + 100 + 100 + 100 (the server recorded the first 8 pieces) |
sev-frag-auto-verified | TLS Fragmentation Auto | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 111.52 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.2 s 2 TCP connections |
sev-frag-auto-proxy | HTTP proxy; TLS Fragmentation Auto | download, 15 s | connect | VERIFIED — TESTED SUCCESSFULLY 114.65 Mbit/s | VERIFIED — TESTED SUCCESSFULLY transfer 7.3 s 2 TCP connections |
Log levels
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
sev-log-normal | Log Level Normal | connect only | connect | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the session line not in the log: the adapter's DHCP line, the core's own lines, TLS secrets | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the session line not in the log: the adapter's DHCP line, the core's own lines, TLS secrets |
sev-log-expert | Log Level Expert | connect only | connect | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the adapter's DHCP line not in the log: the core's own lines, TLS secrets | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the adapter's DHCP line not in the log: the core's own lines, TLS secrets |
sev-log-debug | Log Level Debug | connect only | connect | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the adapter's DHCP line, the core's own lines not in the log: TLS secrets | VERIFIED — TESTED SUCCESSFULLY in the log: the connect line, the adapter's DHCP line, the core's own lines not in the log: TLS secrets |
Sleep, lost connections and Retry Times
| Case | Settings | Traffic | Expected | iPhone | Android |
|---|---|---|---|---|---|
sev-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.1 s On Sleep Pause, Auto Reconnect off: connected again after 4.4 s On Sleep Off, Auto Reconnect on: connected again after 4.3 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. |
sev-life-peer-drop-reconnect | Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 5.1 s | VERIFIED — TESTED SUCCESSFULLY connected again 2.9 s after the drop; transfer passed |
sev-life-peer-drop-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). |
sev-life-retry-exhausted | Auto Reconnect on; Retry Times 2 | connect only | connect | VERIFIED — TESTED SUCCESSFULLY the server was stopped: ended after 27.7 s with: Could not reconnect after 2 attempts. (Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection.) | VERIFIED — TESTED SUCCESSFULLY ended after 2 retries with: Could not reconnect after 2 attempts. (Cannot reach the server (DNS lookup or TCP connection failed). Check the Server field for typos and the network connection.) |
sev-life-outage-reconnect | Auto Reconnect on | connect only | connect | VERIFIED — TESTED SUCCESSFULLY connected again after 23.0 s | VERIFIED — TESTED SUCCESSFULLY connected again 3.9 s after the server came back, after 1 attempts; transfer passed |