mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #81] Zeroconf defaults to address not available to clients #63
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#63
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @thirdwheel on GitHub (Jul 2, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/81
Operating Systems
Server: Windows 10 Pro
Client: Mac OS X 10.13.5
Barrier Version
2.1.0
Steps to reproduce bug
Barrier lists the IP addresses in its interface, the one in bold is the one that zeroconf uses.
Other info
I can work around this by setting the server IP in the client, but this is not an ideal scenario for me since DHCP is used across the board.
IP in green box is my LAN IP (ideal), dark yellow is my WiFi IP (OK but rather not) and red is the IP address of my Surface Pro's virtual WiFi adapter for Miracast (can't use!)
Log from Barrier showing it attempt to connect to the miracast IP and failing as it's not available outside my laptop
@walker0643 commented on GitHub (Jul 2, 2018):
Hi @thirdwheel - This is definitely a problem and I did start to work on it tonight. You're welcome to try the smartzeroconf branch and see if it fixes your issue. Unfortunately I have to be up in a few hours for work and I won't have time to test or implement the unix side, so let this be fair warning that it probably won't work yet!
Commit:
2d7818fe49@walker0643 commented on GitHub (Jul 11, 2018):
@thirdwheel - are you able to test the smartzeroconf branch to see if it fixes your problem?
@thirdwheel commented on GitHub (Jul 12, 2018):
Haven't had a chance to test it as yet, haven't been able to build it on Mac OS X:
@p12tic commented on GitHub (Jul 12, 2018):
Do you have Xcode and Xcode command line tools installed? The latter is installed automatically the first time you open Xcode IIRC.
@thirdwheel commented on GitHub (Jul 12, 2018):
@p12tic Yes. I'm running the beta at the moment (because I'm developing a mobile app and my phone is running iOS 12) so I don't know if that's likely to cause issues.
@p12tic commented on GitHub (Jul 12, 2018):
Could it be that you're hit by this one? https://stackoverflow.com/questions/32720564/cmake-broken-after-update-to-xcode-7-0#32721456
@thirdwheel commented on GitHub (Jul 13, 2018):
@p12tic No good sadly, followed the suggestion and the same error came up
@walker0643 commented on GitHub (Sep 8, 2018):
Closing for now. Please reopen if you have anything to add. Thanks!
@ghost commented on GitHub (Feb 15, 2019):
I have the same issue with the binary; I'll try building from the smarter zeroconf branch in a few.
In my case, Barrier ignores the
auto confsetting and always uses whatever address was in the text field when theauto confoption was selected. If I clear the text field and setauto confI get a message saying "Please fill in a hostname for the barrier client to connect to" when I hit theStartbutton. I'm guessing this means that the client can't figure out the server information from zeroconf, but who knows; the error message doesn't say why I need to fill in the field, and there's nothing in the logs about the error.@ghost commented on GitHub (Feb 15, 2019):
@walker0643 Confirmed that the
smartzeroconfdoes auto-discovery on OSX correctly, now. Any plans to merge that branch into default?@theofficialgman commented on GitHub (Dec 22, 2020):
Just wanted to bump this and say that this is still a desirable addition.