(See ... for context)
I have a Brother All-in-one wireless laser printer/scanner which has worked for years using the manufacturer's driver blob. I now want to configure it using the printer-driver-brlaser package from the Fedora repo.
I've uninstalled the original Brother driver and deleted the printer config using the CUPS interface.
I then added a new printer using the KDE System Settings widget, and attempted to print a test page. This appears to go through, but then the queue status shows "Unable to locate printer".
I deleted that configuration and tried again using the CUPS web interface. This shows up as:
dnssd://Brother%20DCP-7055W._ipp._tcp.local/
Printing a test page again shows "Unable to locate printer". This happens both using the generic IPP driver and the specific model driver from the RPM package.
The CUPS systemd service and AVAHI daemon are both running, as is systemd-resolved, which handles DNS-SD (I reloaded the latter just in case.)
I'm out of ideas. To repeat: both printing and scanning work correctly with the manufacturer's driver, so it's not a hardware or connection problem.
Any thoughts before I give up and revert to the binary blob?
poc
On Wed, Jun 22, 2022 at 8:32 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
(See ... for context)
I have a Brother All-in-one wireless laser printer/scanner which has worked for years using the manufacturer's driver blob. I now want to configure it using the printer-driver-brlaser package from the Fedora repo.
I've uninstalled the original Brother driver and deleted the printer config using the CUPS interface.
I then added a new printer using the KDE System Settings widget, and attempted to print a test page. This appears to go through, but then the queue status shows "Unable to locate printer".
I deleted that configuration and tried again using the CUPS web interface. This shows up as:
dnssd://Brother%20DCP-7055W._ipp._tcp.local/
I suspect this detection doesn't adequately check the details of the IPP support. Given the age of the printer, IPP may not be implemented "properly" by current standards.
Printing a test page again shows "Unable to locate printer". This happens both using the generic IPP driver and the specific model driver from the RPM package.
I looked at the Brother DCP-7055W Advanced User's Guide, which is dated 2012. I can't see any mention of IPP or AirPrint.
https://discussions.apple.com/thread/7199902 says this model was not on Apple's list of supported printers for AirPort in 2015.
https://wiki.gentoo.org/wiki/Brother_networked_printer says the printer works, but gives no configuration details
https://www.pwg.org/ipp/ippguide.html tells you to "Consult your Printer documentation or the Printer's Bonjour (DNS-SD) registration information to determine the proper hostname, port number, and path to use for your Printer." It would be interesting to know why IPP is failing, but I suspect you are stuck with Brother's rpm.
The CUPS systemd service and AVAHI daemon are both running, as is systemd-resolved, which handles DNS-SD (I reloaded the latter just in case.)
I'm out of ideas. To repeat: both printing and scanning work correctly with the manufacturer's driver, so it's not a hardware or connection problem.
Any thoughts before I give up and revert to the binary blob?
poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
On Wed, Jun 22, 2022, at 4:32 AM, Patrick O'Callaghan wrote:
(See ... for context)
I have a Brother All-in-one wireless laser printer/scanner which has worked for years using the manufacturer's driver blob. I now want to configure it using the printer-driver-brlaser package from the Fedora repo.
I've uninstalled the original Brother driver and deleted the printer config using the CUPS interface.
I then added a new printer using the KDE System Settings widget, and attempted to print a test page. This appears to go through, but then the queue status shows "Unable to locate printer".
I deleted that configuration and tried again using the CUPS web interface. This shows up as:
dnssd://Brother%20DCP-7055W._ipp._tcp.local/
Printing a test page again shows "Unable to locate printer". This happens both using the generic IPP driver and the specific model driver from the RPM package.
The CUPS systemd service and AVAHI daemon are both running, as is systemd-resolved, which handles DNS-SD (I reloaded the latter just in case.)
I'm out of ideas. To repeat: both printing and scanning work correctly with the manufacturer's driver, so it's not a hardware or connection problem.
Any thoughts before I give up and revert to the binary blob?
George might have the final answer, maybe your model will only work via a USP connection if using the brlaser option.
But, I checked my virtual machine to see how it is connecting to the printer...
Brother_DCP-L2550DW_series Brother_DCP-L2550DW_series (Idle, Accepting Jobs, Not Shared) Description: Brother DCP-L2550DW series Location: Driver: Brother DCP-L2550DW series, using brlaser v6 (grayscale, 2-sided printing) Connection: dnssd://Brother%20DCP-L2550DW%20series._pdl-datastream._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4d12445 Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=two-sided-long-edge
So it does seem to be using dnssd. This is a pretty generic F36 XFCE install so I did not do much to get that working, mostly just needed to start cups.
On Wed, Jun 22, 2022, at 8:01 AM, Doug Herr wrote:
But, I checked my virtual machine to see how it is connecting to the printer...
Brother_DCP-L2550DW_series
I just thought to check the web interface that the printer provides and I see that connection protocols can be turned off.
This is at http://%7Bprinter IP}/net/net/protocol.html
Protocol Web Based Management (Web Server) HTTP Server Settings SNMP Advanced Settings LPD Advanced Settings Raw Port IPP HTTP Server Settings AirPrint Advanced Settings HTTP Server Settings Mopria Web Services Advanced Settings HTTP Server Settings Mobile printing for Windows Proxy Advanced Settings Network Scan SMTP Advanced Settings FTP Server FTP Client TFTP mDNS Advanced Settings LLMNR
The only two that are unchecked for the above list are "FTP Server" and "Proxy".
On Wed, Jun 22, 2022 at 12:43 PM Doug Herr fedoraproject.org@wombatz.com wrote:
On Wed, Jun 22, 2022, at 8:01 AM, Doug Herr wrote:
But, I checked my virtual machine to see how it is connecting to the
printer...
Brother_DCP-L2550DW_series
This seems to be a much newer printer and does have Apple AirPrint. AirPrint was introduced in 2011 to support iPads. https://openprinting.github.io/driverless/01-standards-and-their-pdls/ summarizes the differences in the various Driverless Printing implementations. PDF is supported across the board, but there are several raster formats and also PDFm which is viewable with PDF viewers, but tailored for the capabilities of specific printer models. AirPrint and IPP use different raster formats, and Apple could change the details in the future, but currently it doesn't appear to be a big deal as most printers support both and conversion from IPP to Apple raster formats just requires simplifying the header, so probably easy to implement in the printer to gain IPP support.
I just thought to check the web interface that the printer provides and I see that connection protocols can be turned off.
This is at http://%7Bprinter IP}/net/net/protocol.html
Protocol Web Based Management (Web Server) HTTP Server Settings SNMP Advanced Settings LPD Advanced Settings Raw Port IPP HTTP Server Settings <<<<<<< CUPS driverless printing AirPrint Advanced Settings HTTP Server Settings Mopria <<<<<< also a "driverless printing" protocol Web Services Advanced Settings HTTP Server Settings Mobile printing for Windows Proxy Advanced Settings Network Scan SMTP Advanced Settings FTP Server FTP Client TFTP mDNS Advanced Settings LLMNR
The only two that are unchecked for the above list are "FTP Server" and "Proxy".
On Wed, 2022-06-22 at 11:35 -0300, George N. White III wrote:
I deleted that configuration and tried again using the CUPS web interface. This shows up as:
dnssd://Brother%20DCP-7055W._ipp._tcp.local/
I suspect this detection doesn't adequately check the details of the IPP support. Given the age of the printer, IPP may not be implemented "properly" by current standards.
Printing a test page again shows "Unable to locate printer". This happens both using the generic IPP driver and the specific model driver from the RPM package.
I looked at the Brother DCP-7055W Advanced User's Guide, which is dated 2012. I can't see any mention of IPP or AirPrint.
The User's Guide and Networking Guide are both pretty basic and mostly talk about using the manufacturer's admin utility for setup under Windows. However I was motivated to try the RPM package because it explicitly lists the DCP-7055W as one of the supported models.
poc
On Wed, 2022-06-22 at 08:01 -0700, Doug Herr wrote:
George might have the final answer, maybe your model will only work via a USP connection if using the brlaser option.
But, I checked my virtual machine to see how it is connecting to the printer...
Brother_DCP-L2550DW_series Brother_DCP-L2550DW_series (Idle, Accepting Jobs, Not Shared) Description: Brother DCP-L2550DW series Location: Driver: Brother DCP-L2550DW series, using brlaser v6 (grayscale, 2- sided printing) Connection: dnssd://Brother%20DCP-L2550DW%20series._pdl- datastream._tcp.local/?uuid=e3248000-80ce-11db-8000-3c2af4d12445 Defaults: job-sheets=none, none media=na_letter_8.5x11in sides=two-sided-long-edge
So it does seem to be using dnssd. This is a pretty generic F36 XFCE install so I did not do much to get that working, mostly just needed to start cups.
That looks like a different model, and a later one than mine I think.
poc
On Wed, 2022-06-22 at 14:01 -0300, George N. White III wrote:
On Wed, Jun 22, 2022 at 12:43 PM Doug Herr fedoraproject.org@wombatz.com wrote:
On Wed, Jun 22, 2022, at 8:01 AM, Doug Herr wrote:
But, I checked my virtual machine to see how it is connecting to the
printer...
Brother_DCP-L2550DW_series
This seems to be a much newer printer and does have Apple AirPrint.
Mine doesn't show Airprint but does show IPP (as well as FTP, LPD etc.)
poc
On Wed, 2022-06-22 at 14:01 -0300, George N. White III wrote:
AirPrint was introduced in 2011 to support iPads. https://openprinting.github.io/driverless/01-standards-and-their-pdls/ summarizes the differences in the various Driverless Printing implementations. PDF is supported across the board, but there are several raster formats and also PDFm which is viewable with PDF viewers, but tailored for the capabilities of specific printer models.
I have a HP printer in that boat. It proudly proclaims direct PDF printing (send it a PDF file, or plug a USB into the front with a PDF on it). But after a lot of digging around you find that it only supports a special PDF created by their driver program, no other PDF files are supported.
On Thu, 2022-06-23 at 13:02 +0930, Tim via users wrote:
On Wed, 2022-06-22 at 14:01 -0300, George N. White III wrote:
AirPrint was introduced in 2011 to support iPads. https://openprinting.github.io/driverless/01-standards-and-their-pdls/ summarizes the differences in the various Driverless Printing implementations. PDF is supported across the board, but there are several raster formats and also PDFm which is viewable with PDF viewers, but tailored for the capabilities of specific printer models.
I have a HP printer in that boat. It proudly proclaims direct PDF printing (send it a PDF file, or plug a USB into the front with a PDF on it). But after a lot of digging around you find that it only supports a special PDF created by their driver program, no other PDF files are supported.
So Non-Portable Document Format ...
poc
On Wed, 2022-06-22 at 12:32 +0100, Patrick O'Callaghan wrote:
(See ... for context)
I have a Brother All-in-one wireless laser printer/scanner which has worked for years using the manufacturer's driver blob. I now want to configure it using the printer-driver-brlaser package from the Fedora repo.
I've uninstalled the original Brother driver and deleted the printer config using the CUPS interface.
I then added a new printer using the KDE System Settings widget, and attempted to print a test page. This appears to go through, but then the queue status shows "Unable to locate printer".
I deleted that configuration and tried again using the CUPS web interface. This shows up as:
dnssd://Brother%20DCP-7055W._ipp._tcp.local/
Printing a test page again shows "Unable to locate printer". This happens both using the generic IPP driver and the specific model driver from the RPM package.
The CUPS systemd service and AVAHI daemon are both running, as is systemd-resolved, which handles DNS-SD (I reloaded the latter just in case.)
I'm out of ideas. To repeat: both printing and scanning work correctly with the manufacturer's driver, so it's not a hardware or connection problem.
I deleted and reconfigured, this time using the JetDirect option rather than IPP:
dnssd://Brother%20DCP-7055W._printer._tcp.local/
This seems to work, touch wood.
poc
On Thu, Jun 23, 2022 at 6:42 AM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Thu, 2022-06-23 at 13:02 +0930, Tim via users wrote:
On Wed, 2022-06-22 at 14:01 -0300, George N. White III wrote:
AirPrint was introduced in 2011 to support iPads. https://openprinting.github.io/driverless/01-standards-and-their-pdls/ summarizes the differences in the various Driverless Printing implementations. PDF is supported across the board, but there are several raster formats and also PDFm which is viewable with PDF viewers, but tailored for the capabilities of specific printer models.
I have a HP printer in that boat. It proudly proclaims direct PDF printing (send it a PDF file, or plug a USB into the front with a PDF on it). But after a lot of digging around you find that it only supports a special PDF created by their driver program, no other PDF files are supported.
So Non-Portable Document Format ...
PDFm is supposed to work with PDF viewers. I assume it just adds printer-specific metadata: things like which paper tray, duplex (double-sided) long or short edge binding, collating, stapling, etc.
On Wed, Jun 22, 2022 at 6:27 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Wed, 2022-06-22 at 14:01 -0300, George N. White III wrote:
On Wed, Jun 22, 2022 at 12:43 PM Doug Herr fedoraproject.org@wombatz.com wrote:
On Wed, Jun 22, 2022, at 8:01 AM, Doug Herr wrote:
But, I checked my virtual machine to see how it is connecting to the
printer...
Brother_DCP-L2550DW_series
This seems to be a much newer printer and does have Apple AirPrint.
Mine doesn't show Airprint but does show IPP (as well as FTP, LPD etc.)
Not sure where you see IPP and not AirPrint -- do you mean the printer's http configuration status page or the mdns entry? AirPrint shows up as IPP in mdns.
You can use:
% avahi-browse -r _printer._tcp + wlo1 IPv4 Canon MG7500 series _printer._tcp local + enp1s0 IPv4 Canon MG7500 series _printer._tcp local = wlo1 IPv4 Canon MG7500 series _printer._tcp local hostname = [DBF1D0000000.local] address = [192.168.2.244] port = [515] txt = ["Fax=F" "Scan=T" "Duplex=T" "Color=T" "UUID=00000000-0000-1000-8000-D8492FDBF1D0" "mac=D8:49:2F:DB:F1:D0" "usb_MDL=MG7500 series" "usb_MFG=Canon" "adminurl=http://DBF1D0000000.local." "note=" "pdl=application/octet-stream" "product=(Canon MG7500 series)" "ty=Canon MG7500 series" "priority=60" "qtotal=1" "rp=auto" "txtvers=1"] = enp1s0 IPv4 Canon MG7500 series _printer._tcp local hostname = [DBF1D0000000.local] address = [192.168.2.244] port = [515] txt = ["Fax=F" "Scan=T" "Duplex=T" "Color=T" "UUID=00000000-0000-1000-8000-D8492FDBF1D0" "mac=D8:49:2F:DB:F1:D0" "usb_MDL=MG7500 series" "usb_MFG=Canon" "adminurl=http://DBF1D0000000.local." "note=" "pdl=application/octet-stream" "product=(Canon MG7500 series)" "ty=Canon MG7500 series" "priority=60" "qtotal=1" "rp=auto" "txtvers=1"] ^CGot SIGINT, quitting.
On Thu, 2022-06-23 at 07:45 -0300, George N. White III wrote:
On Wed, Jun 22, 2022 at 6:27 PM Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Wed, 2022-06-22 at 14:01 -0300, George N. White III wrote:
On Wed, Jun 22, 2022 at 12:43 PM Doug Herr fedoraproject.org@wombatz.com wrote:
On Wed, Jun 22, 2022, at 8:01 AM, Doug Herr wrote:
But, I checked my virtual machine to see how it is connecting to the
printer...
Brother_DCP-L2550DW_series
This seems to be a much newer printer and does have Apple AirPrint.
Mine doesn't show Airprint but does show IPP (as well as FTP, LPD etc.)
Not sure where you see IPP and not AirPrint -- do you mean the printer's http configuration status page or the mdns entry?
Yes.
AirPrint shows up as IPP in mdns.
You can use:
% avahi-browse -r _printer._tcp + wlo1 IPv4 Canon MG7500 series _printer._tcp local
- enp1s0 IPv4 Canon MG7500 series
_printer._tcp local = wlo1 IPv4 Canon MG7500 series _printer._tcp local hostname = [DBF1D0000000.local] address = [192.168.2.244] port = [515] txt = ["Fax=F" "Scan=T" "Duplex=T" "Color=T" "UUID=00000000-0000-1000-8000-D8492FDBF1D0" "mac=D8:49:2F:DB:F1:D0" "usb_MDL=MG7500 series" "usb_MFG=Canon" "adminurl=http://DBF1D0000000.local." "note=" "pdl=application/octet-stream" "product=(Canon MG7500 series)" "ty=Canon MG7500 series" "priority=60" "qtotal=1" "rp=auto" "txtvers=1"] = enp1s0 IPv4 Canon MG7500 series _printer._tcp local hostname = [DBF1D0000000.local] address = [192.168.2.244] port = [515] txt = ["Fax=F" "Scan=T" "Duplex=T" "Color=T" "UUID=00000000-0000-1000-8000-D8492FDBF1D0" "mac=D8:49:2F:DB:F1:D0" "usb_MDL=MG7500 series" "usb_MFG=Canon" "adminurl=http://DBF1D0000000.local." "note=" "pdl=application/octet-stream" "product=(Canon MG7500 series)" "ty=Canon MG7500 series" "priority=60" "qtotal=1" "rp=auto" "txtvers=1"] ^CGot SIGINT, quitting.
$ avahi-browse -r _printer._tcp + enp4s0 IPv4 Brother DCP-7055W _printer._tcp local + enp4s0 IPv6 Brother DCP-7055W @ Bree _printer._tcp local + enp4s0 IPv4 Brother DCP-7055W @ Bree _printer._tcp local + lo IPv4 Brother DCP-7055W @ Bree _printer._tcp local = enp4s0 IPv6 Brother DCP-7055W @ Bree _printer._tcp local hostname = [Bree.local] address = [fe80::f568:96d8:1d91:c12e] port = [0] txt = [] = enp4s0 IPv4 Brother DCP-7055W @ Bree _printer._tcp local hostname = [Bree.local] address = [192.168.178.21] port = [0] txt = [] = lo IPv4 Brother DCP-7055W @ Bree _printer._tcp local hostname = [Bree.local] address = [127.0.0.1] port = [0] txt = [] = enp4s0 IPv4 Brother DCP-7055W _printer._tcp local hostname = [BRN008092BBFAB5.local] address = [192.168.178.26] port = [515] txt = ["TBCP=F" "Transparent=T" "Binary=T" "PaperCustom=T" "Duplex=F" "Copies=T" "Color=F" "usb_MDL=DCP-7055W" "usb_MFG=Brother" "priority=75" "adminurl=http://BRN008092BBFAB5.local./" "product=(Brother DCP-7055W)" "ty=Brother DCP-7055W" "rp=duerqxesz5090" "pdl=application/vnd.brother-hbp" "qtotal=1" "txtvers=1"]
poc
Tim:
I have a HP printer in that boat. It proudly proclaims direct PDF printing (send it a PDF file, or plug a USB into the front with a PDF on it). But after a lot of digging around you find that it only supports a special PDF created by their driver program, no other PDF files are supported.
Patrick O'Callaghan wrote:
So Non-Portable Document Format ...
The ironies of commercial decisions...
I suspect they went with something like that because the infrastructure was there for them to start with (creating a standalone file for sneakernet, people are used to the idea of a print to PDF file option, and they may have used the existing code to start from). But I can't imagine why they didn't just go with standard PDF files, perhaps some Adobe fees they didn't want to pay.
I recall years ago one of the print to file options in programs being print to a PostScript file. I don't see that any more.
On Thu, 2022-06-23 at 12:41 +0100, Patrick O'Callaghan wrote:
$ avahi-browse -r _printer._tcp
- enp4s0 IPv4 Brother DCP-7055W
_printer._tcp local
- enp4s0 IPv6 Brother DCP-7055W @ Bree
_printer._tcp local
- enp4s0 IPv4 Brother DCP-7055W @ Bree
_printer._tcp local + lo IPv4 Brother DCP-7055W @ Bree _printer._tcp local = enp4s0 IPv6 Brother DCP-7055W @ Bree _printer._tcp local hostname = [Bree.local] address = [fe80::f568:96d8:1d91:c12e] port = [0] txt = [] = enp4s0 IPv4 Brother DCP-7055W @ Bree _printer._tcp local hostname = [Bree.local] address = [192.168.178.21] port = [0] txt = [] = lo IPv4 Brother DCP-7055W @ Bree _printer._tcp local hostname = [Bree.local] address = [127.0.0.1] port = [0] txt = [] = enp4s0 IPv4 Brother DCP-7055W _printer._tcp local hostname = [BRN008092BBFAB5.local] address = [192.168.178.26] port = [515] txt = ["TBCP=F" "Transparent=T" "Binary=T" "PaperCustom=T" "Duplex=F" "Copies=T" "Color=F" "usb_MDL=DCP-7055W" "usb_MFG=Brother" "priority=75" "adminurl=http://BRN008092BBFAB5.local./" "product=(Brother DCP-7055W)" "ty=Brother DCP-7055W" "rp=duerqxesz5090" "pdl=application/vnd.brother-hbp" "qtotal=1" "txtvers=1"]
poc
Also:
$ avahi-browse -t -a|grep Brother + enp4s0 IPv6 Brother DCP-7055W @ Bree _ipps._tcp local + enp4s0 IPv4 Brother DCP-7055W @ Bree _ipps._tcp local + lo IPv4 Brother DCP-7055W @ Bree _ipps._tcp local + enp4s0 IPv6 Brother DCP-7055W @ Bree _ipp._tcp local + enp4s0 IPv4 Brother DCP-7055W @ Bree _ipp._tcp local + enp4s0 IPv4 Brother DCP-7055W _ipp._tcp local + lo IPv4 Brother DCP-7055W @ Bree _ipp._tcp local + enp4s0 IPv6 Brother DCP-7055W @ Bree _printer._tcp local + enp4s0 IPv4 Brother DCP-7055W @ Bree _printer._tcp local + enp4s0 IPv4 Brother DCP-7055W _printer._tcp local + lo IPv4 Brother DCP-7055W @ Bree _printer._tcp local + enp4s0 IPv4 Brother DCP-7055W _http._tcp local + enp4s0 IPv4 Brother DCP-7055W _pdl-datastream._tcp local
However as I mentioned separately, it's now working after reconfiguring as LPD rather than IPP. No idea why but I'll take it.
poc
On Thu, Jun 23, 2022 at 09:30:38PM +0930, Tim via users wrote:
Tim:
I have a HP printer in that boat. It proudly proclaims direct PDF printing (send it a PDF file, or plug a USB into the front with a PDF on it). But after a lot of digging around you find that it only supports a special PDF created by their driver program, no other PDF files are supported.
Patrick O'Callaghan wrote:
So Non-Portable Document Format ...
The ironies of commercial decisions...
I have a 10+ year old Ricoh 3500N color laser that claims to accept PDF files. It is on my lan as host "R3500", a postscript printer and connects using CUPS and an IPP socket.
I never considered whether the cups drivers were converting my PDF files to PS before transmitting. So today I tried using netcat to send PDF files directly to the printer
$ nc R3500 {port_number} < {pdf_file}
When I used port 631 (IPP) I got HTTP errors (400 BAD REQEUEST)
But when I used port 9100 (JetDirect) 5 different pdf files of varying complexity printed properly.
Jon
On Thu, 2022-06-23 at 13:15 -0400, Jon LaBadie wrote:
I have a 10+ year old Ricoh 3500N color laser that claims to accept PDF files. It is on my lan as host "R3500", a postscript printer and connects using CUPS and an IPP socket.
I never considered whether the cups drivers were converting my PDF files to PS before transmitting.
In my case, I just tried sneakernetting PDF files to it over USB (mine's a similarly vintage HP LaserJet P3015).
In the past, I remember CUPS was rather good at detecting whether it was being sent prepared data that could go direct to the printer, or it was receiving Linux internal printing instructions that had to go through the driver. Though, as far as I knew, that was detecting print-ready PostScript, or the printers own page language.
There was also the option of manually setting up a RAW queue, where you set print-ready data to it, and it just passed it along to the printer.
So today I tried using netcat to send PDF files directly to the printer
$ nc R3500 {port_number} < {pdf_file}
When I used port 631 (IPP) I got HTTP errors (400 BAD REQEUEST)
But when I used port 9100 (JetDirect) 5 different pdf files of varying complexity printed properly.
That makes sense. The IPP port simply expecting the usual data, it's special port may be more versatile.
Out of curiosity, if you pipe a PostScript file through to either port, does it handle that? (Assuming the printer supports that format, in the first place.)
On Fri, Jun 24, 2022 at 02:24:37PM +0930, Tim via users wrote:
On Thu, 2022-06-23 at 13:15 -0400, Jon LaBadie wrote:
I have a 10+ year old Ricoh 3500N color laser that claims to accept PDF files. It is on my lan as host "R3500", a postscript printer and connects using CUPS and an IPP socket.
I never considered whether the cups drivers were converting my PDF files to PS before transmitting.
In my case, I just tried sneakernetting PDF files to it over USB (mine's a similarly vintage HP LaserJet P3015).
In the past, I remember CUPS was rather good at detecting whether it was being sent prepared data that could go direct to the printer, or it was receiving Linux internal printing instructions that had to go through the driver. Though, as far as I knew, that was detecting print-ready PostScript, or the printers own page language.
There was also the option of manually setting up a RAW queue, where you set print-ready data to it, and it just passed it along to the printer.
So today I tried using netcat to send PDF files directly to the printer
$ nc R3500 {port_number} < {pdf_file}
When I used port 631 (IPP) I got HTTP errors (400 BAD REQEUEST)
But when I used port 9100 (JetDirect) 5 different pdf files of varying complexity printed properly.
That makes sense. The IPP port simply expecting the usual data, it's special port may be more versatile.
Out of curiosity, if you pipe a PostScript file through to either port, does it handle that? (Assuming the printer supports that format, in the first place.)
I've stuck with PS capable printers for over 30 years, since the LaserJet III? Was it III+ or IIIs, something like that.
My Ricoh 3500 handled netcat'ed postscript files similarly to pdf file. I.e. sent to port 9100 (JetDirect) it printed properly. Sent to port 631 (IPP) I got an "HTTP/1.1 400 Bad Request" error.
On Fri, Jun 24, 2022 at 2:40 AM Jon LaBadie jonfu@jgcomp.com wrote:
On Fri, Jun 24, 2022 at 02:24:37PM +0930, Tim via users wrote:
On Thu, 2022-06-23 at 13:15 -0400, Jon LaBadie wrote:
I have a 10+ year old Ricoh 3500N color laser that claims to accept PDF files. It is on my lan as host "R3500", a postscript printer and connects using CUPS and an IPP socket.
I never considered whether the cups drivers were converting my PDF files to PS before transmitting.
PostScript is a full programming language, so it is much harder to provide security for PostScript: https://www.theregister.com/2017/01/31/postscript_bug/, PDF can embed scripts, but those are more of an issue for viewers than low-end printers.
PDF has better support for the Unicode fonts commonly used for non-Western language documents (for me, using English, but with colleagues from all over, names of people and places are problematic for PostScript producing applications).
-
Doug Herr -
George N. White III -
Jon LaBadie -
Patrick O'Callaghan -
Tim