github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #1188] ubuntu 20.04 not connecting with windows-10 64 bit #958

New issue

Open

opened 2026-05-05 07:19:57 -06:00 by gitea-mirror · 9 comments

gitea-mirror commented

2026-05-05 07:19:57 -06:00

Owner

Originally created by @ishika261 on GitHub (Jun 8, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1188

i wish to use ubuntu as my server and windows as a client. configuration and SSL keys matching is done. The client keeps shows barrier is running and Ubuntu(server) keeps showing barrier is starting. But I am not able to use the same mouse and keyboard for my client. Any help would be great! (p.s. I am new to ubuntu.)

Originally created by @ishika261 on GitHub (Jun 8, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1188 i wish to use ubuntu as my server and windows as a client. configuration and SSL keys matching is done. The client keeps shows barrier is running and Ubuntu(server) keeps showing barrier is starting. But I am not able to use the same mouse and keyboard for my client. Any help would be great! (p.s. I am new to ubuntu.)

gitea-mirror commented

2026-05-05 07:19:59 -06:00

Author

Owner

@ranjeetnooli commented on GitHub (Jun 10, 2021):

even i am having the same issue. i have ubuntu 20.04.2 LTS as server and windows as client. earlier it used to work but now it does not even connect. but when i use windows as server and ubuntu as client it does connect but cursor wont show up when i navigate to ubuntu machine from windows. earlier i have used barrier across my three systems, ubuntu as server and windows and kali linux as clients. never had a problem till now. :(

edit: i changed display server protocol from wayland to x11 and now barrier works (Server : windows, client: ubuntu) but not vice versa. i really want it work the other way.

@ranjeetnooli commented on GitHub (Jun 10, 2021): even i am having the same issue. i have ubuntu 20.04.2 LTS as server and windows as client. earlier it used to work but now it does not even connect. but when i use windows as server and ubuntu as client it does connect but cursor wont show up when i navigate to ubuntu machine from windows. earlier i have used barrier across my three systems, ubuntu as server and windows and kali linux as clients. never had a problem till now. :( edit: i changed display server protocol from wayland to x11 and now barrier works (Server : windows, client: ubuntu) but not vice versa. i really want it work the other way.

gitea-mirror commented

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

Author

Owner

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

I also have the same problem.
Server : openSUSE Leap 15.3 (x11)
Client : Windows 10

Like you, I can connect and it works fine with the following environment.
Server : Windows 10
Client : openSUSE Leap 15.3 (x11)

By the way, it worked fine in the previous environment.
Server : openSUSE Leap 15.2 (x11)
Client : Windows 10

@presire commented on GitHub (Jun 25, 2021): I also have the same problem. Server : openSUSE Leap 15.3 (x11) Client : Windows 10 Like you, I can connect and it works fine with the following environment. Server : Windows 10 Client : openSUSE Leap 15.3 (x11) By the way, it worked fine in the previous environment. Server : openSUSE Leap 15.2 (x11) Client : Windows 10

gitea-mirror commented

2026-05-05 07:20:02 -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.

@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. ![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)

gitea-mirror commented

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

Author

Owner

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

Yes it does work when u stop firewall.. but after a while again it disconnects.. Everytime it disconnects I need to stop and restart the firewall.

@ranjeetnooli commented on GitHub (Jun 26, 2021): Yes it does work when u stop firewall.. but after a while again it disconnects.. Everytime it disconnects I need to stop and restart the firewall.

gitea-mirror commented

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

Author

Owner

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

After a lot of trial and error, By the following step, I was able to get Barrier to work.
Βy the following steps, Barrier will run without stopping firewalld.

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>Barrier</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.
Or reboot your PC.

sudo firewall-cmd --reload
sudo systemctl restart firewalld

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

Try the settings above.

@presire commented on GitHub (Jun 26, 2021): After a lot of trial and error, By the following step, I was able to get Barrier to work. Βy the following steps, Barrier will run **_without stopping firewalld_**. 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>Barrier</short> <description>Share a mouse and keyboard on KVM.</description> <port protocol="tcp" port="24800"/> </service> ``` ![1](https://user-images.githubusercontent.com/82971634/123528006-1919a080-d71f-11eb-8c49-f76d8fbf224f.png) 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> ``` ![2](https://user-images.githubusercontent.com/82971634/123528016-377f9c00-d71f-11eb-976a-62061b1915f3.png) Finally, to reflect the firewall settings, run the following command. Or reboot your PC. sudo firewall-cmd --reload sudo systemctl restart firewalld There are some redundant parts, by the above steps, worked for Barrier and Synergy. Try the settings above.

gitea-mirror commented

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

Author

Owner

@ranjeetnooli commented on GitHub (Jun 27, 2021):

I don't know if this is ethical but this worked for me.

sudo firewall-cmd --permanent --add-port="24800/tcp"

after this it is working fine, automatically connects to both of my client machines ( windows and ubuntu )

@ranjeetnooli commented on GitHub (Jun 27, 2021): I don't know if this is ethical but this worked for me. sudo firewall-cmd --permanent --add-port="24800/tcp" after this it is working fine, automatically connects to both of my client machines ( windows and ubuntu )

gitea-mirror commented

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

Author

Owner

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

On ubuntu 20.04, Barrier was able to connect with firewall-cmd command.
I think that's the best (correct) way to do it.

sudo firewall-cmd --permanent --add-port="24800/tcp"
sudo firewall-cmd --reload

On my openSUSE Leap 15.3, I could not connect with firewall-cmd command.
(Maybe it is because I did not specify --zone=libvirt)

I would like to keep in mind that there are different methods for each distribution.

@presire commented on GitHub (Jun 27, 2021): On ubuntu 20.04, Barrier was able to connect with <code>firewall-cmd</code> command. I think that's the best (correct) way to do it. sudo firewall-cmd --permanent --add-port="24800/tcp" sudo firewall-cmd --reload On my openSUSE Leap 15.3, I could not connect with <code>firewall-cmd</code> command. (Maybe it is because I did not specify <code>--zone=libvirt</code>) I would like to keep in mind that there are different methods for each distribution.

gitea-mirror commented

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

Author

Owner

@ishika261 commented on GitHub (Jul 1, 2021):

On ubuntu 20.04, Barrier was able to connect with firewall-cmd command.
I think that's the best (correct) way to do it.
sudo firewall-cmd --permanent --add-port="24800/tcp"
sudo firewall-cmd --reload
On my openSUSE Leap 15.3, I could not connect with firewall-cmd command.
(Maybe it is because I did not specify --zone=libvirt)

I would like to keep in mind that there are different methods for each distribution.

firewall-cmd is not working for me . i am getting this sudo: firewall-cmd: command not found

what to do?

@ishika261 commented on GitHub (Jul 1, 2021): > On ubuntu 20.04, Barrier was able to connect with `firewall-cmd` command. > I think that's the best (correct) way to do it. > > ``` > sudo firewall-cmd --permanent --add-port="24800/tcp" > sudo firewall-cmd --reload > ``` > > > On my openSUSE Leap 15.3, I could not connect with `firewall-cmd` command. > (Maybe it is because I did not specify `--zone=libvirt`) > > I would like to keep in mind that there are different methods for each distribution. firewall-cmd is not working for me . i am getting this sudo: firewall-cmd: command not found what to do?

gitea-mirror commented

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

Author

Owner

@ranjeetnooli commented on GitHub (Jul 1, 2021):

On ubuntu 20.04, Barrier was able to connect with firewall-cmd command.
I think that's the best (correct) way to do it.
sudo firewall-cmd --permanent --add-port="24800/tcp"
sudo firewall-cmd --reload
On my openSUSE Leap 15.3, I could not connect with firewall-cmd command.
(Maybe it is because I did not specify --zone=libvirt)
I would like to keep in mind that there are different methods for each distribution.
firewall-cmd is not working for me . i am getting this sudo: firewall-cmd: command not found

what to do?

first install firewalld using,

$ sudo apt install firewalld

then start and enable firewalld

$ sudo systemctl start firewalld
$ sudo systemctl enable firewalld

then use this two commands

$ sudo firewall-cmd --permanent --add-port="24800/tcp"
$ sudo firewall-cmd --reload

@ranjeetnooli commented on GitHub (Jul 1, 2021): > > On ubuntu 20.04, Barrier was able to connect with `firewall-cmd` command. > > I think that's the best (correct) way to do it. > > ``` > > sudo firewall-cmd --permanent --add-port="24800/tcp" > > sudo firewall-cmd --reload > > ``` > > > > > > > > > > > > > > > > > > > > > > > > On my openSUSE Leap 15.3, I could not connect with `firewall-cmd` command. > > (Maybe it is because I did not specify `--zone=libvirt`) > > I would like to keep in mind that there are different methods for each distribution. > > firewall-cmd is not working for me . i am getting this sudo: firewall-cmd: command not found > > what to do? first install firewalld using, $ sudo apt install firewalld then start and enable firewalld $ sudo systemctl start firewalld $ sudo systemctl enable firewalld then use this two commands $ sudo firewall-cmd --permanent --add-port="24800/tcp" $ sudo firewall-cmd --reload

No labels

Rows
Columns