github-starred/barrier

Fork 0

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

[GH-ISSUE #2101] Does Barrier work when one system is using lan? #1518

New issue

Open

opened 2026-05-05 07:54:15 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

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

Owner

Originally created by @heyyyheyyy on GitHub (Oct 8, 2024).
Original GitHub issue: https://github.com/debauchee/barrier/issues/2101

What happened?

Win 10 Pro 22H2
Client is on Mac M1 Sequoia 15.0.1

Works fine when both are connected using Wifi. When the Mac gets connected using Lan cable, barrier wont work either with Win or Mac as server. When Win is server barrier runs but Mac client gets stuck at "Barrier is Starting" with the log saying "timed out". Same thing happens when making the Mac the server with the Windows client getting stuck at "barrier is starting" and the connection "timing out". The IP address is updated when using the LAN cable.

Have tried enable/disable ssl, resetting server config, saving and using manual config on both Windows and Mac as servers. Verifying the correct IP on both, Allowing the system through both systems firewalls and re-installing barrier.

I did note that IP for the Mac using LAN is ".168.1.6" not sure if that has anything to do with it.

Please help. Thank you!

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

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

Windows, macOS

What OS versions are you using?

Win 10 Pro 22H2
Client is on Mac M1 Sequoia 15.0.1

Relevant log output

Any other information

No response

Originally created by @heyyyheyyy on GitHub (Oct 8, 2024). Original GitHub issue: https://github.com/debauchee/barrier/issues/2101 ### What happened? Win 10 Pro 22H2 Client is on Mac M1 Sequoia 15.0.1 Works fine when both are connected using Wifi. When the Mac gets connected using Lan cable, barrier wont work either with Win or Mac as server. When Win is server barrier runs but Mac client gets stuck at "Barrier is Starting" with the log saying "timed out". Same thing happens when making the Mac the server with the Windows client getting stuck at "barrier is starting" and the connection "timing out". The IP address is updated when using the LAN cable. Have tried enable/disable ssl, resetting server config, saving and using manual config on both Windows and Mac as servers. Verifying the correct IP on both, Allowing the system through both systems firewalls and re-installing barrier. I did note that IP for the Mac using LAN is ".168.1.6" not sure if that has anything to do with it. Please help. Thank you! ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) Windows, macOS ### What OS versions are you using? Win 10 Pro 22H2 Client is on Mac M1 Sequoia 15.0.1 ### Relevant log output ```shell - ``` ### Any other information _No response_

gitea-mirror commented

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

Author

Owner

@RoyeA commented on GitHub (Oct 22, 2024):

I have a configuration that works over both WiFi and Lan. to resolve the issue I had to make sure I can use the command ping, and ping from either machine to all others.
As soon as ping works, this will work too.

@RoyeA commented on GitHub (Oct 22, 2024): I have a configuration that works over both WiFi and Lan. to resolve the issue I had to make sure I can use the command ping, and ping from either machine to all others. As soon as ping works, this will work too.

gitea-mirror commented

2026-05-05 07:54:21 -06:00

Author

Owner

@Ayx03 commented on GitHub (Nov 25, 2024):

You'll have to make sure both devices are in the same LAN (or not in the same level but router firewall rules allowed access), you can see WiFi as a virtual network cable and as long as they're connected to the same router/carrier box they should be able to ping each other assume ICMP something is not disabled in devices' firewall and the router/carrier box didn't block access between devices(known as AP隔离/AP isolation?). I have my desktop connected via ethernet cable and laptop connected via WiFi and it worked fine, I'm using the successor of this project - InputLeap tho, you can find the link to it in the releases.

@Ayx03 commented on GitHub (Nov 25, 2024): You'll have to make sure both devices are in the same LAN (or not in the same level but router firewall rules allowed access), you can see WiFi as a virtual network cable and as long as they're connected to the same router/carrier box they should be able to ping each other assume ICMP something is not disabled in devices' firewall and the router/carrier box didn't block access between devices(known as AP隔离/AP isolation?). I have my desktop connected via ethernet cable and laptop connected via WiFi and it worked fine, I'm using the successor of this project - InputLeap tho, you can find the link to it in the releases.

No labels

Rows
Columns