mDNS not working on Ubuntu core amd64 #176
Comments
If you launch it manually does it work? Are you on the same network (192.168.0.0-254) as the device? |
Hi @kyrofa . As I put on the first message if I launch manually I have the following message: |
If I connect my PC on the Wired network, same. |
What operating system is the PC running (i.e. the thing from which you're pinging |
Ubuntu 16.04.1 |
Ok so, some updates. I was looking for Avahi (who manage mDNS) on the Ubuntu core but didn't found it. Looking on google I found this page: So I installed snapweb... and entering http://snapweb.local without the port my browser show me... Nextcloud ^^ . So my theory is that we are missing Avahi so the nexcloud snap declare the mDNS domain but there no daemon to catch it and send it over the network. |
@kyrofa any idea how can I try to debug this problem ? |
Neither snaps use avahi; avahi is a daemon that broadcasts mDNS for its clients. Both the nextcloud and snapweb snaps directly broadcast mDNS on their own. It's interesting that |
Can I see the output of |
Hi ! Thank for taking time to respond. Yes it's what I understand now. The difference I can see between Snapweb and Nextcloud is the lib you are using for publishing the domain on the network. The one used on mdns-publisher is : github.com/davecheney/mdns I have a second bug I didn't mention before but it can help. I have 2 network interfaces on the box eth1 and eth0. And if I connect the network on eth1 and run the mdns-publisher manually is returning an error telling me there are no IP on eth0. If I connect on eth0 and execute the mdns-publisher manually is returning me the message I post before. I didn't mention before but when I execute mdns manually and I got the message : If I ping nextcloud.local: if I ping snapweb: thx ;-) |
Hi @kyrofa , So I did a small tweak in the mdns-publisher.go replacing github.com/davecheney/mdns by the lib used on snapweb : github.com/presotto/go-mdns-sd And it's working fine. So do you think I can try to send a PR on mdns-publisher ? |
@seb2411 yes, please do! I'm curious to see the difference. |
I'm not sure why but I found a way to fix the problem on my box. Replacing the hostname in Ubuntu Core (/etc/hostname) by nextcloud instead of localhost.localdomain. And it's working. So I don't know if it's necessary to do a PR on mdns-publisher. |
Sounds like this issue is resolved, although I'll poke at that on the mdns-publisher project. |
Hello,
I'm testing Nextcloud Snap on a Mini PC Celeron using this config to generate the img file of Ubuntu Core:
"architecture": "amd64",
"gadget": "pc",
"kernel": "pc-kernel",
Everything seem to work well but I can't access the Nexcloud instance using nexcloud.local . It seem to me that the mdns-publisher work well but the request is sending is not processed at some point.
If I launch mdns-publisher manually I got this:
So I have no idea how to debug at this point and how to fix this problem or if the problem comes from nextcloud-snap or from Ubuntu Core for PC.
Thx.
The text was updated successfully, but these errors were encountered: