Feature changed by: Johannes Meixner (jsmeix) Feature #313282, revision 2 Title: Full automated setup for printers in the network openSUSE Distribution: Unconfirmed Priority Requester: Neutral Requested by: Johannes Meixner (jsmeix) Partner organization: openSUSE.org Description: I would like to have it evaluated whether or not and/or to what extent it is possible to setup printer devices which are accessible via - network in a full automated way. The basic idea behind: For locally - connected USB printers there is already full automated setup. I would - like to have it evaluated if and/or to what extent this could be - extended reagarding printer devices which are accessible via network. + network in a full automated way. + The basic idea behind: For locally connected USB printers there is + already full automated setup. I would like to have it evaluated if + and/or to what extent this could be extended reagarding printer devices + which are accessible via network. FYI: For printer devices which are accessible via a CUPS server there is nothing to do because this works already via the so called "CUPS - Browsing". Some use cases: Network printer) A network printer is a - printer with a built-in network interface so that the printer device is - directly accessible via network. The problem regarding full automated - setup is how to autodetect the printer model so that the right driver - for this model can be set up. Therefore the problem is how to - autodetect the parinter model on a printer device which is directly - accessible via network. Usually this is possible via some generic SNMP - query. The CUPS tool "lpinfo -l -v" results this for the "socket" - device URI e.g.: + Browsing". + Some use cases: + Network printer) + A network printer is a printer with a built-in network interface so + that the printer device is directly accessible via network. + The problem regarding full automated setup is how to autodetect the + printer model so that the right driver for this model can be set up. + Therefore the problem is how to autodetect the parinter model on a + printer device which is directly accessible via network. + Usually this is possible via some generic SNMP query. The CUPS tool + "lpinfo -l -v" results this for the "socket" device URI e.g.: # lpinfo -l -v Device: uri = socket://10.10.2.92 make-and-model = HP LaserJet 4050 Series Device: uri = lpd://10.10.4.4/ make-and-model = Kyocera FS-C5100DN - SMB) A printer device which is accessible via a SMB printer share: In - this case the client system must submit readymade printer specific data - to the SMB share (i.e. there is no so called "filtering" on a SMB print - server). Therefore on the client system usually a printer driver must - run. If it is a PostScript printer, the client must at least provide - generic PostScript (e.g. when printing image data it must be converted - into PostScript on the client system). The problem regarding full - automated setup is how to autodetect the printer model so that the - right driver for this model can be set up but the printer device is - "hidden" behind the SMB share. Therefore the problem is how to - autodetect the parinter model via a SMB share. + SMB) + A printer device which is accessible via a SMB printer share: In this + case the client system must submit readymade printer specific data to + the SMB share (i.e. there is no so called "filtering" on a SMB print + server). + Therefore on the client system usually a printer driver must run. If it + is a PostScript printer, the client must at least provide generic + PostScript (e.g. when printing image data it must be converted into + PostScript on the client system). + The problem regarding full automated setup is how to autodetect the + printer model so that the right driver for this model can be set up but + the printer device is "hidden" behind the SMB share. Therefore the + problem is how to autodetect the parinter model via a SMB share. -- openSUSE Feature: https://features.opensuse.org/313282