Sorry, now I've tried with a Ubuntu device and I'm able to perform the ping to hostname, so I think that there is some settings or firewall rule that to avoid mDNS in Windows 10.

I've typed in the post the wrong hostname.
My hostname is esp32-mdns_XXYYZZ (with XXYYZZ mac address number, the same hostname that I see in the log).

If I tried ping esp32-mdns_XXYYZZ with the command "ping esp32-mdns_XXYYZZ.local" , I have the above problem.

Hi guys, I'm working with master branch v.3.3-dev and I've tried "mdns_example". It doesn't works for me. I've configured the SSID, the password of an external AP, and the hostname of the device for mdns (I've setted "esp32"). When I run the example, I see print in the log the correct name of hostna...

Ok, with the last release of the master is fixed.

Thanks

Sure!

Hi, I've upgrade ESP-IDF from v.3.2-beta1 to v.3.3-dev and I've got an error with the linker also with hello-world example: "linker script generation failed for /esp-idf/components/esp32/ld/esp32.commonld.in ERROR: LD build/hello-world.elf /../../../xtensa-esp32-elf/bin/ld: cannot open linker script...