On 05/30/2014 07:47 AM, Liam Proven issued this missive:

Has anyone successfully got this working between two Fedora 20 machines?

The app says that the default port -- 24800 -- is not available. I don't know why, I can't see anything taking it in the firewall or anything, but anyway, changing to different ports doesn't seem to help... the client and server never connect.

Can anyone give me any pointers as to how to start to troubleshoot this?

I use synergy all the time between F19 and F20 machines (the console is currently on an F19 box).

On the F20 box (XFCE), right-click on the firewall icon and edit the current zone (I'm using "Public"). Click on the "Ports" tab, then click the "Add" button. In the pop-up, put in "24800" and the TCP protocol and click "Save". That should open up the port for now.

If you want this to be permanent, click on the "Configuration" dropdown, select "Permanent", and repeat the "Ports->Add" thing and save this configuration for future boots.

You'll need to have port 24800/TCP open on ALL machines involved in the synergy config. For full disclosure, here's my /etc/synergy.conf file (and yes, it hasn't changed in six years despite all the updates and rot that's gone on)

# Synergy configuration for Rick Stevens at AllDigital # Author: Rick Stevens, AllDigital Inc. # Last Edit: 29 February 2008

section: screens prophead: golem4: bigdog: end

section: aliases prophead: prophead.hci.com golem4: golem4.hci.com bigdog: bigdog.hci.com end

section: links # Screen configuration: # +-> golem4 (laptop) <--> prophead (main) <--> bigdog (Opteron) <-+ # +----------------------------------------------------------------+ prophead: right = bigdog left = golem4 bigdog: left = prophead right = golem4 golem4: left = bigdog right = prophead end

section: options switchDelay = 500 screenSaverSync = true end

---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Blessed be the peacekeepers, for they shall be shot at from - - both sides. - - -- A.M. Greeley - ----------------------------------------------------------------------

On 05/30/2014 10:16 AM, Liam Proven issued this missive:

On 30 May 2014 18:44, Rick Stevens ricks@alldigital.com wrote:

...

I use synergy all the time between F19 and F20 machines (the console is currently on an F19 box).

On the F20 box (XFCE), right-click on the firewall icon and edit the current zone (I'm using "Public"). Click on the "Ports" tab, then click the "Add" button. In the pop-up, put in "24800" and the TCP protocol and click "Save". That should open up the port for now.

If you want this to be permanent, click on the "Configuration" dropdown, select "Permanent", and repeat the "Ports->Add" thing and save this configuration for future boots.

You'll need to have port 24800/TCP open on ALL machines involved in the synergy config. For full disclosure, here's my /etc/synergy.conf file (and yes, it hasn't changed in six years despite all the updates and rot that's gone on)

Reassured that it should work, I'll continue to play. I added the port reservation on both sides, but the client still says it failed to connect - connection refused. Most annoying.

It might be something to do with the work network config - I'll have to ask...

It smells suspiciously like the synergy server isn't running on the machine with the keyboard and mouse. On the server as the root user, try:

netstat -lpnt | grep synergy

and verify that synergys is running and listening on TCP port 24800:

[root@prophead ~]# netstat -lpnt | grep synergy tcp 0 0 0.0.0.0:24800 0.0.0.0:* LISTEN 3988/synergys

If it isn't, try to start it as the desktop user--NOT root. If it won't start, figure out why first. Again, as the desktop user, you can try to start it like:

/usr/bin/synergys -f

That will start it in the foreground and should show you any errors it may be generating (or you can just check /var/log/messages for previous runs). Get those issues sorted first off.

Most likely it's a typo in the config file, either

$HOME/.synergy.conf (the first place it looks) or /etc/synergy.conf

Note that if you're using "/etc/synergy.conf", make sure it has world- read privileges as the desktop user MUST be able to read it.

Here's how I have them start up in my environment:

"prophead" (F19, XFCE) is the server with the keyboard and mouse. In the XFCE config (Applications Menu->Settings->Session and Startup->Application Autostart tab), I have it automatically start the Synergy server using this command:

/usr/bin/synergys

(and I use a global "/etc/synergy.conf" file). On the clients (e.g. "golem4", my laptop), I have a similar autostart but the command starts the client:

/usr/bin/synergyc -d ERROR 192.168.1.50

where 192.168.1.50 is the IP address of the Synergy server (prophead).

Hope that helps. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Change is inevitable, except from a vending machine. - ----------------------------------------------------------------------

On 06/02/2014 08:57 AM, Liam Proven issued this missive:

On 30 May 2014 19:56, Rick Stevens ricks@alldigital.com wrote:

...

Hope that helps.

Thanks very much for the exhaustive reply!

Sadly not. I suspect it might be something to do with the odd network configuration at $JOB; my machines both have 2 different IP addresses on 2 different subnets.

I've tried both IPs, although on one, they're on different 3rd octets and can't ping one another.

I've tried running Synergy with ``sudo``. No difference.

I've tried bumping the port # up from 24800 to 24801; no difference. (Obviously I changed it on both ends.)

I've tried picking a random high port (42424); no difference.

I've checked with ``lsof'' that nothing's using the standard ports - it isn't.

I'm out of ideas, TBH.

Ok, the machines MUST be able to ping each other. If they can't, you need to get that sorted first. If they have funky network configs, you should try to ping via IP addresses instead of host names and see if that works and you may have to add some routes to get it functional. Note that the Synergy configs will work with IPs or hostnames (or both), but the machines involved MUST be able to talk to each other.

---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Okay, who put a "stop payment" on my reality check? - ----------------------------------------------------------------------

On 06/02/2014 02:13 PM, Liam Proven issued this missive:

On 2 June 2014 19:04, Rick Stevens ricks@alldigital.com wrote:

...

Ok, the machines MUST be able to ping each other. If they can't, you need to get that sorted first. If they have funky network configs, you should try to ping via IP addresses instead of host names and see if that works and you may have to add some routes to get it functional. Note that the Synergy configs will work with IPs or hostnames (or both), but the machines involved MUST be able to talk to each other.

Pinging works OK on the 192.168.v.w subnet that they're both in. But looking at ifconfig, the "real" address is a 10.x.y.z one and the 192.* one is... something else. They can ping each other on the 192.* address but not on the 10.* address.

I can get the server to start on the host (i.e. with k/b & mouse) but the remote machine I want to control says it can't connect.

On the server, do the "netstat -lpnt" and make sure synergys is listening on either 0.0.0.0:24800 or 192.168.v.w:24800. On my machine:

# netstat -lpnt | grep synergy tcp 0 0 0.0.0.0:24800 0.0.0.0:* LISTEN 3988/synergys

The "0.0.0.0:24800" means that it's listening on all the IP addresses my machine has and would allow any client to connect as long as the client can connect to one of the addresses my machine uses. Think of the "0.0.0.0" bit as a wildcard.

On the client, make sure you run

synergyc -d ERROR 192.168.v.w

where "192.168.v.w" is the address of the server on that 192.168 network that the two machines share.

If you don't specify the server's IP address to the client, then the client will probably be trying to connect over the OTHER network, and no, that won't work. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 22643734 Yahoo: origrps2 - - - - Treat each day as if it's your last...a lot of crying and whining - - usually gets you what you want! -- Sam Sledge - ----------------------------------------------------------------------

On 3 June 2014 00:02, Rick Stevens ricks@alldigital.com wrote:

If you don't specify the server's IP address to the client, then the client will probably be trying to connect over the OTHER network, and no, that won't work.

Success!

It was the firewall in the end; Synergy's error message is misleading. It says "no route to host", but there is a route, it's just that nobody's able to listen.

Procedure, in case it helps anyone:

[1] I moved the 2nd machine onto a different network port, getting it on the same subnet. No difference.

[2] I investigated why I had this 2nd network interface, virbr0:

http://nixcraft.com/showthread.php/15760-Remove-Virtual-Interface

So I got rid of it:

http://www.cyberciti.biz/faq/linux-kvm-disable-virbr0-nat-interface/

No difference. Rebooted, still no difference.

[3] I checked out that there _was_ a route. There was. No hops, 2 machines on same 10.x.y.z subnet. I even added a hostname to /etc/hosts. No difference.

[4] So then I thought the "no route to host" message must be spurious, and finally Googled it.

https://ask.fedoraproject.org/en/question/42001/synergy-no-route-to-host-but...

And this post is correct. Although there are no firewall rules visible in the GUI, they _are_ there and the port _was_ being blocked.

Open the port and it worked instantly.