OverviewEven though Edge Cache is enabled and is working for IPv4 traffic, it will not currently work for IPv6 traffic.
CauseIPv6 caching functionality is not currently implemented in the Exinda software, and should not be expected to work.
Additional InformationA feature request has been submitted and is under consideration for future implementation of IPv6 Edge Cache.
Internal NotesThis KB was originally for Edge Cache not working on version 6.4, and was expected to work in 7.0.3U1+. However, it does not currently work, and I have submitted a feature request to have Edge Cache work for IPv6.
Overview - When dealing with edge cache, it should be possible to cache both IPv4 and IPv6 traffic. However, it's noted in v6.4.7 and earlier, IPv6 traffic that should be hitting the edge cache and being cached is not being touched by the edge cache engine.
Cause - Edge Cache uses the Linux application called Squid, which allows for core functionality. In version v6.4.7 of the Exinda appliance, the versino of Squid on the back end is v2.7.STABLE9. This is a relatively old version of Squid, and it does not support caching IPv6 traffic. That functionality was added in v3.1 of Squid, and implemented in v7.0 of the Exinda firmware.
Resolution - The only resolution at this time in order to be able to cache IPv6 traffic is to upgrade the Exinda firmware to v7.0.
Additional Information - For more information on Squid's IPv6 functionality, see here.
For more information on upgrading to v7.0.3u1 of the Exinda firmware, see here.
From Jamie Lenehan on the matter:
To support IPv6 for acceleration (that includes edge cache, tcp acceleration and redirection) we needed:
1) Linux kernel support for transparently proxying IPv6. We did not
have this when tcp acceleration and edge cache were originally
added. We do have this - now (since firmware v6.4.0)
2) For edge cache - squid support for IPv6. We have this now (since
firmware version v7.0.2)
3) For tcp acceleration - we need to make discovery work for IPv6.
Not done yet but I think when I looked into it appears that the
way things are there is enough room in the options message that
we use to pass the IP address (If not we'll need to invent
4) The Exinda acceleration kernel modules need to be updated to
handle IPv6. This wasn't done originally because of items 1-3
So we do NOT support IPv6 for acceleration (including edge-cache and tcp acceleration) at this point in time but all the parts we need to support it are now present. So this would be a feature request.