It's not possible to correctly run two mDNS stacks at the same time, as
while multicast udp packets can be received by multiple programs, only
one program will receive unicasted port 5353 mDNS replies, even if both
daemons allow multiple-binding to port 5353.

While actually using that feature is not so commonly used intentionally,
it is used sortof by accident by many enterprise wireless network
vendors when they "convert" multicast to unicast as a network
optimisation (because multicast packets are truly multicasted, but at a
"base" network rate much slower than the normal rate of the clients,
which uses up more airtime than sending them all individually at a
higher speed).

Hence, we cannot really enable the independent systemd-resolved support
at the same time as actually using Avahi to do proper service discovery,
and you should use the avahi/nss-mdns support instead if you want any
actual mDNS service discovery support.


Ideally resolved would add a backend to use avahi when it exists/is
installed so we could drop the extra nss-mdns step. But no one has
written that code so far.

But I am not sure why you say you cannot disable the systemd-resolved
mDNS support. It's disabled in resolved by default out of the box, and
then when disabled it doesn't bind to the port, so Avahi works fine, and
nss-mdns will work find alongside systemd-resolved. Many people use this
configuration all the time.

So I am curious.. in what specific scenario and configuration are you
seeing it enabled and the port conflict?

On an out of the box install if you run "resolvectl status" you'll see
-mDNS on all the interfaces. Can you detail your configuration more
precisely?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2062927

Title:
  Ambiguity in mdns configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/2062927/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to