>>>>> "CL" == Chuck Lever <chuck.lever...> writes:
[...]
CL> In other words, system support for IPv6 outside of NFS is kind of
CL> like wireless was 5 years ago -- innumerable small admin tools that
CL> users had to integrate themselves, usually without much success.
BTW, I tend to disagree with that. I've ``discovered'' IPv6
only this summer, and for me, the whole thing was smooth...
... Almost. There were only a few issues:
* /etc/network/interfaces (like in Debian GNU/Linux) handling is
a bit IPv4-centric (even more so in Etch, oldstable); say, one
may have to resort to the hacks like:
iface eth1 inet6 static
address X:Y:Z:W::1234:5678
netmask 64
gateway X:Y:Z:W::1
post-up ip -6 addr add G:H:I:J::DEAD:1/64 dev "$IFACE" && ip -6 addr add K:L:M:N::1337:CAFE/64 dev "$IFACE"
(with Etch, one'd have to add IPv6 management commands to the
existing IPv4 interfaces' stanzas.)
* the stable version of Squid lacks IPv6 support completely;
Apache has it, but it lacks caching, which is a must for me;
* there're no VoIP switches with IPv6 support in Debian; in
particular, Asterisk speaks no IPv6, while FreeSWITCH is not
in Debian; (there was an ITP); there's Linphone for an
IPv6-compatible user agent;
* NFS.
Otherwise, I use IPv6 on a daily basis, both at home and at
work, and there seems to be no significant flaws, other than
those few above.
Occasionally, some hardware seems to behave strangely (e. g., I
was unable to use IPv6 in one of classrooms here), and sometimes
there're noticeable response times from hosts using old NICs,
but hey, there're still a couple of 10 Mbit/s hubs in the darker
corners of the network, and nobody seems to worry about it much.
--
FSF associate member #7257
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
