plajjan
commented
4 years ago I'm seeing this too. Linux server with mac client. Let it idle over the weekend and now seeing:
[2020-10-05T09:25:35] INFO: OpenSSL 1.1.1d 10 Sep 2019
[2020-10-05T09:25:35] INFO: accepted secure socket
[2020-10-05T09:25:35] INFO: TLS_AES_256_GCM_SHA384 TLSv1.3 Kx=any Au=any Enc=AESGCM(256) Mac=AEAD
[2020-10-05T09:25:35] NOTE: accepted client connection
[2020-10-05T09:25:35] ERROR: invalid message from client "mbp13": DINF
[2020-10-05T09:25:35] NOTE: new client disconnectedUnlike OP I do not have a secondary interface. Just my local network so shouldn't be any powering down of USB NIC. I am using the built-in wireless NIC.
A restart of barrier fixes it.
sgrienen
zgxsin
aleksipirttimaa
Jan02
tamsky
mahmoudimus
fordodone
charel
leafgray
MatthewMartinFD
scirelli
Describe the bug I have a windows 10 desktop (server) and a macbook (client) that I have setup for sharing. It works well most of the time (occasional clipboard issue that requires a server restart, but that's another thread)! However, I've noticed when I come back to my desk after a long period of time (overnight for example) I find barrier to be disconnected. On the server I get the following initial error:
[2020-09-25T22:41:04] ERROR: ssl error occurred (system call failure) [2020-09-25T22:41:04] ERROR: eof violates ssl protocol [2020-09-25T22:41:04] NOTE: client "macbook" has disconnected [2020-09-25T22:41:25] INFO: OpenSSL 1.0.2l 25 May 2017 [2020-09-25T22:41:25] INFO: accepted secure socket [2020-09-25T22:41:25] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD [2020-09-25T22:41:25] NOTE: accepted client connection [2020-09-25T22:41:25] ERROR: invalid message from client "macbook": DINF [2020-09-25T22:41:25] NOTE: new client disconnected
(the last 6 lines repeat repeatedly as the client thrashes trying to reconnect)
On the client-side I get the following (slightly redacted for good hygiene and paranoia) messages:
[2020-09-25T22:41:06] INFO: process exited normally [2020-09-25T22:41:06] INFO: detected process not running, auto restarting
[2020-09-25T22:41:27] INFO: starting client [2020-09-25T22:41:27] INFO: config file: /private/var/folders/fk/3hbckppj7jjd3lhpaa4t78440154gp/T/Barrier.rGWJlU [2020-09-25T22:41:27] INFO: log level: INFO [2020-09-25T22:41:27] INFO: drag and drop enabled [2020-09-25T22:41:27] NOTE: started client [2020-09-25T22:41:27] NOTE: connecting to '': :24800
[2020-09-25T22:41:27] INFO: OpenSSL 1.1.1g 21 Apr 2020
2020-09-25 22:41:27.710 barrierc[65280:432218] starting cocoa loop
[2020-09-25T22:41:27] NOTE: server fingerprint:
[2020-09-25T22:41:27] NOTE: trustedServersFilename: /Users/me/Library/Application Support/barrier/SSL/Fingerprints/TrustedServers.txt
[2020-09-25T22:41:27] NOTE: Opened trustedServersFilename: /Users/me/Library/Application Support/barrier/SSL/Fingerprints/TrustedServers.txt
[2020-09-25T22:41:27] NOTE: Fingerprint matches trusted fingerprint
[2020-09-25T22:41:27] INFO: connected to secure socket
[2020-09-25T22:41:27] INFO: server ssl certificate info: /CN=Barrier
[2020-09-25T22:41:27] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD
[2020-09-25T22:41:27] NOTE: disconnected from server
(the last 13 lines repeat to infinity)
If I manually stop the barrier client on my macbook and restart it, it connects again just fine. If I manually stop and start the server, nothing changes. It looks like there's something happening with the macos client that only happens after a period of time.
To Reproduce
Steps to reproduce the behavior:
Expected behavior Clients should maintain connectivity, but if process exits it should gracefully restart and reconnect. Not sure what DINF is.
Screenshots (see logs above)
Desktop (please complete the following information):
Additional context
Barrier interface is a secondary interface on the same network (e.g. I multihome both machines and have barrier over a second static IP interface) due to wireless performance. Macbook's secondary interface is a USB NIC.
I found a smattering of similar issues reported that suggests perhaps the macbook is powering down the device when idle to conserve power, not sure if this would impact or why it couldn't restart gracefully.