Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does Barrier work when one system is using lan? #2101

Open
heyyyheyyy opened this issue Oct 8, 2024 · 2 comments
Open

Does Barrier work when one system is using lan? #2101

heyyyheyyy opened this issue Oct 8, 2024 · 2 comments

Comments

@heyyyheyyy
Copy link

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

@RoyeA
Copy link

RoyeA commented 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.

@Ayx03
Copy link

Ayx03 commented 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants