Re: CUPS - how to match autodetected printers to physical ones
On Sat 25 Feb 2023 at 17:44:15 +0300, Reco wrote:
> Hi.
>
> On Fri, Feb 24, 2023 at 12:58:15PM -0500, Greg Wooledge wrote:
> > On Fri, Feb 17, 2023 at 05:35:11PM +0300, Reco wrote:
> > > Try this next time you're on site:
> > >
> > > lpadmin -p D14841 -E -v ipp://10.76.172.100/ipp/print -m everywhere
> >
> > This worked. I printed two copies of the single-page PDF from Chrome
> > without any further problems.
>
> Just as planned. CUPS autodiscovery is only good for something if you
> don't know printer's real IP. This little episode shows us that nothing
> beats IP-on-sheet-of-paper discovery.
99% of users with tablets, smart phones, laptops etc would find
DNS-SD more to their liking, especially if DHCP assignment is
in place. It would also be hoped that port numbers and resource
paths are on the sheet of paper, otherwise a user will have a
lot of guessing to do.
In this thread we see how a very experienced user reacted to
being denied mdns multicasting. How would an ordinary user go
on? "Give them a piece of paper" sounds awfully like "Let them
eat cake".
> > I've gotta say, though, this option is a disaster:
> >
> > -E When specified before the -d, -p, or -x options, forces the use of
> > TLS encryption on the connection to the scheduler. Otherwise, enables
> > the destination and accepts jobs; this is the same as running the
> > cupsaccept(8) and cupsenable(8) programs on the destination.
> >
> > Whoever decided to overload that option in that way... yikes.
>
> Back in the day Apple's slogan was "think different". The whole CUPS
> suite is a living proof of that.
Wrong target! -E was there in its present form well before Apple
acquired CUPS.
--
Brian.
Reply to: