Hey,
I guess we cannot do much about it. We do not support IPv6 in IPFire 2.
I think it was a bit of a mistake of the squid team to assume that IPv6 is available everywhere. It also does not make their job much easier - I think.
However, we should compile it with —disable-ipv6 as long as that is supported and that is the end of the story.
I have no idea why it needs to connect to itself anyways because we do not tell it to listen on localhost.
-Michael
On 31 Jan 2019, at 20:06, Matthias Fischer matthias.fischer@ipfire.org wrote:
Hi,
I'm testing 'squid 4.5' with the latest patches. Its running, but...:
Despite IPv6 being enabled in configure options, one of these patches (http://www.squid-cache.org/Versions/v4/changesets/squid-4-568e66b7c64e0d7873...) leads to "WARNING: BCP 177 violation. Detected non-functional IPv6 loopback." during startup.
I found an explanation regarding 'squid 3.5.7' here: (http://lists.squid-cache.org/pipermail/squid-users/2015-August/004930.html)
"IPv6: improve BCP 177 compliance
Since early 2012 it has been mandatory for new or upgraded Internet connected machinery and software to support IPv6 ad use it in preference over IPv4.
Squid IPv6 behaviour has followed these practices since well before the guidelines became a BCP. Over the years it has also grown into a well-tested and widely used feature.
The --disable-ipv6 build option is now deprecated. It is long past time to fix whatever network brokenness you may have that made it look attractive in past years.
Squid-3.5.7 and later will perform IPv6 availability tests on startup in all builds.
- Where IPv6 is unavailable Squid will continue exactly as it would
have had the build option not been used.
These Squid can have the build option removed now.
- Where IPv6 is detected but --disable-ipv6 prevents use Squid will log
"WARNING: BCP 177 violation".
Please test whether you can rebuild with IPv6 enabled."
IPv6 is enabled, but I get these warning. Anything we could/should do? Opinions?
Best, Matthias