On Mon 11 Apr 2022 at 13:55:03 -0400, Greg Wooledge wrote: > On Mon, Apr 11, 2022 at 06:47:59PM +0100, Brian wrote: > > BTW. I am interested in how using /usr/lib/cups/backend/snmp went. > > Its drawback is that not all printers provide an snmp service. > > wooledg:~$ /usr/lib/cups/backend/snmp > network socket://10.76.172.120 "HP LaserJet 4250" "hp LaserJet 4250" > "MFG:Hewlett-Packard;CMD:PJL,MLC,PCLXL,PCL,PJL,POSTSCRIPT;1284.4DL:4d,4e,1;MDL:hp > LaserJet 4250;CLS:PRINTER;DES:Hewlett-Packard LaserJet 4250;" "W01-0224" > network socket://10.76.172.88 "HP LaserJet 4100 Series" "HP LaserJet 4100 > Series" "MFG:Hewlett-Packard;CMD:PJL,MLC,PCL,POSTSCRIPT,PCLXL,PJL;MDL:HP > LaserJet 4100 Series ;CLS:PRINTER;DES:Hewlett-Packard LaserJet 4100 Series;" > "" > network socket://10.76.173.60:9100 "HP LaserJet P3010 Series" "HP LaserJet > P3010 Series" > "MFG:Hewlett-Packard;CMD:PJL,BIDI-ECP,PJL,POSTSCRIPT,PDF,PCLXL,PCL;MDL:HP > LaserJet P3010 Series;CLS:PRINTER;DES:Hewlett-Packard LaserJet P3010 Series;" > "" > > Looks like that doesn't contain anything for the Canon printers.
Although used by other vendors, a socket://... URI is really an HP thing, used by JetDirect appliances, so not surprising. Anyway, this very useful info of yours would prompt me to discard advising the use of snmp to match IP address with printer model. We are back to avahi-browse. I appreciate you print to that printer infrequently but would suggest a manually set up queue may suit you. Execute driverless to get its URI. (I am sure you can sort out which one it is). Then lpadmin -p SENSIBLE_PRINTER_NAME -L MYOFFICE -v URI -E -m everywhere -- Brian.
