On 26/01/19 5:00 am, Amos Jeffries wrote:
> On 25/01/19 11:29 pm, Troiano Alessio wrote:
>> Hello,
>>
>> I need to definitively solve the ipv6 (un)reachbility issue.
>>
>> I state I read this topic:
>> http://squid-web-proxy-cache.1019090.n4.nabble.com/dns-v4-first-on-ignored-td4658427.html
>> but
On 25/01/19 11:29 pm, Troiano Alessio wrote:
> Hello,
>
> I need to definitively solve the ipv6 (un)reachbility issue.
>
> I state I read this topic:
> http://squid-web-proxy-cache.1019090.n4.nabble.com/dns-v4-first-on-ignored-td4658427.html
> but not found a solution. Amos wrote “Squid tests for
On 1/25/19 3:29 AM, Troiano Alessio wrote:
> I need to definitively solve the ipv6 (un)reachbility issue.
You can
* build Squid with --disable-ipv6
* try an experimental (and unofficial) Squid branch that implements the
TCP part of the Happy Eyeballs algorithm:
https://github.com/measurement-fa
Em 25/01/2019 08:29, Troiano Alessio escreveu:
What can I do?
My ISP is IPv4 only.
I'm not completely sure but it looks more like a DNS issue than the IP
binding on Squid server. But check if your 'ifcfg-ethX' has IPV6INIT=no.
Also, is Squid listening on all local IPs? If yes, then try bindin
Hello,
I need to definitively solve the ipv6 (un)reachbility issue.
I state I read this topic:
http://squid-web-proxy-cache.1019090.n4.nabble.com/dns-v4-first-on-ignored-td4658427.html
but not found a solution. Amos wrote “Squid tests for IPv6 ability
automatically by opening a socket on a priva
