-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 20/12/2014 2:08 a.m., Dieter Bloms wrote: > > When I do a http://ssl.ratsinfo-online.net/ the fallback from ipv6 > to ipv4 works fine, but when I do a > https://ssl.ratsinfo-online.net/ squid tries ipv6 only and doesn't > do a fallback to ipv4. > > I would be nice, if you can try it on your dial stack setup. > > Thank you. > It takes me 10-20 sec to receive any response on the very first DNS lookup for that domain. After which all responses are quite fast for a few minutes. Then repeat with the slow lookup. Like you say it responds with 1 IPv4 and 1 IPv6. Which is not too many, and none actually failing to resolve. So DNS is reasonable even with the occasional delay. I am seeing approx 40-90% packet loss on several of the NTT.net transit hops between me and the site in IPv4. Not sure if that is related in any way related to your access path. My current colo provider blocks network measurements from end-servers (but only on v6) so I cant adequately test the v6 connectivity anymore. But your log entry indicates that probably a TCP SYN handshake did not finish over either IP version. Amos -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iQEcBAEBAgAGBQJUlCofAAoJELJo5wb/XPRjtC8H/jza0kveI1sedrGVqAUleGxL sD0V7gOy7sb6INFcIKKhl9VhTZf43m6zB4qcP/bJ9AtvjAJKc9D4FLNAaicvzTJr e2IS+glEfg8bXC67DEbH1YpMo6R3iK73LX5T50+E+SqrYbsRv8xXqkEnU6J7d4dL dFsYFbYFs7zqcOCSkqHFHuWmAKsi86zmmvuLgBxsmOGuHUPMR70J8MtFxSZTL3DJ zCyDESIuw3L3P+fJw9A0SiKiXLCagj6Gv/XKWpOiBvwUhUSow0D+avsH37J1rAOC ddZuzOOfNHbPCuQT41X7xN3AWfY42fvJmz3Ihr0sgzkBQph9IBSIqvx21cuxq8s= =J0by -----END PGP SIGNATURE----- _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
