ping On 2014-01-08 Wed 11:13 AM |, Craig R. Skinner wrote: > On 2014-01-01 Wed 20:55 PM |, Amos Jeffries wrote: > > > > > > I included a link to a bug verified by the FreeBSD ports team. > > > > > >> > > >> The line you have mentioned: > > >> http://bazaar.launchpad.net/~squid/squid/3-trunk/view/head:/src/cf.data.pre#L847 > > >> Assumes that the machine is ipv6 enabled by default. > > The FreeBSD patch removes that assumption. > > > > > > > It's very easy to test. No kernel or squid recompile needed. > > > > > > By setting the DNS resolver to use IPv4 only, squid can't start/parse > > > > > > (i.e. it is a DNS resolution issue): > > >>> > > >>> $ fgrep family /etc/resolv.conf > > >>> family inet4 > > >>> > > > > Exactly. > > > > > > > > Re-enabling IPv6 DNS resolution lets squid run again: > > > > > >>> > > >>> $ fgrep family /etc/resolv.conf > > >>> #family inet4 > > >>> > > > > > > > Possibly the resolv.conf configuration directive could be done earlier > > in the configuration sequence, the ACL made non-fatal when an invalid > > value is passed for interpretation as an IP address, and Squid updated > > to support that family directive from resolv.conf. > > > > Amos > > That seems sensible. > -- Craig Skinner | http://twitter.com/Craig_Skinner | http://linkd.in/yGqkv7
