Bug 113481
| Summary: | Cups configuration configures wrong interface | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | David Anderson <david> |
| Component: | redhat-config-printer | Assignee: | Tim Waugh <twaugh> |
| Status: | CLOSED CANTFIX | QA Contact: | David Lawrence <dkl> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 9 | CC: | mattdm, orion |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-01-02 19:06:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
David Anderson
2004-01-14 14:00:12 UTC
Forgot to mention - because CIPE wasn't active, CUPS fell over on trying to bind the interface on startup. redhat-config-printer shouldn't try to get CUPS to listen on inactive interfaces because it prevents CUPS from starting. How exactly did you configure print sharing? Using the redhat-config-printer tool? What settings did you change, exactly? Thanks. Yes, using redhat-config-printer I edited the "sharing" configuration for each of my 3 printers to share with the local net (10.0.0.0/8). Although I think the first time I did it wrongly and entered 10.0.0.0/255.255.255.0 = 10.0.0.0/24 The CIPE interface had IP 9.8.7.2 (obviously non-routeable) I'm having basically the same problem, but in my case it is caused by and alias. I have ifcfg-eth0:0 which defines an alias on the same subnet - used for virtual hosting a website. A Listen line is added only for the alias, not for the primary interface. This essentially breaks printing on my network until I edit /etc/cups/cupds.conf by hand after every configuration change. Also, there should be a way to configure which interface(s) cups should listen on. Red Hat apologizes that these issues have not been resolved yet. We do want to make sure that no important bugs slip through the cracks. Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc. They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/) for security updates only. If this is a security issue, please reassign to the 'Fedora Legacy' product in bugzilla. Please note that Legacy security update support for these products will stop on December 31st, 2006. If this is not a security issue, please check if this issue is still present in a current Fedora Core release. If so, please change the product and version to match, and check the box indicating that the requested information has been provided. If you are currently still running Red Hat Linux 7.3 or 9, please note that Fedora Legacy security update support for these products will stop on December 31st, 2006. You are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a security issue, please change the product as necessary. We thank you for your help, and apologize again that we haven't handled these issues to this point. Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc. f you are currently still running Red Hat Linux 7.3 or 9, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Closing as CANTFIX. |