I try to answer your questions, because we move in the way of writing the huge discussion book in a post:) >Why would it get stuck on IPV4 or IPV6? It is my assumption, call it intuition. And the flag IPv4 resolved the main problem, isn't it? >Also a FD :: should not be related to any of squid helpers but to another parts of squid service levels. That's true, it is more like squid asks the IPv6 on interface lo0. However, The lo0 is configured only with IPv4, so comes the FD ::1 error/warning (it is my logical conclusion based on: http://proxy.ccu.edu.tw/squidfaq/FAQ.pdf; <http://proxy.ccu.edu.tw/squidfaq/FAQ.pdf; p115 > (p.115) Maybe I am wrong. >it's ubuntu 13.10 + 3.3.8 ?.. Yes Ubuntu Server 13.10 + Squid 3.3.8 from Ubuntu repository. >Are you using stock settings? Yes I do, but with some changes for my test environment (see the very first post). >Are you using do you have ipv6 + ipv4 real or local addresses? I use only local IPv4 addresses (192.168.1.0/24) >What would you be doing to get to this site? >http://[2001:470:505a::101]/ >Try to ping it or browse to it... Ping: Request timed out. Request timed out. Browse: This page can’t be displayed I did it from my W8.1 Pro machine. >"ip addr" and also use the default squid.conf to make sure that squid >runs without any auth parameters. Squid runs for sure without any auth programs. But with FD:: problem. How to use script is not clear to me... My /etc/network/interface: # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto LAN iface LAN inet static address 192.168.1.130 netmask 255.255.255.0 gateway 192.168.1.1 dns-nameservers 192.168.1.1 8.8.8.8 post-up iptables-restore < /etc/iptables.up.rules >About script external_acl_type memberof %SRC /etc/proxystatcheck.sh like this? script should look like this?: #/bin/bash #proxystatcheck.sh by Eliezer Croitoru #you can use a ramfs/shm fs to lower the disk R\W access while read url do echo $url >> /tmp/ext_acl.log if [ -a /tmp/proxy1.err ] then echo ERR else echo OK fi done Did I understand you good? -- View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/Ubuntu-Server-13-10-Squid-3-3-8-WARNING-external-ACL-memberof-queue-overload-tp4663243p4663297.html Sent from the Squid - Users mailing list archive at Nabble.com.