[Bug 737039] New: Cupsd does not listen for browsing announcements
https://bugzilla.novell.com/show_bug.cgi?id=737039 https://bugzilla.novell.com/show_bug.cgi?id=737039#c0 Summary: Cupsd does not listen for browsing announcements Classification: openSUSE Product: openSUSE 12.1 Version: Final Platform: x86-64 OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Printing AssignedTo: jsmeix@suse.com ReportedBy: bartoschek@or.uni-bonn.de QAContact: jsmeix@suse.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.7 (KHTML, like Gecko) Chrome/16.0.912.63 Safari/535.7 We use cups servers that announce printers to the network. With opensuse 12.1 the cupsd only binds to localhost and not to all interface. I have enabled the following checkbox: Yast -> Printers -> Print via Network -> "Accept Printer Announcements from CUPS Servers" The drop box "General Setting" is set to "accept all announcements from anywhere". However cupsd still does not listen to any connection. The firewall is properly configured pass port 631. Reproducible: Always Steps to Reproduce: 1. 2. 3. I've manually added Listen *:631 to the cupsd.conf. However the remote printers still do not appear. Wireshark tells me that the printer announcements are received. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=737039 https://bugzilla.novell.com/show_bug.cgi?id=737039#c1 Johannes Meixner <jsmeix@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WORKSFORME Summary|Cupsd does not listen for |Cupsd does not get browsing |browsing announcements |announcements if firewall | |runs --- Comment #1 from Johannes Meixner <jsmeix@suse.com> 2011-12-15 11:50:52 UTC --- It works for me. Since a long time (i.e. since CUPS 1.2) the cupsd only binds to localhost and not to all interface, see "Configuring CUPS in the Network" in http://en.opensuse.org/SDB:CUPS_in_a_Nutshell This is intentionally for security reasons, read http://en.opensuse.org/SDB:CUPS_and_SANE_Firewall_settings Some hints: If you really need a firewall in your internal network: Is the IPP port 631 open also for UDP broadcasts in your firewall? (UDP broadcasts need to be explicitly opened in the firewall.) Does it work when you switch off your firewall for a test? # netstat -nap | grep cups should show you something like ---------------------------------------------------------------------------- tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 29999/cupsd tcp 0 0 ::1:631 :::* LISTEN 29999/cupsd udp 0 0 0.0.0.0:631 0.0.0.0:* 29999/cupsd unix 2 [ ACC ] STREAM LISTENING 2852732 29999/cupsd /var/run/cups/cups.sock ---------------------------------------------------------------------------- (note the "udp" entry). You do not need "Listen *:631" in cupsd.conf, only ---------------------------------------------------------------------------- Listen localhost:631 Listen /var/run/cups/cups.sock .. Browsing On BrowseOrder allow,deny BrowseAllow all BrowseLocalProtocols CUPS ---------------------------------------------------------------------------- is sufficient. Note that Bugzilla is no replacement for support, see http://en.opensuse.org/openSUSE:Submitting_bug_reports -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=737039 https://bugzilla.novell.com/show_bug.cgi?id=737039#c2 Christoph Bartoschek <bartoschek@or.uni-bonn.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Major |Critical --- Comment #2 from Christoph Bartoschek <bartoschek@or.uni-bonn.de> 2011-12-15 12:37:52 UTC --- You are right. The firewall settings were wrong. This is embarassing. However you disappoint me with the last comment. I would not file a bug report if I was not sure that it is a bug. In this case I was not careful enough. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=737039 https://bugzilla.novell.com/show_bug.cgi?id=737039#c3 --- Comment #3 from Johannes Meixner <jsmeix@suse.com> 2011-12-15 13:38:57 UTC --- Don't take the "Bugzilla is no replacement for support" comment personally when it does not apply to you. It is only meant as a preventive note to avoid false expectations. If you are sure an issue is a bug, please file a bug report. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com