[cups.general] how to get printers on mac os 10.8 from a linuxcups in a different subnet

Johannes Meixner jsmeix at suse.de
Fri Nov 9 04:03:54 PST 2012


On Nov 7 16:01 Michael Sweet wrote:
> On 2012-11-07, at 3:18 PM, franz.pfoertsch.brose <franz.pfoertsch at brose.com> wrote:
>> You also could mark cups browsing as deprecated and disable
>> it by default.
> It *was* deprecated in CUPS 1.5 and has been disabled by default
> since at least CUPS 1.2.

At least in the CUPS 1.5 documentation for the cupsd at
none of the "Browse..." configuration directives is marked as
deprecated (like the AuthClass and AuthGroupName configuration
directives are).

According to this documentation the defaults for CUPS 1.5 are
in particular:
There is no default browse address.
The default is to accept browse packets from all hosts.
The default setting is Yes.

I get the same documentation on http://localhost:631
on my Linux worksatation which runs CUPS 1.5.4.

That defaults exist "since ever" and match what is described
as "Intrinsic design of CUPS for printing in the network" at

For CUPS 1.1 any cupsd did broadcast its local printers by
default (i.e. the BrowseAddress was not empty by default)
and that was bad in networks because when John Doe connected
his laptop to a network or when he set up local printers on
his workstation his local cupsd would broadcast John Doe's
printers on the network which is usually neither wnted by
John Doe nor by the other users (and admins) of the network.

Therefore since a CUPS 1.1.N version or at least since CUPS 1.2
BrowseAddress is empty by default but Browsing is and was enabled
all the time by default up to CUPS 1.5.

>> In my opinion you break cups for Linux and structued networks.
> You don't need to upgrade if you rely on legacy support.
> And structured networks are built on DNS, which is the basis
> of Bonjour!

Franz would need to upgrade to CUPS 1.6 on his server
to get CUPS support for his Mac OS 10.8 clients.

Franz can at most upgrade to CUPS 1.5 on his server
to keep CUPS support for his other clients.

This is a dilemma.

Perhaps Franz could use two servers, one with at most CUPS 1.5
to keep CUPS support for the existing clients and another one
with CUPS 1.6 to get CUPS support for Mac OS 10.8 (and similar)?

Perhaps this way a smooth transition from CUPS <= 1.5
to CUPS >= 1.6 would be possible?


Perhaps also mDNS is not yet an ideal solution for bigger networks?

Right now I noticed the Genman heise online news article


and its English version


that reads (excerpt):
mDNS is incorporated in Apple's Bonjour and in the Avahi software for
Linux to allow small networks to be self-configuring. But mDNS is built
around the idea that everything works on a single subnet. Universities
and businesses that would like to use the technology find that, if they
enable the multicast across their networks, they become flooded
with mDNS traffic.

But I am really not a (m)DNS expert - I only noticed those articles.

Kind Regards
Johannes Meixner
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer

More information about the cups mailing list