I am running an IPv6-only network, but to be honest it is not yet ready to to handle all my use cases. Often operating system updates fail due to ipv4-only update servers. The equipment is all software, the switch is openvswitch on a 12-NIC linux box from soekris, the router is a linux box and most of the systems are linux systems. Thus I am able to implement everything what I am missing in software. I do not have to wait for vendors to implement a specific feature. The downside of this is, that it quite slow. It works for small work groups, but it would never scale up to enterprise environment. Dual Stack networks and NAT64 networks cost more money, so I see a real business case for IPv6-only as soon as there are no bigger business cases bound to ipv4 (like hundreds(!) of enterprise applications that were in the stoneage of IT) Best regards Dan On Wed, Jul 10, 2013 at 4:53 PM, Shane Kerr <shane@time-travellers.org> wrote:
All,
I saw this today:
http://wiki.test-ipv6.com/wiki/Main_Page
And I was thinking about the seeming increase in interest recently in researching the realities of an IPv6-only world.
According to Cisco's IPv6 stats site:
We're a long way from having most content available over IPv6... but not *that* long, if we can take the 40% numbers seriously.
So I guess this is mostly a "setting the groundwork" for now, but maybe not. Does anyone actually run an IPv6-only network now, or is thinking about it? (As in, without a gateway to the IPv4 world.)
Cheers,
-- Shane
-- Dan Luedtke http://www.danrl.de