TunSafe Forum

Welcome to the TunSafe Community Forum. This is open for discussions related to TunSafe and the WireGuard protocol.

You are not logged in.

#1 2019-07-06 10:02:21

Tuni
Member
Registered: 2019-07-06
Posts: 1

Handshake only completes for the "auto-detected" server

I successfully set up TunSafe with the standard WireGuard client on macOS 10.14. Works like a charm. However, I can only use the "auto-detected" server, in my case "Netherlands #1". When I try to setup a second server (London, Amsterdam via Sweden, Frankfurt), the handshake never completes. The log looks like this:

2019-07-06 10:48:58.688402: [APP] Tunnel 'TunSafe London #1' connection status changed to 'connected'
2019-07-06 10:48:58.820520: [NET] peer(FO1H…tjzM) - Sending handshake initiation
2019-07-06 10:48:58.821314: [NET] peer(FO1H…tjzM) - Awaiting keypair
2019-07-06 10:49:03.509500: [APP] Status update notification timeout for tunnel 'TunSafe London #1'. Tunnel status is now 'connected'.
2019-07-06 10:49:03.825862: [NET] peer(FO1H…tjzM) - Sending handshake initiation
2019-07-06 10:49:08.991305: [NET] peer(FO1H…tjzM) - Handshake did not complete after 5 seconds, retrying (try 2)
2019-07-06 10:49:08.991405: [NET] peer(FO1H…tjzM) - Sending handshake initiation
2019-07-06 10:49:14.274879: [NET] peer(FO1H…tjzM) - Handshake did not complete after 5 seconds, retrying (try 2)
2019-07-06 10:49:14.275003: [NET] peer(FO1H…tjzM) - Sending handshake initiation

My understanding is that I should be able to generate new key pairs for other servers. Any ideas of what is going wrong here?

Offline

Board footer

Powered by FluxBB