mDNS support on Pico

[ondrej1024]

Hi,

is there mDNS support enabled on the RP2040/Pico port of Micropython (like ESP32 port)?
If it is, how can it be configured?

I am running this MP version:
MicroPython v1.19.1-910-g4937174b4 on 2023-03-01; W5500-EVB-Pico with RP2040

Network connection is active but I cannot see the mDNS info on the network.

[ondrej1024]

So I dug further into this issue and found some documentation about the mDNS service implemented in the lwip stack.

This states to call this function to initialise the service:
mdns_resp_init()

and then start responding on a netif by calling this function:
mdns_resp_add_netif()

On the Pico port, the first function is actually called in main.c but the second function never seems to be called. This leaves the service inactive. Looks like a bug in the MP Pico port.

So I wonder which part of the MP implementation should call mdns_resp_add_netif()? It has to be done probably after the network interface has been created by the driver.

Anyone who can shed some light on this?

[ondrej1024]

I think this bug report answers my question.

[vinux84]

Hi, Just curious, were you able to get mDNS to work on the RP2040?

[ondrej1024]

I ended up using the micropython-mdns package which works great.

[scruss]

(this may not be a useful answer)

I can confirm local DNS (not mDNS) with the nightly build MicroPython v1.23.0-preview.324.gd11ca092f on 2024-04-17; Raspberry Pi Pico W with RP2040

Set the hostname before you initialize the network:

    import network
    network.hostname("picowX")
    ...

For some reason, my LAN seems to prefer .ht.home over .local, but I can do this:

ping picowX.ht.home
PING picowX.ht.home (192.168.2.138) 56(84) bytes of data.
64 bytes from picowX.ht.home (192.168.2.138): icmp_seq=1 ttl=255 time=293 ms
64 bytes from picowX.ht.home (192.168.2.138): icmp_seq=2 ttl=255 time=123 ms
64 bytes from picowX.ht.home (192.168.2.138): icmp_seq=3 ttl=255 time=145 ms
...

[cwalther]

For some reason, my LAN seems to prefer .ht.home over .local, but I can do this:

ping picowX.ht.home
PING picowX.ht.home (192.168.2.138) 56(84) bytes of data.

That does not look like mDNS to me. That looks like your LAN router registers the name picowX.ht.home in its own DNS server (using information it has from also being the DHCP server). I suspect it’s the router answering the query here, not the Pico.

(I can’t try it myself because I don’t have a Pico W.)

[scruss]

ah, right — that would be it.

[ShadowLNC]

I couldn't figure out why I could ping pico on Linux (WSL, Rasperry Pi), but not on Windows (Powershell, CMD) - I suspect that my router is doing the same thing here (I can see it responds to dig).

It also seems that Linux will resolve TLDs as hostnames if a DNS record exists, but that Windows will not, although ping pico. (note the dot) will resolve, so for some reason Windows will only accept a DNS TLD if it ends with a dot (which is usually implicit), otherwise it assumes it must be mDNS or NetBIOS.

[vinux84]

I have been able to get the same package to work that @ondrej1024 uses, just bare bones, pulling the example out of that repository.

But has anyone ever got this to work with python http server, or any high level working web server?

Basically Im wanting a user to be able to access pico w with : hostname.local and be redirected to a home web page, hosted from the pico. This isn't my strong suit by any means and I could be missing something very obvious, but could not get it to work.

[mendenm]

@vinux84 I think it should work with microdot, which is itself a really nice web server for the Pico.