Re: [squid-users] caching failed tcp connects to destination ips

From: Dieter Bloms <squid_at_bloms.de>
Date: Thu, 25 Jul 2013 09:37:41 +0200

Hi Amos,

thank you for your quick answer.

On Thu, Jul 25, Amos Jeffries wrote:

> On 25/07/2013 6:52 p.m., Dieter Bloms wrote:
> >Hi,
> >
> >we use ipv4 and ipv6 tcp protocol for our outgoing interface.
> >The most sides are accessable via ipv6, if a AAAA Record is available,
> >so ipv6 works great in most cases.
> >
> >Some sides like http://www.hsp-steuer.de/ announce ipv6 records, but are
> >not accessable via ipv6.
>
> Send them a bug report?

I did, but the provider is resistant about this.

> >Is it possible that squid notice this fail so that future request will
> >go to ipv4 directly and the user doesn't have to wait for the long
> >tcp timeout every time ?
>
> Yes it is possible and Squid already does.
> If you check your cachemgr "ipcache" report you can see this as the
> DNS results domain/IP mapping list OK/BAD flags on each IP address
> known. BAD will not be used, OK will be tried, success is always a
> gamble.

the ipv6 adress 2001:8d8:88c:37e2:3e1b:35f0:e10:1 is not reachable on
port 80, but cachemgr says:

--snip--
www.hsp-steuer.de 33 1110 2( 0) 2001:8d8:88c:37e2:3e1b:35f0:e10:1-OK
                                                                                          82.165.11.88-OK
--snip--

so is this a bug in squid, that the ipv6 address is listed as OK ?

-- 
Best regards
  Dieter
--
I do not get viruses because I do not use MS software.
If you use Outlook then please do not put my email address in your
address-book so that WHEN you get a virus it won't use my address in the
From field.
Received on Thu Jul 25 2013 - 07:37:43 MDT

This archive was generated by hypermail 2.2.0 : Thu Jul 25 2013 - 12:00:10 MDT