You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hotfix for v0.2.3 / v0.2.4: a failed openconnect handshake could leave a
zombie child behind with vpnc-script's DNS and route mutations applied
but never reverted, stranding the entire machine's networking until the
user quit the app. The connect() failure branch now always SIGTERMs any
residual child so vpnc-script's disconnect phase restores DNS/routes.
Also: the pre-connect host-route flush now only deletes when `route get`
returns a concrete IPv4 destination. Previously, if no dedicated host
route existed, the fall-through destination "default" was passed to
`route delete`, wiping the system default route.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
<p><strong>Hotfix — strongly recommended for v0.2.3 / v0.2.4 users.</strong></p>
15
+
<ul>
16
+
<li>Fixed a case where a failed openconnect handshake could leave a zombie child behind, with vpnc-script's DNS and route mutations applied but never reverted — symptom: "WiFi connected but nothing has network access" until the user quit the app. connect() now always SIGTERMs any residual child on failure so vpnc-script's disconnect phase runs and restores DNS/routes.</li>
17
+
<li>Pre-connect route flush now only deletes when the kernel returns a concrete IPv4 destination. Previously, when no dedicated host route existed, `route get` fell through to the default route (destination="default") and the subsequent delete wiped the system default route.</li>
0 commit comments