How to tunnel connections with Synergy 2 to connect computers on distinct subnets that can't reach each other?

[Nick Name]

I have two computers on my desk that (by policy) are on different subnets that are unreachable from each other. I was still able to use Synergy 1 with the following technique:

On server:

ssh -N -f -R 24800:127.0.0.1:24800 … [central_server]

On client:

ssh -N -f -L 24800:127.0.0.1:24800 … [central_server]

I would then configure the client to connect to localhost as the server, and things would work.

How do I solve this problem with Synergy 2?

[Nick Name]

With Synergy 2, I see this on one host:

[ Service ] [2017-10-05T11:39:08] debug: tcp client connect error: Connection refused
[ Service ] [2017-10-05T11:39:08] debug: connectivity test failed for xxx.xxx.xxx.xxx:24810
[ Service ] [2017-10-05T11:39:11] debug: failed report: dest = AAAA, ips = xxx.xxx.xxx.xxx
[ Service ] [2017-10-05T11:39:11] debug: local profile modified, id=BBBB
[ Service ] [2017-10-05T11:39:11] debug: comparing profiles, id=BBBB this=v2 other=v2
[ Service ] [2017-10-05T11:39:11] debug: profile screen test result changed, screenId=AAAA success=``->`` failed=``->`xxx.xxx.xxx.xxx`
[ Service ] [2017-10-05T11:39:11] debug: handling new report from connectivity tester, screenId=AAAA successfulIp= lastServerId=AAAA
[ Service ] [2017-10-05T11:39:11] debug: finished connectivity test

I see this on another:

[ Service ] [2017-10-05T11:37:32] debug: tcp client connect error: Connection refused
[ Service ] [2017-10-05T11:37:32] debug: connectivity test failed for yyy.yyy.yyy.yyy:24810
[ Service ] [2017-10-05T11:37:34] debug: tcp client connect error: Connection refused
[ Service ] [2017-10-05T11:37:34] debug: connectivity test failed for zzz.zzz.zzz.zzz:24810
[ Service ] [2017-10-05T11:37:34] debug: failed report: dest = CCCC, ips = zzz.zzz.zzz.zzz,yyy.yyy.yyy.yyy
[ Service ] [2017-10-05T11:37:34] debug: local profile modified, id=BBBB
[ Service ] [2017-10-05T11:37:34] debug: comparing profiles, id=BBBB this=v2 other=v2
[ Service ] [2017-10-05T11:37:34] debug: profile screen test result changed, screenId=CCCC success=``->`` failed=``->`zzz.zzz.zzz.zzz,yyy.yyy.yyy.yyy`
[ Service ] [2017-10-05T11:37:34] debug: handling new report from connectivity tester, screenId=CCCC successfulIp= lastServerId=CCCC
[ Service ] [2017-10-05T11:37:34] debug: finished connectivity test

 

[Naf Birnirsk]

I notice in your log that it is trying to use port 24810. Perhaps you need to forward that port instead of 24800?

You can also combine your commands into one:

ssh -N -f -R 24810:127.0.0.1:24810 -L 24810:127.0.0.1:24810 … [central_server]