Zoltan Pappandhchengting 10a35f9215 Handle network changes without restarting the engine (#237) ...

Network changes no longer restart the engine; they are handled as events.

No network: the reconnect loops suspend instead of retrying against an unreachable network, and the UI and the notification show "No network available". The loops resume with a fresh backoff when connectivity returns.
Network switch: stale management, signal and relay connections are swept and re-dialed immediately on the new network (cross-transport handover fast path: fix: notify Go core on seamless network handover (cellular → WiFi) while VPN is active #243).
WiFi-to-WiFi handovers are detected by network identity, so a same-transport switch triggers the same reconnect path.
Availability is seeded from non-VPN internet networks, so an up tunnel cannot mask a missing underlying network.
New instrumented e2e suites (NetworkTransitionTest, ExitNodeNetworkTransitionTest) cover blackout, transport-switch and handover scenarios with outage budgets.
---------

Co-authored-by: hchengting <74168694+hchengting@users.noreply.github.com>

2026-08-25 20:24:31 +02:00

..

actions/build-android

Pin gobind alongside gomobile instead of running gomobile init (#240)

2026-08-17 12:10:34 +02:00

workflows

Handle network changes without restarting the engine (#237)

2026-08-25 20:24:31 +02:00