On 18/01/2016 11:13 p.m., Henri Wahl wrote: > Hi list, > Since I upgraded the OS to CentOS 7.2 and Squid to 3.5.12 (RPM from > www1.ngtech.co.il the local squidclient gets no answer if pointed to > localhost: > > # squidclient -v -p 3128 mgr:info > Request: > GET cache_object://localhost/info HTTP/1.0 > Host: localhost > User-Agent: squidclient/3.5.12 > Accept: */* > Connection: close > > > . > ERROR: Cannot connect to [::1]:3128 > That one is of course because there is no Squid listenign for traffic on [::1]:3128. > > Same with IPv4: > > # squidclient -v -h 127.0.0.1 -p 3128 mgr:info > > Request: > GET cache_object://127.0.0.1/info HTTP/1.0 > Host: 127.0.0.1 > User-Agent: squidclient/3.5.12 > Accept: */* > Connection: close > > > . > So whats preventing the IPv4 TCP connect() getting through? > > Even there it is strange that it does not listen anymore on IPv6 even if > there was no change in the config file. The relevant part looks like this: > > http_port 0.0.0.0:3128 > http_port [::]:3128 > http_port [::1]:3128 > So what is Squid logging during startup/reconfigure about that IPv6 port ? Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
