ipptest-ing get-printer-attributes with a Canon iR6000
Kurt Pfeifle
kpfeifle at danka.de
Thu Jul 27 15:09:28 PDT 2006
The following info concerns a Canon iR6000 printer. It may be useful
to determine future improvements (putting exceptions/workarounds for
certain vendors/models into the code) when the snmp backend probes
for valid IPP device URIs.
I used the ipptest utility (in the "test" subdir of the self-compiled
sources) to probe the printer:
./ipptest -v ipp://10.162.2.94:631/ get-printer-attributes.test
---------------------------------------------------------------
"get-printer-attributes.test":
Get-Printer-Attributes:
attributes-charset (charset) = "utf-8"
attributes-natural-language (language) = "en"
printer-uri (uri) = "ipp://10.162.2.94:631/"
Get printer attributes using get-printer-attributes [
With this device URI the output hangs with the open "[" shown on the
last line (I interrupted after 4 minutes).
The next probe was with a different device URI:
./ipptest -v ipp://10.162.2.94:631/ipp get-printer-attributes.test
------------------------------------------------------------------
"get-printer-attributes.test":
Get-Printer-Attributes:
attributes-charset (charset) = "utf-8"
attributes-natural-language (language) = "en"
printer-uri (uri) = "ipp://10.162.2.94:631/ipp"
Get printer attributes using get-printer-attributes [FAIL]
RECEIVED: 889 bytes in response
status-code = 0000 (successful-ok)
EXPECTED: printer-info
EXPECTED: printer-more-info
EXPECTED: printer-state-reasons
attributes-charset (charset) = "utf-8"
attributes-natural-language (language) = "en"
printer-uri-supported (uri) = "http://10.162.2.94/ipp" "ipp://10.162.2.94/ipp"
uri-security-supported (keyword) = "none" "none"
uri-authentication-supported (keyword) = "none" "none"
printer-name (namelang) = "IS_1050",de
printer-location (textlang) = "",de
printer-make-and-model (textlang) = "Canon iR5000-6000",de
printer-state (enum) = 3
ipp-versions-supported (keyword) = "1.0" "1.1"
operations-supported (enum) = 2 10 8 9 11 4
charset-configured (charset) = "utf-8"
charset-supported (charset) = "utf-8"
natural-language-configured (language) = "de"
generated-natural-language-supported (language) = "de"
document-format-default (mimetype) = "application/octet-stream"
document-format-supported (mimetype) = "application/octet-stream" "application/vnd.hp-PCL"
printer-is-accepting-jobs (boolean) = true
queued-job-count (integer) = 0
pdl-override-supported (keyword) = "not-attempted"
printer-up-time (integer) = 539641
compression-supported (keyword) = "none"
Same result can be obtained with /ipp/port1, /ipp/port2, /ipp/bullshit
(sorry, couldn't resist to try that :-) -- however, a simple /bullshit
yields this result:
./ipptest -v ipp://10.162.2.94:631/bullshit get-printer-attributes.test
-----------------------------------------------------------------------
"get-printer-attributes.test":
Get-Printer-Attributes:
attributes-charset (charset) = "utf-8"
attributes-natural-language (language) = "en"
printer-uri (uri) = "ipp://10.162.2.94:631/bullshit"
Get printer attributes using get-printer-attributes [FAIL]
ERROR 0406 (Not Found) @ Thu Jul 27 23:57:30 2006
I'll try to write a shell script that crawls the LAN, automatically
probes all available printers around here and stores the result in
a set of files.
If anyone has done this already, let me know.
Cheers,
Kurt
More information about the cups
mailing list