Well, does getting a tunnel to the border router, and giving the public webservers, and the internal servers a static ipv6-address count? No special hardware needed. Windows and linux-servers. Of cause, old fashioned Voip and printers still run internal ipv4-adresses. Otherwise, the pc's just get ipv6-adress from rtadvd. My only oops'es was dns, having *.my.dom a 1.2.3.4 www.my.dom aaaa 1:2.... gave "no A-record for www.my.dom"

IBM Zurich Research Laboratory has been running native IPv6 for about 6 years now; it is not a huge place people-wise, hovering around 400 folks, but there are a lot of hosts and devices attached to the network (clusters tend to take an IP for every node and there are a couple of those ;). In IPv4 a /16 is almost completely filled though there is room for growth left, the IPv6 /48 (thanks SWITCH.ch) we have is quite sparse actually as most of the network is switched, effectively a (V)LAN per floor of each building or functional groups depending on where the administrators wanted the broadcast domain or other such grouping. The external website is IPv6 enabled and so are a couple of other external services. Most internal services have been IPv6 enabled too. Services generally run on a mix of AIX, Win2k8 and Linux hosts, most of the networking gear is Cisco based. One of the most annoying issues: Cisco PIX/ASA, they still don't do proper failover in IPv6 from what I understand, though we didn't hit that bug for a while now from what I have noticed at least.

I deployed IPv6 throughout 3 campus networks using Linux and Quagga (using a router-on-a-stick approach since the brownfield kit did not support ipv6 natively). See VLAN Plan for the addressing plan I used.

We're running IPv6 in our network. We were able to roll everything out during production, and no one even noticed anything was happening. Our problems were ones I suspect everyone encounters: printers and access points don't support IPv6 unless they're new. The biggest hurdle was trying to get help/support from hardware suppliers.

We got Apple Servers, Linux Servers, Mac Clients. Fortigate Firewalls, Apple Accesspoints. The only problem we have, Fortinet does not support PPPoE with IPv6 yet. Otherwise we did not even have to use sixxs.net. Currently we have DHCPv4 providing DNS and RA. Nobody realized, that IPv6 is running. You can see it in the logs, that people connect to the servers using IPv6.