mDNS fix works on RRF3.4.5 but not on RRF3.5b4

Hugsy

Hi,

I saw the mdns fix at this commit and copied it into my current RRF3.4.5 branch and it works!
Now with RRF3.5b4 where it's already implemented, when I upgraded my MB6HC to it, saldy my mac doesn't get it with the mDNS even tho it worked on RRF3.4.5 with the fix.

An I missing something? Does anybody have the same issue? Did something else changed regarding networking in RRF3.5?

Thanks in advance,
Hugues

chrishamm

@Hugsy I cannot confirm that, I just installed 3.5-b4 on a 6HC and both name resolution and service discovery work:

 ~> avahi-resolve -n duet3.local
duet3.local	192.168.1.135
...
~> avahi-browse -alr
...
= wlp2s0 IPv4 HTTP                                          Web Site             local
   hostname = [duet3.local]
   address = [192.168.1.135]
   port = [80]
   txt = ["version=3.5.0-beta.4" "product=RepRapFirmware for Duet 3 MB6HC"]

Hugsy

@chrishamm Weird, maybe I need to update DWC as well? All my duet3D-firmware modules are updated I don't see why it wouldn't work. I'm trying to find what broke during my merge with 3.5-dev.

I'm struggling to install avahi correctly so I'll try to find something else to test the mDNS.

chrishamm

@Hugsy Avahi is the mDNS toolkit for Linux, not sure if that's applicable to OS X. Before we released 3.5-b4 @droftarts could confirm that the same fix works with the latest OS X, too.

Hugsy

@chrishamm I isolated the problem to be specific to only one of our machines. So it's not firmware related, the problem is on our end