Warning about its usage?
I strongly suggest that Avahi not be used at this time; especially with Win9X on the LAN. Avahi does nothing to help with the network connections and does not offer any services which are not available elsewhere. Worse, it is not complete, and is missing key elements.
Futher, since all networking configuration is extremely difficult, it is far more advantageous to focus the user on the basics. Unless the user is of advanced understanding of Arch and the inner workings of Linux in general, the use of Avahi is only distracting from the ultimate quest; having a simple and intuitive network and file sharing setup.
If any user might stumble upon this subject, it would be good to offer appropriate warnings at the begining of the article, and clearly explain the details of the tested situation offered in the article. Obviously it does not work in certain situations, as I can attest.
Thanks. - KitchM 20:51, 3 June 2010 (EDT)
- This comment is quite long. Since Avahi upstream does see itself unstable, so maybe the warning here is not needed. At the same time, the "Not working situations" should be list clearly of cause. --Fengchao (talk) 05:49, 18 May 2012 (UTC)
- The comment was meant to be amplified enough so all could understand all the nuances of the problem. Further, just because upstream thinks it is stable, or even useful, does not make it either. To test if the product works, anyone is free to test it. KitchM (talk) 15:10, 18 May 2012 (UTC)
Is mDNS still necessary? It seems systemd-resolved has built-in support for it. Enabling mDNS as this article describes now causes the error message:
*** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** —This unsigned comment is by Fylwind (talk) 06:39, 11 February 2018. Please sign your posts with ~~~~!
- Is systemd-resolved enabled by default? We should definitely mention that it's an alternative.
- Also note this quote by Lennart Poettering (original developer of Avahi and now working on systemd-resolved): "Our plan is to turn systemd-resolved into an nscd compatible daemon that speaks dns/dnssec, mdns, llmnr, in the long run replacing avahi."
- I'm not sure how far they are on achieving the ultimate goal though. Lonaowna (talk) 12:52, 17 February 2018 (UTC)
Don't Merge Avahi print service/CUPS with Airport/Airprint
There is no logical relationship. AirPort/AirPrint is something separate and distinct from creating an Avahi service file to make printers available to wireless clients. Avahi and its services are not in any way related. 'AirPort' is an apple product you buy, Configuring an Avahi service to make a printer available -- is something you can do with Avahi. Make sense that would stay on the Avahi page.
David C. Rankin, J.D.,P.E. -- Rankin Law Firm, PLLC (talk) 06:17, 29 July 2017 (UTC)