On 10/04/2012 1:11 a.m., Markus Moeller wrote:
But it should be possible to determine that automatically (e.g. if the
bind on ::1 fails try ipv4) shouldn' it ?
Yes. The socket handling is a bit strange in 3.1 though. Failover does
not work on helpers. Mostly because its an internal channel, Squid is
running the app at both ends, both are opening localhost / ::1.
Going back and reading your report after some sleep, it would seem you
did not fully disable IPv6 or restart Squid after changing such
fundamental detail. The Squid startup sequence probes to determine
whether an IPv6 stack is present, and what type. The "localhost" default
values depend on those probes results, with ::1 preferred if available.
Amos
Thank you
Markus
"Amos Jeffries" <squid3@xxxxxxxxxxxxx> wrote in message
news:4F82CD96.8060708@xxxxxxxxxxxxx...
On 7/04/2012 12:08 p.m., Markus Moeller wrote:
It looks like to be an ipv6 problem. I disabled ipv6 on my OpenSuse,
but squid wants to bind on ::1 (ipv6 localhost) which fails.
Is this a bug ?
In the documentation yes. It has been fixed and will say the correct
ipv4/ipv6 default in later confg manuals.
You need to specify the "ipv4" option to get Squid to contect helpers
on IPv4-only TCP sockets.
Amos
