# # IPP
APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

IPP

I've removed advertising from most of this site and will eventually clean up the few pages where it remains.

While not terribly expensive to maintain, this does cost me something. If I don't get enough donations to cover that expense, I will be shutting the site down in early 2020.

If you found something useful today, please consider a small donation.



Some material is very old and may be incorrect today

© March 2005 Tony Lawrence

Internet Printing Protocol which is what CUPS uses. You may know that if you fire up your web browser and point it at http://localhost:631 you get the CUPS administration screen, but did you realize that CUPS itself sends print and status requests to the same port?

There's nothing secret about this: CUPS documentation (which you can find at http://localhost:631/ipp.html ) explains all of it. If you wanted to, you could control CUPS directly with HTTP requests. We can demonstrate that with a little tom-foolery: let's create a little shell script that we'll run on port 631. First the script, which logs attempted connections.

#!/bin/bash
echo "Connection" >> /tmp/fakecupsd
date >> /tmp/fakecupsd
read line
echo $line >> /tmp/fakecupsd
 

We turn that on by creating a file in /etc/xinetd, stopping the real cups, and telling xinetd to start using ours for port 631 connections.

# cat /etc/xinetd.d/fakecups
service ipp
{
        socket_type     = stream
        wait            = no
        user            = root
        server          = /root/fakecups
}
/etc/init.d/cups stop
kill -1 `cat /var/run/xinetd.pid`
 

Now do an "lpstat -v" - it will hang, so ctrl-c it, and look in /tmp/fakecupsd. You'll see something like this repeated multiple times:

Connection
Sat Mar 26 05:36:30 EST 2005
POST / HTTP/1.1
 

The reason lpstat hangs is that it is sending more data with that http post, which the real cups daemon would process and acknowledge.


If you found something useful today, please consider a small donation.



Got something to add? Send me email.





(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

->
-> IPP

1 comment


Inexpensive and informative Apple related e-books:

iOS 8: A Take Control Crash Course

Digital Sharing Crash Course

Take Control of High Sierra

Take Control of the Mac Command Line with Terminal, Second Edition

Photos: A Take Control Crash Course





More Articles by © Tony Lawrence



Related Articles






Thu Mar 31 13:46:18 2005: 264   drag



I prefer using IPP over using something like SAMBA. It seems much nicer to me.

Windows clients support IPP since Windows 2000, and I've tried it and it works very well... for me. IPP basicly turns your computer in a postscript-compatable networked printer.

But I've been told that Windows IPP support is sub-par and usually SAMBA is going to be better for large numbers of windows clients.

Although if you use Unix ones, especially ones that use CUPS (ie: Linux or FreeBSD or OS 10.2(10.2.4(?)) or newer) then it rocks.

--Drag

------------------------


Printer Friendly Version


Related Articles

Have you tried Searching this site?

This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more.

Contact us


Printer Friendly Version





I am fascinated by religion. (That's a completely different thing from believing in it!) (Douglas Adams)




Linux posts

Troubleshooting posts


This post tagged:

CUPS

Printing



Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode