All of lore.kernel.org
 help / color / mirror / Atom feed
From: Solomon Peachy <pizza@shaftnet.org>
To: Dave Close <dave@compata.com>
Cc: printing-users@lists.linux.dev
Subject: Re: CUPS and IPP strangeness
Date: Thu, 31 Jul 2025 08:22:45 -0400	[thread overview]
Message-ID: <aItgFWTHvLF8V3ct@shaftnet.org> (raw)
In-Reply-To: <202507300615.56U6Feav3458581@d9020.compata.com>

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

On Tue, Jul 29, 2025 at 11:15:40PM -0700, Dave Close wrote:
>   E [29/Jul/2025:22:03:18 -0700] Returning IPP client-error-bad-request
>   for Send-Document (ipp://localhost:631/printers/PF0) from localhost
> 
> That sure look to me like CUPS is trying to send IPP traffic to this
> printer. That certainly won't work, port 631 is not open on this printer.
> I've restarted CUPS without effect. What can I do to fix this?

To me this reads that something sent the _CUPS server_ a "bad" IPP 
request; if it was talking to the printer via JD the URI would include 
the printer's address/name ("pf0") instead of "localhost".

> My major task on this network is to port it to a new system running a
> much more recent OS. At this time, CUPS is running on CentOS 6 and is
> version cups-1.4.2-81.el6_10.x86_64. I need to keep it running awhile
> longer.

I see no reason why you'd need to keep such an old CUPS version around; 
as an example I currently have a CUPS queue talking to a Brother printer 
via JetDirect with CUPS 2.4.x.  It works more reliably than the 
printer's native driverless IPP functionality..

 - Solomon
-- 
Solomon Peachy			      pizza at shaftnet dot org (email&xmpp)
                                      @pizza:shaftnet dot org   (matrix)
Dowling Park, FL                      speachy (libera.chat)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2025-07-31 13:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-30  6:15 CUPS and IPP strangeness Dave Close
2025-07-31 12:22 ` Solomon Peachy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=aItgFWTHvLF8V3ct@shaftnet.org \
    --to=pizza@shaftnet.org \
    --cc=dave@compata.com \
    --cc=printing-users@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.