Changes
IPv6
,→Adoption at Virginia Tech
* Central web hosting (due to a lack of IPv6 support in the load balancers)
* Campus email (Exchange, legacy POP/SMTP, but not the new Google services)
* VT_WLAN authentication (anyone can access the IPv6 internet without entering VT credentials)
VT DNS resolvers have AAAA records:
* <code>jeru.cns.vt.edu 2001:468:c80:4101:0:100:0:42</code>
* <code>milo.cns.vt.edu 2001:468:c80:6101:0:100:0:62</code>
==Departmental Subnet Routing==
Since CNS doesn't officially support departments operating their own routers, only single addresses (/128) are routed to each ethernet port. This is problematic for those that wish to distribute global IPv6 addresses to internal networks, and has a limited number of known solutions:
* Use a [http://priv.nu/projects/ndppd/ NDP proxy] on the router to send all router solicitations/advertisements over the WAN, and relay the response. This can optionally be used with DHCPv6 to distribute custom DNS servers and IP addresses. By using IP addresses that are ''not'' generated by [[w:SLAAC|SLAAC]], there is no need to update the DNS records for the machine if the NIC is ever swapped.
* Bridge IPv6, while NATing IPv4 on the router. This would (in theory) have less overhead, but there doesn't appear to be an easy way to do this.
=References=
<references />