On 08/31/2013 06:47 AM, Amos Jeffries wrote: > On 31/08/2013 6:53 a.m., Michael Graham wrote: >> On Wed, 2013-08-28 at 16:50 +1200, Amos Jeffries wrote: >>> What problem is it causing you exactly? Squid getting a SERVFAIL means >>> it goes on and uses the IPv4 addresses instead. >> It takes around 2-4 seconds to time out which can make access to the >> site very sluggish. >> >>> NP: It is worth noting that this SERVFAIL happens on *less* IPv6-enabled >>> sites overall than on IPv4-enabled ones. About 0.01% of IPv6 sites last >>> time it was measured by APNIC researchers, and things have been steadily >>> improving. Disabling access to IPv6 networks *entirely* for all your >>> customers is a bit of overkill for that type of error rate. >> I know, I'm trying to keep it enabled but people are complaining about >> access to this site and what else am I supposed to do? >> > > There has been a proposal with patch submitted in the last few days that > can be used to avoid this problem on an dst-IP specific basis: > http://bugs.squid-cache.org/show_bug.cgi?id=3901 > > Amos I wanted to ask something: let say we have another general proxy situation not HTTP one. if the client is trying to access a ipv4 intercepted address the general and logical rule will be to contact the IPV4 address first right?? and if the client tries to contact an IPV6 address the default will be to contact the IPV6 service provider\server? So can we set a basic rule of logic for squid intercepted connections to try IPV4 first in a case of intercepted connection on a IPV4 address and IPV6 on a IPV6 intercepted connection?? I am unsure about the current situation So correct me if i'm wrong on the current logic. Thanks, Eliezer
