mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #789] mac server, linux client: new client is unresponsive #623
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#623
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 @nmarasoiu on GitHub (Jul 10, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/789
Operating Systems
Server: MacOS Catalina (firewall off, SSL off in barrier)
Client: Ubuntu 20.04 LTS (firewall off)
Barrier Version
2.3.2
Steps to reproduce bug
configure server to have the client on the left, put the client hostname
configure server ip = the thunderbolt bridge ip
started server
configured client to server 169.254 thunderbolt ip
started client
telnet from client working to server ip 169.254.155.198 24800
client is "barrier is starting" for ever
pls see the logs below
trying with the ethernet IPs 192.168 instead of the thunderbolt ones is not different in any way.
Other info
Logs:
[2020-07-10T21:27:17] DEBUG: Opening new socket: C4398D70
[2020-07-10T21:27:17] NOTE: accepted client connection
[2020-07-10T21:27:29] DEBUG: Opening new socket: C350DDE0
[2020-07-10T21:27:29] NOTE: accepted client connection
[2020-07-10T21:27:33] DEBUG: Opening new socket: C42042F0
[2020-07-10T21:27:33] NOTE: accepted client connection
[2020-07-10T21:27:45] DEBUG: Opening new socket: C4155A40
[2020-07-10T21:27:45] NOTE: accepted client connection
[2020-07-10T21:27:47] NOTE: new client is unresponsive
[2020-07-10T21:27:49] DEBUG: Opening new socket: C350ABB0
[2020-07-10T21:27:49] NOTE: accepted client connection
@shymega commented on GitHub (Jul 10, 2020):
The IP address used is a link-local address. I do wonder if that's
having an effect.
Could you explain further about this 'Thunderbolt bridge'?
Thanks.
On this date - Fri, Jul 10, 2020 at 01:38:35PM -0700, nicu marasoiu wrote:
--
Kind regards,
Dom Rodriguez (shymega)
@nmarasoiu commented on GitHub (Jul 11, 2020):
Hi, sure, I am using a Thunderbolt 2 cable to connect to MBP laptops. Both Linux & MacOS support networking over thunderbolt, so they create a local link between them with between 3 and 8 Gbit/s and 0.5 ms latency (my tests) which i hope will provide benefits over the ethernet connection.
@nmarasoiu commented on GitHub (Jul 11, 2020):
However the same exact behaviour happened when i configured both client and server to use the Ethernet connection between them via the router. I will also repeat this test removing the cable between them, I am not sure if they still have the cable connected at that time.
@github-actions[bot] commented on GitHub (Sep 18, 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.
@p12tic commented on GitHub (Jan 10, 2021):
Let's not close valid bug reports.