Re: CUPS - how to match autodetected printers to physical ones
On Fri, Apr 08, 2022 at 08:52:26PM +0100, Brian wrote:
> You didn't like my bus analogy, did you?
I don't think it's a very good analogy for this situation.
> What makes you think that knowing an IP address tells you where
> any machine of any description is located?
Because the device is (was) sitting 50 feet away from me, and even
if the people who installed it had not been kind enough to print some
kind of config page and attach it to the front of the printer, I could
have Googled the printer's model number and found out how to print the
printer's own config page myself. Or else how to scroll through the
printer's control panel menus to find its IP address that way.
The printer's brand, model and IP address are the extremely concrete
pieces of information that I can readily acquire and compare. Software
that refuses to divulge useful information is not acting in a helpful
manner.
Also, completely coincidentally, I happen to know how the corporate
network is subdivided -- at least in the building that I work in.
Each floor has a /23 network assigned to it. So, from the IP address
alone, I can at least tell whether the device is on my floor. If I
need more specific location info than that, I would either have to call
someone, or search manually.
> Trial and error is not neeed. Just an IT department with basic
> skills and the intention to help users would suffice.
I wonder how many IT departments match both parts of that description.
In any case, "avahi-browse -rt _ipp._tcp" was helpful and useful, so
thank you for that. I've typed it into my notes for next time I need it.
Reply to: