After some time into a print, my MINI+ will no longer be reachable under its mDNS hostname (in my case prusamini.local) - it simply does not respond to the mDNS multicast query anymore. It still responds fine to pings using its IP address, and the web interface remains accessible using the IP address.
A quick fix is to disable and re-enable the Ethernet connection (e.g. by switching to WiFi and back, or by getting a new DHCP lease).
This doesn't appear to be happening when the printer is just sitting idle - it only occurs after a while during a print.
Even after the print has concluded, there are still no responses to mDNS queries once the printer is idle again; the only fix is, again, to re-init the network connection on the printer.
In my testing, if I simply run a dig -p 5353 prusamini.local @224.0.0.251 in a sleep 60 loop or similar while the MINI+ is printing, then it will correctly keep working forever, so I cannot say after how long of a print time this happens.
It seems that the background process that handles mDNS responses "goes to sleep" after some time during a print and then never wakes up again, as this method of "keeping it awake" using periodic mDNS queries prevents the problem from occurring.
How to reproduce
Print a longer print (say, two hours), then attempt to resolve the printer's IP address using its ${hostname}.local address.
Expected behavior
Multicast mDNS query responses by the printer do not stop after a while when printing.
Printer model
MINI+
Firmware version
6.1.2
Upgrades and modifications
None
Printing from...
PrusaLink via Ethernet
Describe the bug
After some time into a print, my MINI+ will no longer be reachable under its mDNS hostname (in my case
prusamini.local) - it simply does not respond to the mDNS multicast query anymore. It still responds fine to pings using its IP address, and the web interface remains accessible using the IP address.A quick fix is to disable and re-enable the Ethernet connection (e.g. by switching to WiFi and back, or by getting a new DHCP lease).
This doesn't appear to be happening when the printer is just sitting idle - it only occurs after a while during a print.
Even after the print has concluded, there are still no responses to mDNS queries once the printer is idle again; the only fix is, again, to re-init the network connection on the printer.
In my testing, if I simply run a
dig -p 5353 prusamini.local @224.0.0.251in asleep 60loop or similar while the MINI+ is printing, then it will correctly keep working forever, so I cannot say after how long of a print time this happens.It seems that the background process that handles mDNS responses "goes to sleep" after some time during a print and then never wakes up again, as this method of "keeping it awake" using periodic mDNS queries prevents the problem from occurring.
How to reproduce
Print a longer print (say, two hours), then attempt to resolve the printer's IP address using its
${hostname}.localaddress.Expected behavior
Multicast mDNS query responses by the printer do not stop after a while when printing.
Files
No response