Skip to content

Mavi VPN 1.0 — More ways to connect

Choose a tag to compare

@zerox80 zerox80 released this 05 Sep 22:03

Mavi VPN 1.0 brings a choice of QUIC, HTTP/3 MASQUE, and HTTP/2 CONNECT-IP transports to a self-hosted VPN with Windows, Linux, and Android clients. This milestone focuses on connections that recover more reliably, authentication that stays current, and installers that set up the background services correctly.

Highlights

HTTP/2 when UDP is unavailable

The new end-to-end HTTP/2 CONNECT-IP transport carries VPN traffic over TLS/TCP, providing an alternative on networks that block UDP. QUIC remains the default, with optional HTTP/3 camouflage and MASQUE framing. Select HTTP/2 on the client and enable the server's TCP listener; this is an explicit transport choice, not automatic fallback.

More reliable connections and sign-in

  • Android: Connection setup has an overall deadline and can be cancelled before a native session exists. An unresponsive address no longer blocks all subsequent connection attempts, and an old worker cannot cancel its replacement. Settings now include a dedicated split-tunneling screen.
  • Linux: Keycloak token renewal continues through reconnect backoff. After an outage, the client renews an expired token before authenticating again, while coordinating refresh-token rotation between foreground and background tasks.
  • Windows: The CLI passes Keycloak refresh credentials to the service so it can renew the session. Stopping an HTTP/2 tunnel also works when the upload queue is full, and reconnect cleanup removes stale VPN DNS rules.

Services and installers that work together

  • Windows IPC permissions are refreshed on the already-listening named pipe after a user signs in or switches sessions, including when the service started before login.
  • The Windows NSIS installer now includes the CLI and service, registers and starts the service, and handles service shutdown during upgrades and removal.
  • Linux DEB/RPM packages configure the mavivpn IPC group and restart the daemon with the appropriate permissions. The GUI source installer builds the bundled CLI first.
  • Linux DNS fallback updates preserve the resolver's symlink, inode, and permissions, work with the service sandbox, and retain a durable backup for recovery.
  • The Keycloak Compose overlay resolves the realm import from the correct directory.

Authentication and network hardening

Server-side session-expiry enforcement and HTTP/2 authentication deadlines have been strengthened. This release also addresses JWKS refresh races, IPv6 leak races, and Windows privileged file and WinTUN loading paths. Dependency and CI updates accompany these changes.

Installation and upgrade

See the installation guide for platform setup and the README for server configuration.

  • Windows: Use the MSI or NSIS installer once the 1.0.0 assets are attached. Installation requires administrator privileges to configure the VPN service.
  • Linux: Choose either the GUI package or the CLI-only package. After installation, log out and back in to activate mavivpn group membership. If the package manager could not identify your desktop user, run sudo usermod -aG mavivpn USER first, substituting your trusted local username.
  • Android: Android 8.0 or newer is required. The current CI workflow produces a debug APK, not a production-signed release APK. Android only accepts an in-place update signed with the same certificate; a different signing key can require reinstalling the app and re-entering its configuration.
  • Server: Back up configuration and persistent certificate/key data before upgrading. Use matching 1.0.0 server and client builds when enabling HTTP/2, and keep the configured TUN MTU aligned across peers.

For source builds, Rust 1.95 or newer is required. The h2, h3, and quinn forks continue to track their branch tips, with the resolved commits recorded in Cargo.lock.

Release status

This is a draft. Versioned distribution assets and their checksums must be attached and verified before publication. Android production distribution additionally requires a signing configuration and a verified HTTPS App Link for Keycloak redirects.

Mavi VPN has not been independently security-audited. The 1.0 version number does not change that status. Desktop ECH support is GREASE/camouflage; it does not provide end-to-end encrypted ClientHello confidentiality, and Android uses a cover SNI without an ECH extension.

Changes since 0.99.5: commit comparison.