Lusca IPv6: (almost) everything has been migrated
Adrian Chadd
I've just finished the next major pass of changes to IPv6ify the codebase.
I'd appreciate some basic testing now. It's nowhere near ready for
production, so please only test on your local machines.
Yes, the usefulness right now is limited with CONNECT being broken to
IPv6 hosts. I'll next look at SSL server + CONNECT support.
What I've now done:
* client HTTP requests (tested)
* server HTTP requests (tested)
* peers (untested)
* ICP (untested)
* neighbor handling (untested)
What hasn't been converted:
* HTCP (easy, but I'm slack, and I can do this later)
* SSL/CONNECT support to upstreams
* SSL server support
* Multicast ICP (because I don't yet have a multicast setup to test with)
* send-announce (noone uses that)
* FTP client support (ie, it only speaks to FTP upstreams over IPv4,
and will quite happily fail to connect to IPv6 destinations)
What can't be converted:
* WCCPv2 (IPv4 only)
Adrian
Adrian Chadd
http://code.google.com/p/lusca-cache/w/edit/TodoListForIpv6
Please let me know immediately if you find something that should be on
that list, or if the list says something work but it doesn't.
(Hint hint: please test out the code; I won't start SMP, fast COSS
rebuilds, SSD support, byte-caching, video-caching, etc until IPv6 is
done and stable. Hint hint.)
Adrian
Adrian Chadd
> .. and the todo list in the Wiki is now up to date:
>
> http://code.google.com/p/lusca-cache/w/edit/TodoListForIpv6
>
> Please let me know immediately if you find something that should be on
> that list, or if the list says something work but it doesn't.
I've fixed a bunch of niggling issues, including a silly bug which
compared ipv4/ipv6 addresses when building that splay tree ACL (for
source/destination IP ACLs). I'm now using it locally to connect to
IPv4/IPv6 servers from IPv4/IPv6 clients. It's all working just fine.
Hint hint, test it. :)
Adrian