Open detly opened 4 years ago
Could be because Snap doesn't use the system resolve order(!!).
Workaround as per #12 on bug #1838038: on the client, install (via apt
) the nscd
package and restart snapd
:
sudo apt install nscd
sudo systemctl restart snapd
@detly can you confirm that installing nscd worked?
I am not sure Barrier can do anything about this as the root cause is something to do with Snap's name resolution policy.
@the-wes It did! And I agree re. it being a Snap issue. I'll leave it up to you whether you want to document it as a necessary workaround in the installation instructions or not (I'd consider it since Avahi is such a common tool for resolution on local networks).
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.
The client connects to the server just fine when using the numeric IP address. It does not connect when given the Avahi mDNS server address.
I can live with using numeric IP addresses, but it's nice not to have to. Plus it seems odd that only one piece of software on the client machine can't resolve using Avahi.
Operating Systems
Server: Ubuntu 19.10 (eoan)
Client: Ubuntu 18.04.3 LTS (bionic)
Server is a Lenovo laptop, connected via wifi. Hostname and screen name is "aang".
Client is a Mac Mini 2016, connected via ethernet. Hostname and screen name is "fox".
Barrier Version
Server: installed via apt
2.3.1+dfsg-1ubuntu1
Client: installed via Snap:
Steps to reproduce bug
Server:
192.168.1.231
, confirmed viaip addr show
.Client:
192.168.1.231
.It works!
Now try:
Client:
aang.local
.It does not connect. See log below.
Other info
Avahi works fine for everything else. From client:
Log on server
Log for successful connection (via IP address):
Log for unsuccessful connection (via Avahi):
(Nothing after this.)
Log on client
Successful/IP address:
Unsuccessful/Avahi: