26 Apr
2013
26 Apr
'13
7:01 a.m.
Jason White <jason(a)jasonjgw.net> writes:
Trent W. Buck <trentbuck(a)gmail.com> wrote:
Good idea. I have at least one working printer, so I can tshark that
traffic to work out how to speak IPP.
I have a printer that's being strange. Since
the printer itself runs
ipp, I'm trying to send it jobs directly with
lp/lpstat/loptions/cancel &c, without talking to cupsd.
I get some responses, but nothing very helpful.
Does Wireshark/Tshark give you any clues as to what's going wrong with the
exchange between host and printer?
Looking at some sample traffic might be enough to allow you to avoid reading
(most of the) RFCs... Or perhaps not.