Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 332771 - Squid-3.1.6: SSL does not work with USE-flag "ipv6" disabled
Summary: Squid-3.1.6: SSL does not work with USE-flag "ipv6" disabled
Status: RESOLVED DUPLICATE of bug 331965
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: High major (vote)
Assignee: Gentoo Network Proxy Developers (OBSOLETE)
URL: http://www.spinics.net/lists/squid/ms...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-14 19:09 UTC by Guenther Brunthaler
Modified: 2010-08-16 06:33 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Guenther Brunthaler 2010-08-14 19:09:42 UTC 
When emerging >=squid-3.1.6 with USE="-ipv6", any attempt to access an SSL URL results in the error massage  and the access fails.

Reproducible: Always

Steps to Reproduce:
1.USE="-ipv6" emerge -av1 ">=net-proxy/squid-3.1.6"
2.Start it.
3.Try to open a https Website
Actual Results:  
The access (allowed by squid ACL configuration) fails. Error message "comm_open: socket failure: (97) Address family not supported by protocol" in "/var/log/squid/cache.log".

Expected Results:  
No such error message. Access should be granted or denied depending on squid configuration, but not just fail due to a socket error.

Some people "fixed" that bug by re-enabling ipv6 in the kernel.

However, this is a kludge rather than a fix. Also, enabling or disabling IPv6 is a system-wide issue with all sorts of consequences, such as modified Firewall configuration.

Squid has a --disable-ipv6 configure option, and it should honor it.

Note that this is clearly an upstream bug. Nevertheless, it affects the functionality of the USE flag, so we might consider adding a patch.
Comment 1 Alin Năstac (RETIRED) gentoo-dev 2010-08-16 06:33:15 UTC 

*** This bug has been marked as a duplicate of bug 331965 ***