whyzzie 1 Posted April 11, 2018 Share Posted April 11, 2018 Hi, i have bought synergy 2 and successfully installed it on my mac. Now, want to connect to my rock64 sbc, successfully compiled synergy-core (as only armhf is available) and started with: ./synergy-core --client --no-daemon --version 192.168.0.101 which gives me only: [2018-04-11T17:54:33] NOTE: connecting to '192.168.0.101': 192.168.0.101:24800 [2018-04-11T17:54:33] WARNING: failed to connect to server: Connection refused Version says synergy-core 2.0.0, protocol version 1.6 but on my mac it is 2.0.9-stable is this the reason ? If so, how can i fix it ? Thanks Martin Link to post Share on other sites
jml 50 Posted April 11, 2018 Share Posted April 11, 2018 Probably not. That's an active reject from your host. Are you sure you don't have any firewall software running on the target? If you do a netstat, is 24800 listening? Link to post Share on other sites
whyzzie 1 Posted April 12, 2018 Author Share Posted April 12, 2018 (edited) Thx jml for ur answer. I've disabled firewall. And that is the list of ports, pretty many of them, i would say, tried the other ports too with same result: ╰─➤  sudo lsof -i -n -P | grep syner synergy-s 87677    wysiecki   8u  IPv4 0x2568ad7cfa25858d    0t0   TCP *:24802 (LISTEN) synergy-s 87677    wysiecki  10u  IPv4 0x2568ad7cfa258eed    0t0   TCP 127.0.0.1:24801 (LISTEN) synergy-s 87677    wysiecki  11u  IPv4 0x2568ad7ce821684d    0t0   TCP 127.0.0.1:24888 (LISTEN) synergy-s 87677    wysiecki  14u  IPv4 0x2568ad7d1441beed    0t0   TCP 127.0.0.1:50381->127.0.0.1:24888 (ESTABLISHED) synergy-s 87677    wysiecki  15u  IPv4 0x2568ad7d1441d1ad    0t0   TCP 127.0.0.1:24888->127.0.0.1:50381 (ESTABLISHED) synergy-s 87677    wysiecki  18u  IPv4 0x2568ad7ced62284d    0t0   TCP 127.0.0.1:24888->127.0.0.1:53653 (ESTABLISHED) synergy-s 87677    wysiecki  21u  IPv4 0x2568ad7ce821558d    0t0   TCP 192.168.0.101:53626->45.55.221.2:443 (ESTABLISHED) synergy-s 87677    wysiecki  23u  IPv4 0x2568ad7d03d78b0d    0t0   TCP 127.0.0.1:24888->127.0.0.1:53654 (ESTABLISHED) synergy-c 89443    wysiecki   0u  IPv4 0x2568ad7cfa25984d    0t0   TCP 127.0.0.1:24800 (LISTEN) synergy-c 89443    wysiecki  14u  IPv4 0x2568ad7d1441beed    0t0   TCP 127.0.0.1:50381->127.0.0.1:24888 (ESTABLISHED) synergy-c 89443    wysiecki  15u  IPv4 0x2568ad7d1441d1ad    0t0   TCP 127.0.0.1:24888->127.0.0.1:50381 (ESTABLISHED) synergy-c 89443    wysiecki  18u  IPv4 0x2568ad7d14b2a84d    0t0   TCP 127.0.0.1:24888->127.0.0.1:50383 (CLOSE_WAIT) synergy-c 89443    wysiecki  24u  IPv4 0x2568ad7d18496b0d    0t0   TCP 192.168.0.101:53625->159.203.127.129:443 (CLOSE_WAIT) synergy-c 89535    wysiecki  16u  IPv4 0x2568ad7d19310b0d    0t0   TCP 127.0.0.1:53653->127.0.0.1:24888 (ESTABLISHED) synergy-t 89540    wysiecki  17u  IPv4 0x2568ad7d1331884d    0t0   TCP 127.0.0.1:53654->127.0.0.1:24888 (ESTABLISHED) I have to mention, that synergy 1 was working on my setup, so in general, the network is working fine. thx Martin Edited April 12, 2018 by whyzzie Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted April 16, 2018 Synergy Team Share Posted April 16, 2018 On 4/11/2018 at 6:11 PM, jml said: If you do a netstat, is 24800 listening? With Synergy 2, it's actually 24802 that needs to be listening. Actually, 24800 is still used (as well as 24801), but only on local loopback for IPC. Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted April 16, 2018 Synergy Team Share Posted April 16, 2018 On 4/11/2018 at 5:04 PM, whyzzie said: successfully compiled synergy-core (as only armhf is available) Ah, never mind my last post. I see you're running the core directly. Is the other computer running via the config app? In which case it won't be listening on 24800, and 24802 actually uses a different (encrypted) protocol, they're not compatible. If you're running core directly on one computer, you have to do this on all computers. You can't mix auto and manual config modes. Link to post Share on other sites
whyzzie 1 Posted April 16, 2018 Author Share Posted April 16, 2018 Thx Nick for the answer, so finally, i have to compile the core version on my mac and wait till there is a arm64 build available, right ? Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted April 16, 2018 Synergy Team Share Posted April 16, 2018 4 minutes ago, whyzzie said: i have to compile the core version on my mac Actually, you can run core directly from the official bundle. Need help with this? 5 minutes ago, whyzzie said: wait till there is a arm64 build available Only if you want to use the auto config feature. Link to post Share on other sites
whyzzie 1 Posted April 16, 2018 Author Share Posted April 16, 2018 Ah ok ! "Actually, you can run core directly from the official bundle. Need help with this?" Would love to get a hint, how to do this. Have paid for the product, would be cool if i knew how to use it for my setup. THX Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted April 16, 2018 Synergy Team Share Posted April 16, 2018 6 minutes ago, whyzzie said: "Actually, you can run core directly from the official bundle. Need help with this?" Would love to get a hint, how to do this. Cool, assuming you already have the bundle installed on your Mac, you can run the core from the terminal: /Applications/Synergy.app/Contents/Resources/synergy-core --server Here are the full instructions for running Synergy Core in manual mode: https://github.com/symless/synergy-core/wiki/Command-Line You may need to allow Terminal in assistive devices (under Security & Privacy). Link to post Share on other sites
whyzzie 1 Posted April 16, 2018 Author Share Posted April 16, 2018 HAAAA ! it works, finally, thanks Nick, however, not only me for sure, would love to get a arm64 build Thank you 1 Link to post Share on other sites
whyzzie 1 Posted April 16, 2018 Author Share Posted April 16, 2018 (edited) one last question, promised :-) i have disabled and killed the original app, so nothing in tray, but still have 3 processes. - synergy-core (which is ok) - synergy-service - synergy-config Last two shouldn't be there, as started core from terminal with a config file. If i try to kill one of them, then they are standing up, and have sometimes two core processes. How can i stop this ? Thx Edited April 16, 2018 by whyzzie Link to post Share on other sites
whyzzie 1 Posted April 16, 2018 Author Share Posted April 16, 2018 also getting in console 2018-04-16 14:47:54.175 synergy-core[50002:15723789] pid(50002)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! however it does work Link to post Share on other sites
Synergy Team Nick Bolton 407 Posted April 16, 2018 Synergy Team Share Posted April 16, 2018 1 hour ago, whyzzie said: - synergy-core (which is ok) - synergy-service - synergy-config Last two shouldn't be there, as started core from terminal with a config file. If i try to kill one of them, then they are standing up, and have sometimes two core processes. On macOS? Run this command: launchctl unload /Library/LaunchAgents/com.symless.synergy.synergy-service.plist 56 minutes ago, whyzzie said: 2018-04-16 14:47:54.175 synergy-core[50002:15723789] pid(50002)/euid(501) is calling TIS/TSM in non-main thread environment, ERROR : This is NOT allowed. Please call TIS/TSM in main thread!!! Don't worry about that. It's a warning from macOS that doesn't seem to have any adverse effects. Link to post Share on other sites
TheDoctor 6 Posted April 16, 2018 Share Posted April 16, 2018 It compiles just fine. I have it running on a armhf and arm64 setup. Link to post Share on other sites
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now