Wireguard handshake problems in Mesh WiFis

[hvbakel]

The new version indeed fixes the issue. Thank you for the quick turn-around, much appreciated!

[Geier97332]

Hi,

I still have the problem in a Mesh WiFi.

[admin]

In the latest release the "Restart WireGuard connection when connectivity change" option restarts the VPN even when a connectivity change event is received with the same WiFi SSID the device was connected to.
Initially, in release 1.01.35, this change introduced problems on some devices and therefore, in release 1.01.36, a minimum limit of 1.5 seconds was placed between one event and another.
Unfortunately, if these changes didn't fix the problem, it means that in your case the connectivity change events are not sent and therefore there is no way to know when your device moves from one AP to another.

[Geier97332]

Hello,
I tried it again, but no success.

Thanks for your work!

[Geier97332]

Hi,

I tried it again in two other network, but with same result.

Maybe you can add an option to restart the wireguard connection after defined handshake attempts.

Thanks!

[admin]

Do you see messages like "Connectivity change detected: ..." in the VPN log?

[Geier97332]

No, just "Send handshake (XXX) to IP:Port" and then "Peer IP:Port handshake timeout" repeating till I manually turn off and on the wireguard connection.

[admin]

The new release 1.01.37 has just been released.
I'll see if it will be possible to add this option in the next release...

[admin]

Maybe you can add an option to restart the wireguard connection after defined handshake attempts.

I sent you PM with a test version...

[Geier97332]

Hi,

I was able to test the new version now and it works as designed.
My phone restarts wireguard after max handshakes and I get a working connection.

Thanks you very much and best regards!