Severity: minor
> If you specify an address, ie: http_port 127.0.0.1:3128 it works just
fine, but
> there's no way to speficy "listen to ALL interfaces in IPV4 mode on
port 3128",
> which was possible in 3.0 ;\
3.0 in fact has the wildcard *:port (AKA "listen on ALL possible
addresses"), but did not have IPv6 support. This wildcard remains
unchanged in 3.1 and does so via an IPv6 port with v4mapping enabled.
This is what you can see with netstat.
There are two problems you might have hit:
Problem 1:
"eveything stoped working" - AKA Squid starts responding with "access
denied".
Cause:
Your clients have probably started connecting to Squid using IPv6.
But you have not updated the access control settings in squid.conf to
permit the network IPv6 ranges or localhost-v6.
Solution: update squid.conf.
Problem 2:
"eveything stoped working" - AKA TCP connections cannot be made at all
to Squid. They just die or timeout.
Cause:
This only happens on Debian kernels which have had their default
v4mapping abilities broken. Squid 3.1 requires v4mapping in the TCP stack.
Solution: update squid.conf
To force listening on the IPv4-only subset of address space use the
explicit IPv4-only wildcard address 0.0.0.0:3128. You will likely then
hit bug 581901 as outbound sockets are also prevented to do v4mapping
failover connections. This is fixed in the 3.1.4 release.
Amos
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
