--------------------- PatchSet 4899 Date: 2007/06/29 16:47:59 Author: amosjeffries Branch: squid3-ipv6 Tag: (none) Log: Update NOTES-IPv6 to mention localhost-apps issue (hopefully closed already) Members: NOTES-IPv6:1.1.2.45->1.1.2.46 Index: squid3/NOTES-IPv6 =================================================================== RCS file: /cvsroot/squid-sf//squid3/Attic/NOTES-IPv6,v retrieving revision 1.1.2.45 retrieving revision 1.1.2.46 diff -u -r1.1.2.45 -r1.1.2.46 --- squid3/NOTES-IPv6 25 Jun 2007 13:09:37 -0000 1.1.2.45 +++ squid3/NOTES-IPv6 29 Jun 2007 16:47:59 -0000 1.1.2.46 @@ -1,4 +1,4 @@ -$Id: NOTES-IPv6,v 1.1.2.45 2007/06/25 13:09:37 amosjeffries Exp $ +$Id: NOTES-IPv6,v 1.1.2.46 2007/06/29 16:47:59 amosjeffries Exp $ NP: Any problems with this version of squid please contact squid3@treenet.co.nz for assistance. @@ -6,9 +6,22 @@ NP: All IPv6 builds from before 9 June 2007 contain a cache corruption bug and require a full cachedir deletion and rebuild. - Failure to do this will result in random segfaults and memory corruption + Failure to do this will result in random segfaults and memory corruption. + + +CURRENTLY KNOWN ISSUES: + +PROBLEM: Squid connecting to IPv4 applications listening on 127.0.0.1, will attempt + to use IPv6 sockets to connect to them on IP '::1'. +SOLUTION: Code from 30 June will attempt an IPv6 link and if that fails try IPv4. + To my knowledge this only occurs with localhost due to its special nature + in both protocols. +BYPASS: If the current fix still fails there is a work-around + Most of the apps squid interacts with over HTTP/FTP where this occurs most + should be capable of a simple IPv6-enabling configuration to get around this. + Configure the other app to listen on IPv6-localhost if possible or to listen + on another explicit IPv4 address (127.0.0.2 for example) and point squid at that. -CURRENTLY KNOWN BUGS: PROBLEM: Sockets created with IPv4 'family' cannot be use for IPv6 *anywhere*. Likewise ones opened for IPv6 on split-stack systems cannot be used for IPv4.