Summary
In this chapter, we spent a lot of time on HTTP before moving on to other services. HTTP is important because it still accounts for a significant percentage of Internet traffic[16] and is an ideal candidate for offering over IPv6, especially if you use Apache as a server.
Naturally we can't cover everything. IRC, LDAP and SQL come to mind as notable exceptions from our discussions, but rather than give an exhaustive list, we hope we've given you an idea of the level of IPv6 support available out there and the problems you can encounter deploying these services. To keep up to date with the availability of IPv6-enabled software, keep an eye on the list of Applications on Peter Bieringer's pages, http://www.bieringer.de/linux/IPv6/status/ and http://www.deepspace6.net/docs/ipv6_status_page_apps.html, or on sites like the KAME site.
We've also encountered a few general principles for deploying IPv6 services in this chapter: you may need to explicitly enable IPv6 at compile time or at run time, you may need to update log file processors, you may need to update ACLs. One thing we didn't cover explicitly is testing your service—remember to check it works over IPv6, IPv4 and any other way in that it can be accessed.
Overall we've seen that a lot of software is now offering IPv6 support comparable with the IPv4 support. However, this code has yet to accumulate the man-centuries of testing associated with IPv4 and hence we have to expect the odd glitch.
[16] HTTP's main competitor for ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access