Re: Configuring a printer with DNS-SD

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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.


--
Jon H. LaBadie                  jonfu@xxxxxxxxxx
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux