[FEATURE] - Auto-reconnect on handshake failure or timeout

[Jeylucifer]

Add an optional auto-reconnect feature that restarts the tunnel when handshake failures occur or when no successful handshake is received within a configurable timeout. This would help maintain stable connectivity on unreliable networks.

[skooterking5]

If I'm not mistaken, the app does continue to retry the handshake in the background, it just doesn't tell the user.

[Gothico74]

No. Tunnel collapses and is bypassed. In list its on but red (disconnected).
Odly i cannot pin down the issue thats forcing a handshake failure. Also its random (it seems so). Serverside are no logs about this event.

[zaneschepke]

No. Tunnel collapses and is bypassed. In list its on but red (disconnected). Odly i cannot pin down the issue thats forcing a handshake failure. Also its random (it seems so). Serverside are no logs about this event.

The tunnel should not collapse and bypass in this scenario. If it is, then this is a bug. Can you please share what issue this is occurring on?

[BELLA12GLG]

Carriers often block long-lived connections; this is common practice in China.

[bar-g]

This sounds similar to #1036, maybe try the same?:

With UDP I think some NAT/FW routers can close connections after just 30 seconds. Thus the WG default for persistent keepalives is 25 seconds, and it must be kept enabled at least on one side (probably most battery-efficient: on the server), if at least one side (likely a client) is changing between networks/IPs (i.e. "roaming").

At least with the new wgtunnel feature to do DynDNS re-resolves (for servers behind dynamic IPs), wgtunnel should watch and re-attempt handshakes after a failure. Have you tried enabling that?