Re: Bug#1000468: ITP: mdnsd -- embeddable Multicast DNS Daemon
On Tue, 23 Nov 2021 at 19:47:44 +0100, Gürkan Myczko wrote:
> This is a standalone mDNS-SD daemon for small systems. Although still
> limited in functionality it can announce services like FTP, HTTP, and
> SSH and respond to scanning (enumeration) requests from tools like
> mdns-scan.
>
> This is similar like avahi-daemon but different.
Since Avahi is the "market leader" for this functionality, perhaps it
would be useful to expand the description to mention why you would want
to use this implementation over Avahi, and why you would want to use
Avahi over this implementation?
If I understand correctly, mdnsd can announce services listed in
a configuration file to be seen by other machines on the LAN (the
service side of mDNS), and it does that with lower resource cost
(memory? installed size?) than a basic installation of Avahi.
Does it have functionality to help other processes on the local machine
to browse services elsewhere on the LAN? There are two ways the client
side of mDNS can work: clients can either do all the UDP themselves from
first principles, like python3-zeroconf does, or they can communicate
with a centralized daemon that can multiplex requests from multiple clients
on the same machine, like Avahi clients do. In general the first way is
simpler if you have a single long-running client on a very small embedded
system, but the second way reduces network load if you have multiple
clients on a general-purpose system like a laptop or a larger/more
modular embedded system.
Does it have IPC functionality for processes on the local machine to
announce additional services dynamically (Avahi uses D-Bus for this),
or is it limited to a relatively static configuration?
smcv
Reply to: