Does mDNS work? I don't see mine on my network...


 
D

Dave Camp

New member
My HeaterMeter has a RasPI 3 with software version 20170513B. Testing on a MacBook running 10.12.5. Both are on the same wireless network.

"dns-sd" in the terminal lists a number of things on my network, but not my HeaterMeter.

Code: 
dave$ dns-sd -B _http._tcp
Browsing for _http._tcp
DATE: ---Sat 17 Jun 2017---
11:02:26.735  ...STARTING...
Timestamp     A/R    Flags  if Domain               Service Type         Instance Name
11:02:26.736  Add        3   4 local.               _http._tcp.          Brother MFC-9340CDW
11:02:26.736  Add        3   4 local.               _http._tcp.          Living Room mini
11:02:26.736  Add        3   4 local.               _http._tcp.          Premier 4XL
11:02:26.737  Add        2   4 local.               _http._tcp.          UniFi Controller

The docs seem to indicate it should be on by default, and I don't see any options in the config pages related to mDNS.

I'm working on a set of iOS/tvOS/watchOS apps for the HeaterMeter, having mDNS working would really help...
 
I see the file /etc/avahi/services/linkmeter.service but I don't see the avahi package installed. Maybe this was missed in the switch to lede.
 
I don't see this stuff in the current diffconfig.BCM2708 file, but it was in the older config.BCM2708 file

Code: 
CONFIG_PACKAGE_avahi-daemon=y
CONFIG_PACKAGE_libavahi=y
 
Oops, looks like it didn't make the transition to the LEDE platform with the rest of the packages. I think this is because they removed it. I'll look into it, thanks for reporting!
 
Last edited:
Confirming that the latest snapshot fixes this.

Code: 
$ dns-sd -B _http._tcp
Browsing for _http._tcp
DATE: ---Fri 04 Aug 2017---
17:24:08.462  ...STARTING...
Timestamp     A/R    Flags  if Domain               Service Type         Instance Name
17:24:08.658  Add        2   4 local.               _http._tcp.          HeaterMeter on HM43W
 
Thanks for confirming Steve! And before you bring it up, LEDE's umdns only lets each Linux service only publish one mDNS service, which is why there is no https advertised. I'm not entirely sure what they were thinking when they said "Let's throw out avahi and write our own mDNS implementation that is missing a bunch of features, but has this ONE that we want." I believe it is theoretically possible to do, but you gotta jump through a lot of hoops editing the JSON objects stored in shell environment variables so I may invest time getting it working at some point but this will have to do for now.
 
I don't really think it matters too much. As long as the device is discoverable, the application wishing to speak to it should be able to query it to see if https is enabled. I would also imagine that 99% of deployed HMs are still using http instead of https. I actually don't even run https on the HM itself, I only run https on my main RasPi running nginx, which then proxies the connection to the HM over http.
 
You must log in or register to reply here.

 

Back
Top