According to my notes [1], IPP uses TCP/631 for printing and UDP/631 for
browsing. This matches with a quick search in the CUPS docs, and other
search results. One page that states this pretty explicit is [2]:
cupsd uses UDP port 631 for sending and receiving "IPP browsing"
information.
Although a patch seems to be overkill for such a trivial change, it has
been requested to send one. So, here you go -- patch against macro.IPP
attached. :)
(Note that this covers the client to server part only. In case of a
tight firewall that restricts outgoing connections from the server, the
server itself still would not be able to browse other servers.)
karsten
[1] http://lists.shorewall.net/~kb/action.AllowCUPS
[2] http://en.opensuse.org/SDB:CUPS_in_a_Nutshell
--
[ESR] Eric S. Raymond: "How To Ask Questions The Smart Way"
http://www.catb.org/~esr/faqs/smart-questions.html
[SGT] Simon G. Tatham: "How to Report Bugs Effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
Index: Shorewall-common/macro.IPP
===================================================================
--- Shorewall-common/macro.IPP (revision 5936)
+++ Shorewall-common/macro.IPP (working copy)
@@ -9,4 +9,5 @@
#ACTION SOURCE DEST PROTO DEST SOURCE ORIGINAL RATE USER/
# PORT PORT(S) DEST LIMIT GROUP
PARAM - - tcp 631
+PARAM - - udp 631
#LAST LINE -- ADD YOUR ENTRIES BEFORE THIS ONE -- DO NOT REMOVE
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Shorewall-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-devel
