github-starred/barrier

Fork 0

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

[GH-ISSUE #1745] Multiple IP Addresses #1288

New issue

Open

opened 2026-05-05 07:42:08 -06:00 by gitea-mirror · 10 comments

gitea-mirror commented

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

Owner

Originally created by @quartzeye on GitHub (Aug 15, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1745

What happened?

I have Barrier installed on (3) computers, (2) Win10 and (1) Fedora. On all three I have VMware workstation and OpenVPN for vpn access to work and customers. That yields multiple real and virtual network devices with their own IP LAN segment on each computer. Barrier will not align with the physical network adapter and the local IP LAN segment and seems to be binding to the VMware virtual bridge as that is the IP that is bold in the configuration panel on each computer.

Entering the IP address in the configuration panel does not for alignment either. The documentation is woefully absent on how to force Barrier to bind to a specific LAN segment that all my computers are attached to. Could someone please articulate in explicit detail how to manually force Barrier to attach to and communicate with other computers on a specific LAN segment rather than allowing it to randomly select one that is incorrect.

I suspect I will need a custom barrier.conf file but again the documentation seems to be lacking in detail and examples on how to configure barrier for networking.

I would appreciate clarity and guidance on how to configure Barrier to work correctly with my environment or at least an explanation on whether forced alignment to specific LAN segments is supported.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

From the Github page

What OSes are you seeing the problem on? (Check all that apply)

Linux, Windows

What OS versions are you using?

Win10 and Fedora 35

Relevant log output

No response

Any other information

No response

Originally created by @quartzeye on GitHub (Aug 15, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1745 ### What happened? I have Barrier installed on (3) computers, (2) Win10 and (1) Fedora. On all three I have VMware workstation and OpenVPN for vpn access to work and customers. That yields multiple real and virtual network devices with their own IP LAN segment on each computer. Barrier will not align with the physical network adapter and the local IP LAN segment and seems to be binding to the VMware virtual bridge as that is the IP that is bold in the configuration panel on each computer. Entering the IP address in the configuration panel does not for alignment either. The documentation is woefully absent on how to force Barrier to bind to a specific LAN segment that all my computers are attached to. Could someone please articulate in explicit detail how to manually force Barrier to attach to and communicate with other computers on a specific LAN segment rather than allowing it to randomly select one that is incorrect. I suspect I will need a custom barrier.conf file but again the documentation seems to be lacking in detail and examples on how to configure barrier for networking. I would appreciate clarity and guidance on how to configure Barrier to work correctly with my environment or at least an explanation on whether forced alignment to specific LAN segments is supported. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? From the Github page ### What OSes are you seeing the problem on? (Check all that apply) Linux, Windows ### What OS versions are you using? Win10 and Fedora 35 ### Relevant log output _No response_ ### Any other information _No response_

gitea-mirror commented

2026-05-05 07:42:11 -06:00

Author

Owner

@wzh1895 commented on GitHub (Sep 11, 2022):

I have the same problem and would appreciate any input from the developer. Thanks!

@wzh1895 commented on GitHub (Sep 11, 2022): I have the same problem and would appreciate any input from the developer. Thanks!

gitea-mirror commented

2026-05-05 07:42:12 -06:00

Author

Owner

@gbdrbob commented on GitHub (Oct 27, 2022):

I also have this issue. My barrier server has two IP adresses as it runs zerotier. I need barrier to bind to the local LAN IP but it always binds to the zerotier interface.

The only workaround I have found is to disconnect from zerotier, launch barrier and then reconnect, so barrier only sees the local LAN interface. Using the documented --address command line option doesn't seem to do anything at all, barrier still binds to the wrong interface.

@gbdrbob commented on GitHub (Oct 27, 2022): I also have this issue. My barrier server has two IP adresses as it runs zerotier. I need barrier to bind to the local LAN IP but it always binds to the zerotier interface. The only workaround I have found is to disconnect from zerotier, launch barrier and then reconnect, so barrier only sees the local LAN interface. Using the [documented](https://github.com/debauchee/barrier-wiki/blob/master/Command-Line.md) --address command line option doesn't seem to do anything at all, barrier still binds to the wrong interface.

gitea-mirror commented

2026-05-05 07:42:13 -06:00

Author

Owner

@Am0rphous commented on GitHub (Mar 13, 2023):

Same. It is very frustrating that the app doesn't have the option to prohibit barrier to run on specific interfaces.. 😖

@Am0rphous commented on GitHub (Mar 13, 2023): Same. It is very frustrating that the app doesn't have the option to prohibit barrier to run on specific interfaces.. 😖

gitea-mirror commented

2026-05-05 07:42:15 -06:00

Author

Owner

@quartzeye commented on GitHub (Mar 13, 2023):

I found the secret is making sure that you build out a .conf/.sgc file properly and set Barrier to auto-start with that configuration. While I have no confirmed it in the documents, I believe that if you have the server setup to use a valid configuration that encompasses your entire environment that the clients pull those setting when they auto-start and have auto-config turned on.

To that end I have gotten, through trial and a lot of error, a four system configuration that works seamlessly. Adding in Voicemeeter and I now have one computer for all streaming with my mouse, keyboard and headset connected that seemlessly proxies bi-directional audio, KVM, and clipboard across all my systems. Both Windows and Linux. Although Linux audio has an additional need for JACK audio to work.

@quartzeye commented on GitHub (Mar 13, 2023): I found the secret is making sure that you build out a .conf/.sgc file properly and set Barrier to auto-start with that configuration. While I have no confirmed it in the documents, I believe that if you have the server setup to use a valid configuration that encompasses your entire environment that the clients pull those setting when they auto-start and have auto-config turned on. To that end I have gotten, through trial and a lot of error, a four system configuration that works seamlessly. Adding in Voicemeeter and I now have one computer for all streaming with my mouse, keyboard and headset connected that seemlessly proxies bi-directional audio, KVM, and clipboard across all my systems. Both Windows and Linux. Although Linux audio has an additional need for JACK audio to work.

gitea-mirror commented

2026-05-05 07:42:15 -06:00

Author

Owner

@Quadstronaut commented on GitHub (Dec 4, 2023):

I installed virtualbox and Barrier is defaulting to the virtual network adapter, which is completely useless for the server. I'd love to see this made configurable.

@Quadstronaut commented on GitHub (Dec 4, 2023): I installed virtualbox and Barrier is defaulting to the virtual network adapter, which is completely useless for the server. I'd love to see this made configurable.

gitea-mirror commented

2026-05-05 07:42:17 -06:00

Author

Owner

@hiuling commented on GitHub (Jan 3, 2024):

i am using windows 11 as server side, have 3 different ip so i set the designated ip in setting->networking->address. and disabled SSL
then arch linux as client side, also set the my arch ip in the setting->networking->address. and disabled SSL.
then as client i also input the designated ip set in first step as the server ip. both the ip need to be in the same subnet.
the connection is successful
however whenever my cursor gets into the client side, it sticks to one of the corner then wont move again.

@hiuling commented on GitHub (Jan 3, 2024): i am using windows 11 as server side, have 3 different ip so i set the designated ip in setting->networking->address. and disabled SSL then arch linux as client side, also set the my arch ip in the setting->networking->address. and disabled SSL. then as client i also input the designated ip set in first step as the server ip. both the ip need to be in the same subnet. the connection is successful however whenever my cursor gets into the client side, it sticks to one of the corner then wont move again.

gitea-mirror commented

2026-05-05 07:42:17 -06:00

Author

Owner

@hiuling commented on GitHub (Jan 3, 2024):

however whenever my cursor gets into the client side, it sticks to one of the corner then wont move again.

for this problem its due to the display is enlarged by 125%, after change back to 100% everything works fine.

@hiuling commented on GitHub (Jan 3, 2024): >however whenever my cursor gets into the client side, it sticks to one of the corner then wont move again. for this problem its due to the display is enlarged by 125%, after change back to 100% everything works fine.

gitea-mirror commented

2026-05-05 07:42:18 -06:00

Author

Owner

@CPioGH2002 commented on GitHub (Mar 17, 2025):

Using the documented --address command line option doesn't seem to do anything at all, barrier still binds to the wrong interface.

If it's still relevant, a note on how to use the command line options from here:

Keep in mind that you have to start barrier via "barriers" (without the quotes) to make sure the server starts and accepts the options that follow. If you just use "barrier" (without the "s" = GUI-based interface) and try to add the options, they are not accepted at all, which is what you might be describing.

Background re: the different names: https://github.com/debauchee/barrier/wiki/Troubleshooting#linuxunixmacos

For example, barriers -f --no-tray --debug INFO --name [server name] -c /home/[user]/barriercfg.conf -a 192.168.1.1:24800 will properly bind to 192.168.1.1 as opposed to using all available network interfaces (which is what happens if no addresses are defined).

One can check the result with ss -tlnp | grep barriers and see how the "all" definition of 0.0.0.0 changes to the one you have defined via the options (=192.168.1.1 in the above example).

@CPioGH2002 commented on GitHub (Mar 17, 2025): > Using the [documented](https://github.com/debauchee/barrier-wiki/blob/master/Command-Line.md) --address command line option doesn't seem to do anything at all, barrier still binds to the wrong interface. If it's still relevant, a note on how to use the command line options from [here](https://github.com/debauchee/barrier-wiki/blob/master/Command-Line.md#server_cli): Keep in mind that you have to start barrier via "**barriers**" (without the quotes) to make sure the _server_ starts and accepts the options that follow. If you just use "barrier" (without the "s" = GUI-based interface) and try to add the options, they are not accepted at all, which is what you might be describing. > Background re: the different names: https://github.com/debauchee/barrier/wiki/Troubleshooting#linuxunixmacos For example, `barriers -f --no-tray --debug INFO --name [server name] -c /home/[user]/barriercfg.conf -a 192.168.1.1:24800` will properly bind to `192.168.1.1` as opposed to using all available network interfaces (which is what happens if no addresses are defined). One can check the result with `ss -tlnp | grep barriers` and see how the "all" definition of `0.0.0.0` changes to the one you have defined via the options (=`192.168.1.1` in the above example).

gitea-mirror commented

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

Author

Owner

@nbolton commented on GitHub (Mar 17, 2025):

If there is still interest in this feature, please cross-post this to Deskflow or Input Leap as Barrier is no longer in development.

https://github.com/deskflow/deskflow
https://github.com/input-leap/input-leap

Both are compatible with Barrier client/server so you can try on one of your computers.

@nbolton commented on GitHub (Mar 17, 2025): If there is still interest in this feature, please cross-post this to Deskflow or Input Leap as Barrier is no longer in development. https://github.com/deskflow/deskflow https://github.com/input-leap/input-leap Both are compatible with Barrier client/server so you can try on one of your computers.

gitea-mirror commented

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

Author

Owner

@CPioGH2002 commented on GitHub (Mar 18, 2025):

Thanks for the heads-up. I will certainly check them both out. :-)

@CPioGH2002 commented on GitHub (Mar 18, 2025): Thanks for the heads-up. I will certainly check them both out. :-)