When a VPN Says "Connected" but Traffic Is Dead: Building Adaptive Connect 2.0

说明与用途

文章说明 Colitu 遇到 VPN 显示已连接但在 30–50 秒后停止传输流量的问题。Adaptive Connect 2.0 通过验证真实流量、按网络维护历史记录、备份感知健康检查和受限并行探测来解决此问题，在 60 分钟的故障注入测试中实现 98.8% 的成功率。

问题

A VPN can display a connected indicator while application traffic stops flowing after 30–50 seconds, even though the TCP tunnel remains open.

结果

Adaptive Connect 2.0 achieved a 98.8% HTTP probe success rate over 60 minutes with 11 injected faults, maintaining connectivity during a 101‑second primary server outage and limiting interruptions to ~5 seconds.

工作流

• Measure server latency
• Select server
• Establish tunnel
• Verify real traffic via external endpoints
• Report connection as functional only after traffic passes
• Maintain bounded local history per network
• Use backup route only when primary fails
• Track primary and effective health separately
• Parallel probe best candidates with bounded retries
• Inject faults to test resilience

证据

A VPN can establish a tunnel, complete its handshake, display a reassuring green Connected indicator, and still fail at its most important job: carrying traffic.

来源

Adaptive Connect 2.0 treats a connection as functional only after useful traffic successfully passes through the selected tunnel.

来源

In the 60‑minute endurance test, we used eight servers and injected 11 controlled failures lasting roughly 60–120 seconds each. An HTTP probe was sent through the VPN approximately every five seconds.

来源

Successful HTTP probes 741 / 750, HTTP probe success rate 98.8%

来源