Repository navigation
Mavi VPN 1.0.2 — Server connection hardening
Mavi VPN 1.0.2 hardens server connection setup against stalled QUIC and HTTP/3 peers and improves deployment and client setup documentation.
What's changed
- Bounded QUIC connection setup: A single 10-second deadline now covers the transport handshake, authentication, and tunnel configuration delivery. Setup progress, keepalives, and blocked stream or response flow control cannot restart or extend that deadline.
- Pending connection limit: The server accepts at most 100 simultaneous QUIC connections awaiting setup, alongside the existing 1,000-connection limit. Pending slots are released when setup completes or the connection exits.
- Reliable setup cleanup: Timed-out raw QUIC and HTTP/3 connections are closed, releasing connection slots and any allocated tunnel addresses. The deadline also covers stalled HTTP/3 camouflage responses.
- Established tunnel continuity: Successfully initialized tunnels are no longer subject to the setup deadline. Regression tests cover raw QUIC and HTTP/3 tunnel survival, stalled responses, address cleanup, and the transition from setup to an active tunnel.
- Clearer setup documentation: Expanded instructions for prebuilt Docker deployment, release downloads, Windows/Linux/Android clients, authentication, transport selection, and troubleshooting, including Windows IPv6 requirements.
Upgrade notes
Update the server to receive the connection-setup hardening. These changes apply to raw QUIC and HTTP/3; HTTP/2 behavior is unchanged. Clients must complete QUIC setup within 10 seconds, and new connection attempts may be rejected while all 100 pending slots are occupied.
Windows clients still require complete IPv6 tunnel settings from the server. Configure IPv6 networking and forwarding and set VPN_DISABLE_IPV6=false before connecting Windows clients.
Release versions are synchronized to 1.0.2 across the Rust workspace, desktop GUI, and Android app. Android's version code increases to 4.
Full changelog: Changes since 1.0.1.