LinkWeaver 2.2.19 — Reliable WireGuard Handoff Verification

Full Changelog: v2.2.18...v2.2.19

LinkWeaver 2.2.18 — Failover-First WireGuard Recovery

Full Changelog: v2.2.17...v2.2.18

LinkWeaver 2.2.17 — Automatic Ethernet Rejoin

Full Changelog: v2.2.16...v2.2.17

LinkWeaver 2.2.16 — Session-Preserving Failover

Full Changelog: v2.2.15...v2.2.16

LinkWeaver 2.2.15 — Immediate WireGuard Failover

Full Changelog: v2.2.14...v2.2.15

LinkWeaver 2.2.14 — Verified WireGuard Recovery

What’s fixed

• Keeps your manually selected Ethernet preference persistent while using Wi-Fi only as a temporary verified backup.
• Separates physical-link detection, interface-bound Internet health, and WireGuard end-to-end verification.
• Never labels a recovered adapter active until routed Internet through WireGuard is verified.
• Recreates probe and WireGuard endpoint routes after Ethernet or Wi-Fi disconnects and reconnects.
• Rolls back to the last verified connection when preferred-path recovery is incomplete.
• Can restart a stuck active WireGuard tunnel as a rate-limited last resort when no verified backup remains.
• Adds Aggressive, Fast, Balanced, and Stable response profiles for tuning failover sensitivity.

Validation

Windows tests, Wintun smoke testing, LinkWeaver UI startup testing, installer packaging, Linux protocol tests, and Linux TUN relay smoke testing all passed.

What's Changed

• Fix verified WireGuard failback and add response profiles by @Abse2001 in #34

Full Changelog: v2.2.13...v2.2.14

LinkWeaver 2.2.13 — Persistent Preferred Path

Fixed

• The adapter selected in Preferred connection is now authoritative in tunnel Failover mode for both upload and relay download traffic.
• Wi-Fi is labeled as a temporary active backup instead of incorrectly becoming Preferred.
• Ethernet is reclaimed automatically as soon as its Internet connection recovers.
• Physical probe routes are recreated after cable/link down-up transitions.
• WireGuard's endpoint route is explicitly moved from temporary Wi-Fi back to recovered Ethernet without restarting WireGuard or deliberately tearing down sessions.
• Backup adapters still exchange small health/control probes; Bonding mode still intentionally uses all healthy paths.

Validation

All 18 protocol/scheduler tests, Windows build, WPF startup smoke test, Wintun smoke test, Linux relay test, and installer packaging passed.

What's Changed

• Keep the selected preferred adapter authoritative by @Abse2001 in #32
• Restore preferred adapters correctly under WireGuard by @Abse2001 in #33

Full Changelog: v2.2.12...v2.2.13

LinkWeaver 2.2.12 — Reliable Startup and Tray Activation

Fixed

• Start with Windows now works reliably: LinkWeaver creates an elevated Windows Task Scheduler logon task instead of relying on the registry Run key.
• Pinned shortcut restores the running app: launching LinkWeaver while it is minimized to the tray now opens the existing window instead of starting another instance.
• Existing DualLink/LinkWeaver startup preferences migrate automatically.
• Closing or minimizing continues monitoring in the tray; use Exit from the tray menu to stop it fully.

Validation

All 16 protocol tests, Windows application build, WPF startup smoke test, Wintun smoke test, Linux relay test, and installer packaging passed.

What's Changed

• Fix Start with Windows and restore the tray instance by @Abse2001 in #31

Full Changelog: v2.2.11...v2.2.12

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

LinkWeaver 2.2.10 — Session-Preserving WireGuard Failover

Fixes the session-loss regression introduced by automatic WireGuard service restarts. LinkWeaver now moves only the Proton endpoint route during failover and keeps the live tunnel running so WireGuard can roam to Wi-Fi or tethering without a deliberate teardown. All Windows, Wintun, UI, protocol, and relay checks passed.

What's Changed

• Preserve WireGuard sessions during adapter failover by @Abse2001 in #27

Full Changelog: v2.2.9...v2.2.10