~Frank Posted November 1, 2017 Share Posted November 1, 2017 Why does synergy try and contact 10.42.0.2:24802 ?? This is not even on my private LAN - I am 192.168.101/24 /var/log/messages: Nov 1 07:41:04 fedora1 synergy-service[1424]: [ Router ] [2017-11-01T07:41:04] debug: Connection to 10.42.0.2:24802 timed out Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted November 1, 2017 Synergy Team Share Posted November 1, 2017 6 minutes ago, ~Frank said: Why does synergy try and contact 10.42.0.2:24802 ?? This is not even on my private LAN - I am 192.168.101/24 /var/log/messages: Nov 1 07:41:04 fedora1 synergy-service[1424]: [ Router ] [2017-11-01T07:41:04] debug: Connection to 10.42.0.2:24802 timed out Don't worry. It simply tries to connect to all IPs that your other machine has assigned. Often, your computers will have IPs assigned that you're not even aware of. Link to comment Share on other sites More sharing options...
~Frank Posted November 1, 2017 Author Share Posted November 1, 2017 Figured it out - I had an OpenVPN tunnel running and it was on the 10.42 network. I guess Synergy was just reaching out to see what was out there... Link to comment Share on other sites More sharing options...
Synergy Team Nick Bolton Posted November 2, 2017 Synergy Team Share Posted November 2, 2017 12 hours ago, ~Frank said: Figured it out - I had an OpenVPN tunnel running and it was on the 10.42 network. I guess Synergy was just reaching out to see what was out there... Yeah, that's the thing with network configs, you often never really know exactly what IP will work... so Synergy 2 tries them all! It's a bit of a golden hammer approach, but it seems to be improving the connection rates. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.