github-starred/barrier

Fork 0

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

[GH-ISSUE #740] Feature Request: swap Client and Server #579

New issue

Open

opened 2026-05-05 06:42:47 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 06:42:47 -06:00

Owner

Originally created by @sybrenstuvel on GitHub (Jun 8, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/740

Operating Systems

Any OS, as this is about a fundamental design choice in Barrier.

Barrier Version

2.3.2

Steps to reproduce bug

Have computer A with mouse and keyboard.
Have computer B without mouse or keyboard.
Try to use Barrier to control computer B from computer A.
The Client/Server model of Barrier makes this impossible, as it requires clicking around on the Client side to initiate the connection with a Server. This is not possible, though, as computer B has no keyboard/mouse.

I expected computer B (the one without peripherals) to be waiting for connections, and computer A (the one with peripherals) to require clicking around to create the connection.

Other info

Does this bug prevent you from using Barrier entirely? Yes

My use case is that I want to be able to control a computer that only has a monitor, no keyboard/mouse. In some cases I want to excert control from my desktop machine, in other cases from my laptop.

Originally created by @sybrenstuvel on GitHub (Jun 8, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/740 ### Operating Systems ### Any OS, as this is about a fundamental design choice in Barrier. ### Barrier Version ### 2.3.2 ### Steps to reproduce bug ### 1. Have computer A with mouse and keyboard. 2. Have computer B without mouse or keyboard. 3. Try to use Barrier to control computer B from computer A. 4. The Client/Server model of Barrier makes this impossible, as it requires clicking around on the Client side to initiate the connection with a Server. This is not possible, though, as computer B has no keyboard/mouse. I expected computer B (the one without peripherals) to be waiting for connections, and computer A (the one with peripherals) to require clicking around to create the connection. ### Other info ### * Does this bug prevent you from using Barrier entirely? **Yes** My use case is that I want to be able to control a computer that only has a monitor, no keyboard/mouse. In some cases I want to excert control from my desktop machine, in other cases from my laptop.

gitea-mirror commented

2026-05-05 06:42:51 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 20, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 20, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:42:53 -06:00

Author

Owner

@sybrenstuvel commented on GitHub (Sep 24, 2020):

I wouldn't mind a response from the devteam here. This message is just to keep the auto-closing bot at bay.

@sybrenstuvel commented on GitHub (Sep 24, 2020): I wouldn't mind a response from the devteam here. This message is just to keep the auto-closing bot at bay.

gitea-mirror commented

2026-05-05 06:42:55 -06:00

Author

Owner

@johnhamelink commented on GitHub (Oct 3, 2020):

I also have this issue; I have an ultrawide monitor which I can split in half in order to display two machines simultaneously on the same screen (no bezel!).

@johnhamelink commented on GitHub (Oct 3, 2020): I also have this issue; I have an ultrawide monitor which I can split in half in order to display two machines simultaneously on the same screen (no bezel!).

gitea-mirror commented

2026-05-05 06:42:56 -06:00

Author

Owner

@haworthiopsis commented on GitHub (Sep 13, 2022):

There's really no need for that. I use barrier in exact same fashion as OP: have a miniPC connected only with screen and I control it using other PC. On a client you just need to setup OS (obviously keyboard will be necessary) and configure barrier client as a service. Later there's no need for mouse or keyboard. Client will connect whenever it will detect server present on the network with preconfigured IP.

The only downside I see is when you change server IP you also have to change that setting in client config because as of now there's no way to specify alternative servers. This is discussed here:

https://github.com/input-leap/input-leap/issues/246

@haworthiopsis commented on GitHub (Sep 13, 2022): There's really no need for that. I use barrier in exact same fashion as OP: have a miniPC connected only with screen and I control it using other PC. On a client you just need to setup OS (obviously keyboard will be necessary) and configure barrier client as a service. Later there's no need for mouse or keyboard. Client will connect whenever it will detect server present on the network with preconfigured IP. The only downside I see is when you change server IP you also have to change that setting in client config because as of now there's no way to specify alternative servers. This is discussed here: https://github.com/input-leap/input-leap/issues/246

gitea-mirror commented

2026-05-05 06:42:57 -06:00

Author

Owner

@Cronvs commented on GitHub (Sep 2, 2023):

Ditto. I have a similiar issue, due to my LAN config with VLANs only the PC with mouse and keyboard can initiate handshakes across VLANs and disallows vice versa. With computer B as client and unable to create handshake it would be impossible to use as is for me. But not sure how feasible the request is.

@Cronvs commented on GitHub (Sep 2, 2023): Ditto. I have a similiar issue, due to my LAN config with VLANs only the PC with mouse and keyboard can initiate handshakes across VLANs and disallows vice versa. With computer B as client and unable to create handshake it would be impossible to use as is for me. But not sure how feasible the request is.