Bug 203053 - print/cups-base: support for DNSSD is incomplete
Summary: print/cups-base: support for DNSSD is incomplete
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Tijl Coosemans
URL:
Keywords:
Depends on: 207746
Blocks:
  Show dependency treegraph
 
Reported: 2015-09-11 20:59 UTC by J.R. Oldroyd
Modified: 2016-03-11 14:28 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description J.R. Oldroyd 2015-09-11 20:59:10 UTC
Since cups-1.7.0, printers are now shared using DNSSD.

The print/cups-base and print/cups-client ports offer AVAHI and MDNSRESPONDER as alternative implementations of DNSSD, with MDNSRESPONDER being enabled by default.

The print/cups-filters port, which provides cups-browsed, offers only AVAHI which is disabled by default.

As a result, printers advertised on FreeBSD servers are not visible by default on FreeBSD clients.

Now it is possible to see them by having the clients poll the servers using the CUPS protocol, but this is a kludge and not practical in a large environment.

Either print/cups-filters should have MDNSRESPONDER support added and enabled, or AVAHI support should be tested and fixed and enabled in all three ports.
Comment 1 w.schwarzenfeld 2016-02-13 07:21:19 UTC
It is possible to make a warning in the cups-client and cups-base ports or a comment in the description of the port-dialog? So nobody could overlook it.
Comment 2 Tobias Kortkamp freebsd_committer freebsd_triage 2016-02-13 17:38:58 UTC
I believe bug #196806 is another instance of the same (or a very closely related) problem.
Comment 3 Tijl Coosemans freebsd_committer freebsd_triage 2016-03-11 14:28:51 UTC
In ports r410825 the MDNSRESPONDER option has been removed and the AVAHI option has been enabled by default in both cups and cups-filters.