as has been asked (but unfortunately never answered) before:
Is there a way to disable the internal mDNS responder, so that openhab does not listen to UDP port 5353 any more?
This collides with another mDNS responder on my machine, and I do not necessarily need the openhab announcement, I think.
If the mDNS responder is disabled, I assume that mDNS discovery will still work?
Thanks a lot for your help!
For anyone who has the same problem, it can at least be stopped in the console using
I suspect this will also stop the discovery part, though.
Block it through the firewall on the machine on which openhab is running?
Create or override a config file named
org.openhab.mdns.cfg with contents
File might exist in one of common locations (look at userdata/etc or runtime/etc).
See: openhab-core/bundles/org.openhab.core.io.rest.mdns/src/main/java/org/openhab/core/io/rest/mdns/internal/MDNSAnnouncer.java at 3.4.0 · openhab/openhab-core · GitHub