I've made one change in squid.conf that seems to cure most of the problem, with 
STABLE14-20090411:

cache_peer 127.0.0.1 parent 8123 0 no-query no-digest no-netdb-exchange default

Interestingly, I was searching about "tunnelReadServer: FD 70: read failure: 
(0) Unknown error: 0" when I found the above options on a Russian forum. 

However, it appears URLs with a question mar (e.g. 
http://www.ipv6.sixxs.net/forum/?msg=general or 
http://ipv6.google.com/advanced_search?hl=en) still causes the same DNS lookup 
failure: squid either spits out "ipcacheParse: No Address records in response 
to 'www.ipv6.sixxs.net'" in cache.log, or the brower gets "Unable to determine 
IP address from host name "www.ipv6.sixxs.net"", but rarely both. Is this 
because of "hierarchy_stoplist cgi-bin ?"? If so, how do I work around it, 
given my setup?

-------- Original-Nachricht --------
Since v3.0 doesn't have IPv6 support, I set up the Polipo proxy 
(http://www.pps.jussieu.fr/~jch/software/polipo/) as a 6to4 relay in front of 
squid, by adding "cache_peer 127.0.0.1 parent 8123 3130" to squid.conf. I was 
able to browse multiple IPv6 sites such as ipv6.googe.com with 
3.0.STABLE14-20090416 as the proxy in Firefox, for quite a while, before 
squid's cache.log spit out:

2009/04/19 20:10:20| Ready to serve requests.
2009/04/19 20:12:09| WARNING: Probable misconfigured neighbor at 127.0.0.1
2009/04/19 20:12:09| WARNING: 143 of the last 150 ICP replies are DENIED
2009/04/19 20:12:09| WARNING: No replies will be sent for the next 3600 seconds
2009/04/19 20:12:31| Detected DEAD Parent: 127.0.0.1
2009/04/19 20:12:52| ipcacheParse: No Address records in response to 
'www.ipv6.sixxs.net'

After building 3.0.STABLE14-20090419, I find the above issue surfaced much 
faster than with STABLE14-20090416. Since 20090416 is no longer downlable, I 
built STABLE14 dated 20090411. It lasted about as long as 20090416, but spit 
out slightly different logs:

2009/04/19 20:57:36| Ready to serve requests.
2009/04/19 20:59:01| ipcacheParse: No Address records in response to 
'ipv6.google.com'
2009/04/19 21:00:01| ipcacheParse: No Address records in response to 
'ipv6.google.com'
2009/04/19 21:00:30| ipcacheParse: No Address records in response to 
'www.ipv6.sixxs.net'
2009/04/19 21:00:39| 95%% of replies from '127.0.0.1' are UDP_DENIED


Could this issue be mitigated from the squid end, so it keeps talking to Polipo 
(which appears to remain functional)?


-- 
Neu: GMX FreeDSL Komplettanschluss mit DSL 6.000 Flatrate + Telefonanschluss 
für nur 17,95 Euro/mtl.!* 
http://dslspecial.gmx.de/freedsl-surfflat/?ac=OM.AD.PD003K11308T4569a

Reply via email to