LinkWeaver 2.2.11 — Connectivity Forensics and Stable Paths

What’s new

• Detects upstream Internet loss even when Ethernet or Wi-Fi remains physically connected.
• Uses two concurrent interface-bound TCP probes with a 75 ms monitoring interval and 225 ms deadline.
• Keeps a manually selected adapter permanently preferred across outages.
• Uses the backup temporarily and reclaims the preferred adapter on its first verified recovery.
• Keeps WireGuard running during route changes instead of restarting the tunnel.
• Stabilizes bonding path identities when adapters disconnect and reconnect.
• Adds detailed connectivity forensics and CSV export: physical state, IPv4, gateway, upstream reachability, active path, WireGuard/bonding state, local/public IP changes, errors, throughput, latency, and outage duration.
• Adds PPP and Bluetooth tethering recognition.

Verification

Passed all automated protocol tests, Windows application build, Wintun smoke test, UI startup test, installer build, and Linux relay checks.

Important

For Proton/WireGuard-only use, choose Failover. The same Proton public IP can normally remain visible while LinkWeaver moves the endpoint route, but absolute session continuity depends on WireGuard roaming and the Proton endpoint. True bandwidth bonding requires a relay.

What's Changed

• LinkWeaver 2.2.11: connectivity forensics and stable failover paths by @Abse2001 in #28
• Detect upstream-only Internet failure immediately by @Abse2001 in #29
• Keep manual preference persistent and reclaim it immediately by @Abse2001 in #30

Full Changelog: v2.2.10...v2.2.11