Thank you. I’ll look into that.
But is there anything from the logs I’m missing, for an indication as to why it
went with the ipv4 conn over ipv6 in the second case. As I understood, it
should prefer ipv6?
> On 16 Jul 2024, at 20.46, Alex Rousskov
> wrote:
>
> On 2024-07-16 09:31, Rasmus Ho
On 2024-07-16 09:31, Rasmus Horndrup wrote:
how can I basically force squid to use IPv6?
One can modify Squid source code to enforce that rule OR
* ban requests targeting raw IPv4 addresses _and_
* ensure your /etc/hosts is not in the way _and_
* use a DNS resolver that never sends IPv4 addres
On 17/07/24 01:31, Rasmus Horndrup wrote:
Hi,
On a dual stack network interface I’m interested in using squid as a ipv6 only
forward proxy.
My general understanding was that squid will prefer to use ipv6 whenever
available, but I’m having issues with squid seemingly preferring ipv4 in some
cas
Hello Rasmus,
squid has implemented the happy eyeballs algorithm, so squid uses the
best protocol to reach the server.
More infos about happy eyeball can be found here:
https://datatracker.ietf.org/doc/html/rfc8305
On Tue, Jul 16, Rasmus Horndrup wrote:
> Hi,
> On a dual stack network interfac
Hi,
On a dual stack network interface I’m interested in using squid as a ipv6 only
forward proxy.
My general understanding was that squid will prefer to use ipv6 whenever
available, but I’m having issues with squid seemingly preferring ipv4 in some
cases.
I have two examples, where it proceeds
Thanks, Alex.
Nothing jumps out in the logs when set to ALL, 9.. redacted snippet below:
2024/07/16 09:13:18.072 kid1| 11,5| http.cc(1181) readReply: conn12
local=squid.cache.ip:57824 remote=origin.server.ip:443 FIRSTUP_PARENT FD 14
flags=1
2024/07/16 09:13:18.072 kid1| 11,7| http.cc(1674) canB
