[GH-ISSUE #1212] Unable to connect on Server [ openSUSE Leap 15.3 ] and Client [ Windows10 ] with barrier 2.3.3 #974

New issue

Closed

opened 2026-05-05 07:20:40 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 07:20:40 -06:00

Owner

Originally created by @presire on GitHub (Jun 24, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1212

Nice to meet you.

As for the title, when the server is openSUSE Leap 15.3 and the client is Windows 10, I cannot connect with barrier 2.3.3.
Both pings are working.

However, when the server is Windows 10 and the client is openSUSE Leap 15.3, I can connect with barrier 2.3.3. (Why?? )
(I also tried Synergy, had the same problem with Synergy.)

The following is the status of barrier when the server is openSUSE Leap 15.3 and the client is Windows 10.
(The image above shows openSUSE Leap 15.3, The image below shows Windows 10)

Is there any way to solve this problem?

Thank you very much for your help.

Originally created by @presire on GitHub (Jun 24, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1212 Nice to meet you. As for the title, when the server is openSUSE Leap 15.3 and the client is Windows 10, I cannot connect with barrier 2.3.3. Both pings are working. However, when the server is Windows 10 and the client is openSUSE Leap 15.3, I can connect with barrier 2.3.3. (Why?? ) (I also tried Synergy, had the same problem with Synergy.) The following is the status of barrier when the server is openSUSE Leap 15.3 and the client is Windows 10. (The image above shows openSUSE Leap 15.3, The image below shows Windows 10) ![Screenshot_20210625_041803](https://user-images.githubusercontent.com/82971634/123320531-d7e18f00-d56c-11eb-9bc4-1c232290f68b.png) ![無題](https://user-images.githubusercontent.com/82971634/123320538-d912bc00-d56c-11eb-9fb1-e8ea422607e0.png) Is there any way to solve this problem? Thank you very much for your help.

gitea-mirror closed this issue

2026-05-05 07:20:41 -06:00

gitea-mirror commented

2026-05-05 07:20:45 -06:00

Author

Owner

@presire commented on GitHub (Jun 26, 2021):

I don't know if this is the right way,
when I stopped firewalld, Barrier worked.

Command :
sudo systemctl stop firewalld

Server : openSUSE Leap 15.3 (Plasma x11)
Client : Windows 10

Perhaps, I think that this is a KVM issue.
On VMware, both are working fine.

However, since disabling the firewall is not a good idea
Please let me know if there is another way.

@presire commented on GitHub (Jun 26, 2021): I don't know if this is the right way, when I stopped firewalld, Barrier worked. Command : sudo systemctl stop firewalld Server : openSUSE Leap 15.3 (Plasma x11) Client : Windows 10 ![ksnip_20210626-090741](https://user-images.githubusercontent.com/82971634/123496729-83b9d600-d664-11eb-87ad-c80f69b20b29.png) ![無題](https://user-images.githubusercontent.com/82971634/123496731-84eb0300-d664-11eb-846f-b864398a91c1.png) Perhaps, I think that this is a KVM issue. On VMware, both are working fine. However, since disabling the firewall is not a good idea Please let me know if there is another way.

gitea-mirror commented

2026-05-05 07:20:46 -06:00

Author

Owner

@presire commented on GitHub (Jun 26, 2021):

I described it in my other post, but I'll describe it here as well.
I'll postpone the close for a little while longer.

After a lot of trial and error,
By editing the following step, I was able to get Barrier to work.

First, create the /usr/lib/firewalld/services/barrier.xml file. (You may not need this file)

Command :
sudo nano /usr/lib/firewalld/services/barrier.xml

<?xml version="1.0" encoding="utf-8"?>
<service>
   <short>Synergy</short>
   <description>Share a mouse and keyboard on KVM.</description>
   <port protocol="tcp" port="24800"/>
</service>

Next, edit the /usr/lib/firewalld/zones/libvirt.xml file.
Above </zone>, add <port port="24800" protocol="tcp"/>.

Command :
sudo nano /usr/lib/firewalld/zones/libvirt.xml

<?xml version="1.0" encoding="utf-8"?>
<zone target="ACCEPT">
   ...
   ...
   <port port="24800" protocol="tcp"/>
</zone>

Finally, to reflect the firewall settings, run the following command.

sudo firewall-cmd --reload
sudo systemctl restart firewalld

There are some redundant parts,
by the above steps, worked for Barrier and Synergy.

@presire commented on GitHub (Jun 26, 2021): I described it in my other post, but I'll describe it here as well. **I'll postpone the close for a little while longer.** After a lot of trial and error, By editing the following step, I was able to get Barrier to work. First, create the ```/usr/lib/firewalld/services/barrier.xml``` file. (**You may not need this file**) Command : sudo nano /usr/lib/firewalld/services/barrier.xml ``` <?xml version="1.0" encoding="utf-8"?> <service> <short>Synergy</short> <description>Share a mouse and keyboard on KVM.</description> <port protocol="tcp" port="24800"/> </service> ``` Next, edit the ```/usr/lib/firewalld/zones/libvirt.xml``` file. Above ```</zone>```, add ```<port port="24800" protocol="tcp"/>```. Command : sudo nano /usr/lib/firewalld/zones/libvirt.xml ``` <?xml version="1.0" encoding="utf-8"?> <zone target="ACCEPT"> ... ... <port port="24800" protocol="tcp"/> </zone> ``` Finally, to reflect the firewall settings, run the following command. sudo firewall-cmd --reload sudo systemctl restart firewalld There are some redundant parts, by the above steps, worked for Barrier and Synergy.

gitea-mirror referenced this issue

2026-05-05 08:00:26 -06:00

[PR #979] [MERGED] Use ansi codepage for internal multibyte strings on windows (fixes #976, fixes #974, fixes #444) #1727