VPN detection of connection loss? #265

dohl commented 2025年05月20日 11:40:01 +02:00

Hello,

we are using the windows eduVPN Client Version 4.2.

We are receiving more and more complaints that our users cannot recognise in the VPN client that the VPN is not working at all due to a missing network.

We have configured wireguard.

It would be nice if the user could recognise that the VPN has no connection to the institution, e.g. due to a missing network connection or disruption of their own Internet.

You can recognise this quite quickly in the log (Connection loss in 09:18:06)
2025年05月14日 09:16:24.988225: [TUN] [...] Sending handshake initiation to peer 1 (...:443)
2025年05月14日 09:16:25.782860: [TUN] [...] Receiving handshake response from peer 1 (...:443)
2025年05月14日 09:16:25.782860: [TUN] [...] Keypair 1 created for peer 1
2025年05月14日 09:16:25.393026: [TUN] [...] Startup complete
2025年05月14日 09:18:06.766023: [TUN] [...] Retrying handshake with peer 1 (...:443) because we stopped hearing back after 15 seconds
2025年05月14日 09:18:06.768248: [TUN] [...] Sending handshake initiation to peer 1 (...:443)
2025年05月14日 09:18:11.164325: [TUN] [...] Handshake for peer 1 (...:443) did not complete after 5 seconds, retrying (try 2)
2025年05月14日 09:18:11.164325: [TUN] [...] Sending handshake initiation to peer 1 (...:443)
2025年05月14日 09:18:16.198690: [TUN] [...] Handshake for peer 1 (...:443) did not complete after 5 seconds, retrying (try 3)
2025年05月14日 09:18:16.198690: [TUN] [...] Sending handshake initiation to peer 1 (...:443)
2025年05月14日 09:18:21.295285: [TUN] [...] Handshake for peer 1 (...:443) did not complete after 5 seconds, retrying (try 4)

Many Thanks

Best Regards
Thomas

Hello, we are using the windows eduVPN Client Version 4.2. We are receiving more and more complaints that our users cannot recognise in the VPN client that the VPN is not working at all due to a missing network. We have configured wireguard. It would be nice if the user could recognise that the VPN has no connection to the institution, e.g. due to a missing network connection or disruption of their own Internet. You can recognise this quite quickly in the log (Connection loss in 09:18:06) 2025年05月14日 09:16:24.988225: [TUN] [...] Sending handshake initiation to peer 1 (...:443) 2025年05月14日 09:16:25.782860: [TUN] [...] Receiving handshake response from peer 1 (...:443) 2025年05月14日 09:16:25.782860: [TUN] [...] Keypair 1 created for peer 1 2025年05月14日 09:16:25.393026: [TUN] [...] Startup complete 2025年05月14日 09:18:06.766023: [TUN] [...] Retrying handshake with peer 1 (...:443) because we stopped hearing back after 15 seconds 2025年05月14日 09:18:06.768248: [TUN] [...] Sending handshake initiation to peer 1 (...:443) 2025年05月14日 09:18:11.164325: [TUN] [...] Handshake for peer 1 (...:443) did not complete after 5 seconds, retrying (try 2) 2025年05月14日 09:18:11.164325: [TUN] [...] Sending handshake initiation to peer 1 (...:443) 2025年05月14日 09:18:16.198690: [TUN] [...] Handshake for peer 1 (...:443) did not complete after 5 seconds, retrying (try 3) 2025年05月14日 09:18:16.198690: [TUN] [...] Sending handshake initiation to peer 1 (...:443) 2025年05月14日 09:18:21.295285: [TUN] [...] Handshake for peer 1 (...:443) did not complete after 5 seconds, retrying (try 4) Many Thanks Best Regards Thomas

rozmansi commented 2025年05月20日 12:39:11 +02:00

Thank you for your suggestion.

We started a discussion how to address this. Possibly not only in Windows client but macOS and other clients as well.

Thank you for your suggestion. We started a discussion how to address this. Possibly not only in Windows client but macOS and other clients as well.

rozmansi commented 2025年07月08日 16:34:41 +02:00

The client will be upgraded to routinely perform WireGuard tunnel traffic test. Currently, it does so only initially.

The client will be upgraded to routinely perform WireGuard tunnel traffic test. Currently, it does so only initially.

rozmansi commented 2025年07月31日 15:08:18 +02:00

I have released the 4.4.99.1 now.

The client now attempts to detect connectivity issues instead of WireGuard (this was always out of WireGuard scope). If your server also supports WireGuard over TCP (ProxyGuard), it will attempt to switch to TCP.

Feel free to reopen this issue, should the change need anything else.

I apologize for the delay. I've been busy on other projects.

I have released the [4.4.99.1](https://codeberg.org/eduVPN/windows/releases/tag/4.4.99.1) now. The client now attempts to detect connectivity issues instead of WireGuard (this was always out of WireGuard scope). If your server also supports WireGuard over TCP (ProxyGuard), it will attempt to switch to TCP. Feel free to reopen this issue, should the change need anything else. I apologize for the delay. I've been busy on other projects.