--------------------- PatchSet 4852 Date: 2007/06/25 09:54:21 Author: amosjeffries Branch: squid3-ipv6 Tag: (none) Log: Update NOTES-IPv6 on latest changes Members: NOTES-IPv6:1.1.2.42->1.1.2.43 Index: squid3/NOTES-IPv6 =================================================================== RCS file: /cvsroot/squid-sf//squid3/Attic/NOTES-IPv6,v retrieving revision 1.1.2.42 retrieving revision 1.1.2.43 diff -u -r1.1.2.42 -r1.1.2.43 --- squid3/NOTES-IPv6 24 Jun 2007 11:36:55 -0000 1.1.2.42 +++ squid3/NOTES-IPv6 25 Jun 2007 09:54:21 -0000 1.1.2.43 @@ -1,21 +1,28 @@ -$Id: NOTES-IPv6,v 1.1.2.42 2007/06/24 11:36:55 amosjeffries Exp $ +$Id: NOTES-IPv6,v 1.1.2.43 2007/06/25 09:54:21 amosjeffries Exp $ + +NP: Any problems with this version of squid please contact + squid3@treenet.co.nz for assistance. + 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 -KNOWN BUGS: +CURRENTLY KNOWN BUGS: -PROBLEM: Sockets created with IPv4 'family' cannot be use for IPv6 anywhere +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. The system that allocates pre-opened sockets to connections needs to be modified such that it checks the stored family of the socket matches the client addr family before allocating it. NP: have modified fde to store the sock_family a socket was allocated with. - Also GetAddrInfo to specifiy needed protocol formatting of an addrinfo - this will still fail retrieving AF_INET of an IPv6-pure destination. - Or on split-stacks needing a crossover port type (IPv4->IPv6, and reverse) + Also GetAddrInfo to specifiy needed protocol formatting of an addrinfo. + This will still fail retrieving AF_INET of an IPv6-pure destination. + ie. If squid listens on 2 ports, one IPv6, one IPv4 (as REQUIRED for spit-stack). + The IPv4-listener *cannot* accept requests to IPv6 destinations. +SOLUTION: Requires inbound and outbound sockets to be disentangled at the comms layer. + That is one of the other planned improvements in 3.1 so won't be fixed here. PROBLEM: Regular segfaults (~3 minutes after startup) @@ -34,11 +41,14 @@ Host newsrss.bbc.net.uk not found: 2(SERVFAIL) -PROBLEM: last of multiple NS from resolv.conf getting caught as 'unknown'?? +PROBLEM: in IPv6 mode IPv4 nameservers from resolv.conf getting caught as 'unknown' DNS lookups occasionally log: idnsRead: FD 8: received 65 bytes from 192.168.0.10:53 WARNING: Reply from unknown nameserver 192.168.0.10:53 - even though 192.168.0.10 has been loaded directly from resolv.conf (3rd of 3 NS) +CAUSE: An error in the comparison logic joining with a problem converting IPA + Would find false non-match IFF one was a socket received value and other set from a string. + Comparison problem Fixed 25 June. If it occurs again try the workaround and report please. +WORKAROUND: change resolv.conf to 'nameserver ::ffff:192.168.0.10' etc... Another intermittent failure: