Setup mDNS for device discovery

[PMuld2]

Hello,

I am experimenting with mDNS to advertise a Galileo on the local network.

However, I have some troubles doing this.

First, I advertise the Galileo with:

$ dns-sd -R '444' _tessel._tcp local 22

When I then browse for the Galileo from another machine (via Wlan0 connected to same router):

$ dns-sd -B _tessel._tcp

There is no device.

Now, exploring why this problem might occur, I checked the hostname configuration on the Galileo.

root@galileo:~# hostname -f

galileo

So, there is a missing .local

But also the difference in /etc/resolv.conf might be interesting

root@galileo:~# cat /etc/resolv.conf

# Generated by Connection Manager

nameserver 127.0.0.1

nameserver ::1

Vs on the other machine in the network:

domain Speedport_W723_V_Typ_A_1_01_011

nameserver 192.168.2.1

nameserver 192.168.2.1

nameserver fe80::1

How could I get mdns running?

[PMuld2]

Note that I am able to ping the device:

m:blog pmu$ ping galileo

PING galileo.speedport_w723_v_typ_a_1_01_011 (192.168.2.105): 56 data bytes

64 bytes from 192.168.2.105: icmp_seq=0 ttl=64 time=6.256 ms

[DBunz]

Hey Patrick, this is Student007 (Dan) from Tessel,

referencing our conversation at https://github.com/tessel/t2-cli/issues/508# issuecomment-168501182 https://github.com/tessel/t2-cli/issues/508# issuecomment-168501182

I know you already talk about they are in the same network, but I remember (with pain) former I foxed myself because I though I could ping a device but it wasn't in the same physical network. The IP range looked like to be in the same range but one part was WLAN the other part LAN and the rooter didn't transport the mDns over there.

Think you haven't done that but I simple want to share this because I had this problem.

Are you using a fritzbox rooter ?

[PMuld2]

Thanks! The router I have here is a Speedport. Interesting, googling gives this: https://telekomhilft.telekom.de/t5/Ger%C3%A4te-Zubeh%C3%B6r/Speedport-723V-blockiert-mDNS-Anfragen/t... Speedport 723V blockiert mDNS Anfragen | Telekom hilft Community (in german). I'll check with configuration of the router.

[PMuld2]

The router does not allow to set anything related to DNS, only the address for DNS lookup 192.168.2.1

[DBunz]

maybe you should flush another firmware or try things with another router so you are really in the same network.

[PMuld2]

I got mdns working with a new setup on the router to create a subnet on 192.168.3.0 (thanks to Sergio's hint here: :

pmu$ dns-sd -B _tessel._tcp .

Browsing for _tessel._tcp

DATE: ---Mon 04 Jan 2016---

22:00:53.274 ...STARTING...

Timestamp A/R Flags if Domain Service Type Instance Name

22:00:53.275 Add 2 4 local. _tessel._tcp. edison

Yet, the Galileo with the Ethernet connection still has a problem to be discovered:

root@galileo:~/projects/udp# dns-sd -R 'galileo' _tessel._tcp . 22

Registering Service galileo._tessel._tcp port 22

DATE: ---Mon 04 Jan 2016---

20:43:43.922 ...STARTING...

20:43:44.611 Got a reply for service galileo._tessel._tcp.local.: Name now registered and active

[Sergio_A_Intel]

Hi poseid,

Do you still need assistance with this case? Is your issue only related to the Ethernet connection?

Sergio