Bug 26579 - Remote access to cups fails on ipv6 addresses
Summary: Remote access to cups fails on ipv6 addresses
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-05-01 18:05 CEST by james Whitby
Modified: 2020-05-02 02:42 CEST (History)
0 users

See Also:
Source RPM: cups-2.2.11-2.mga7.src.rpm
CVE:
Status comment:


Attachments

Description james Whitby 2020-05-01 18:05:09 CEST
Having reinstalled task printing at least twic. I have found the problem.
The cups daemon will not respond to ipv6 addresses.

Try to access from a remote using ipv6, get bad request on screen.
Telnet to same address on port 631, get connected.
Use the ipv4 address, works fine.

It appears the system is handling the ipv6 OK ( telnet works ), but cups is not.

A second, but related item is a fresh install will not allow cups-browserd to start. Used the default cupsd.conf file its ok.

What ever addditional info I can supply, please let me know.
Comment 1 Lewis Smith 2020-05-01 19:24:20 CEST
Thank you for reporting this, and the offer to provide more information.

Assigning this to tv, being the active cups maintainer.

Source RPM: (none) => cups-2.2.11-2.mga7.src.rpm
Assignee: bugsquad => thierry.vignaud
URL: http://jameswhitby.net:631 => (none)

Comment 2 james Whitby 2020-05-02 02:00:16 CEST
Now I feel kinda stupid,

If I use the literal ipv6 address it works.
E.G.: http://[2600:4040:1269:100:6e62:6dff:feec:930f]:631

But not with FQDN
E.G.: http://jameswhitby.net:631

I'm missing something somewhere.
Comment 3 james Whitby 2020-05-02 02:42:40 CEST
So much to learn, sp little time.

FQDN means node name also in cups. Not just the network.

I did change it to net address only in cupsd.conf

Works just fine
So, I'm closing the bug as solved.

Resolution: (none) => FIXED
Status: NEW => RESOLVED


Note You need to log in before you can comment on or make changes to this bug.