From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: squid 4.5. + latest patches => BCD 177 violation Date: Fri, 01 Feb 2019 16:59:55 +0000 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8791348924053590131==" List-Id: --===============8791348924053590131== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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 av= ailable everywhere. It also does not make their job much easier - I think. However, we should compile it with =E2=80=94disable-ipv6 as long as that is s= upported and that is the end of the story. I have no idea why it needs to connect to itself anyways because we do not te= ll it to listen on localhost. -Michael > On 31 Jan 2019, at 20:06, Matthias Fischer = wrote: >=20 > Hi, >=20 > I'm testing 'squid 4.5' with the latest patches. Its running, but...: >=20 > Despite IPv6 being enabled in configure options, one of these patches > (http://www.squid-cache.org/Versions/v4/changesets/squid-4-568e66b7c64e0d78= 73b9575b0dc60886805a2fc6.patch) > leads to "WARNING: BCP 177 violation. Detected non-functional IPv6 > loopback." during startup. >=20 > I found an explanation regarding 'squid 3.5.7' here: > (http://lists.squid-cache.org/pipermail/squid-users/2015-August/004930.html) >=20 > "IPv6: improve BCP 177 compliance >=20 > 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. >=20 > 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. >=20 > 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. >=20 > Squid-3.5.7 and later will perform IPv6 availability tests on startup in > all builds. >=20 > - Where IPv6 is unavailable Squid will continue exactly as it would > have had the build option not been used. >=20 > These Squid can have the build option removed now. >=20 > - Where IPv6 is detected but --disable-ipv6 prevents use Squid will log > "WARNING: BCP 177 violation". >=20 > Please test whether you can rebuild with IPv6 enabled." >=20 > IPv6 is enabled, but I get these warning. Anything we could/should do? > Opinions? >=20 > Best, > Matthias --===============8791348924053590131==--