Re: [squid-users] Problem with IPv6 config when destination is dual-stacked (but everything works when destination is IPv4 or IPv6 only)

fre 2009-10-30 klockan 14:01 +1300 skrev Amos Jeffries:

> I'm looking at a few approaches;
> having Squid kick off the DNS test earlier on in the processing. So
> that the data may be available later as needed, but not hold up the
> processing.

I think the right there is to move tcp_outgoing_* later in the
processing chain, after selecting the current address to connect to. But
this requires some layering changes as it's comm that does lots of this
ipv4/ipv6 magic but comm do not have access to full request details..

I don't really see how it can be done properly before asking comm to
establish the connection.

Which means comm needs to make a async callback asking forward to pick
suitable connection parameters (address + tos) when trying to connect to
a host address (after DNS resolution).

Regards
Henrik
Received on Fri Oct 30 2009 - 01:22:41 MDT