Why does Synergy need to reach unreachable computers?

[anthonypants]

I've been having lots of really weird issues with Synergy (3.0.68.13) on my macOS (13.2.1) client, so I uninstalled it, tried to remove as many settings as I could find, booted into Safe Mode, then reinstalled Synergy, but I'm still getting this issue where synergy-service tries to reach 172.0.0.0/8 or 192.168.0.0/16 addresses. These IP address ranges aren't on my home network, so I don't know if this is a "feature" of the Synergy 3 beta, but since it takes around three months to get a response from the support form, I thought I'd ask in here.

 

Quote

synergy-service [2023-03-23T19:33:52] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:33:52] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:33:52] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:33:52] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:33:52] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:33:52] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:33:52] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:33:52] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:34:28] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:34:28] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:34:28] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:34:28] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:34:32] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:34:32] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:34:32] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:34:32] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:20] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:20] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:20] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:20] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:22] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:22] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:22] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:22] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:33] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:33] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:33] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:33] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:38] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:38] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:38] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:38] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:58] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:58] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:58] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:58] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:58] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:58] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:35:58] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:35:58] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:36:02] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:36:02] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

synergy-service [2023-03-23T19:36:02] - ERROR - Error: connect ETIMEDOUT 172.30.32.1:24802

synergy-service [2023-03-23T19:36:02] - ERROR - Error: connect ETIMEDOUT 192.168.160.1:24802

 

[hobbit1974]

speculation: you probably have multiple network interfaces, and the auto-discovery will keep trying to connect on all of them...

[anthonypants]

6 minutes ago, hobbit1974 said:

speculation: you probably have multiple network interfaces, and the auto-discovery will keep trying to connect on all of them...

That's an interesting guess! I don't happen to have any interfaces on those subnets on my client, which is where I'm seeing these logs. But, the host computer does have some virtual addresses configured with addresses in those ranges. Mystery solved, I guess. Doesn't seem like there's a way to bind Synergy to a single interface, or to only have it announce specific addresses.

[hobbit1974]

Yeah, i noticed them in my logs too, and I didn't dig further into it. I've spent enough time deep down in the bowels of ERP systems, so this wasn't a red flag when everything else was working...!

But you're right, a feature that would allow binding to a certain interface would definitely be a big plus.

[Exomusic]

I'm having the same problem on a Mac that is connecting to Windows 10.  I don't have a clue what to do now.  Can you  point me in the right direction?

Thanks in advance!

Stephen