I use it in my test environment. IPv6 doesn't eliminate the need for DHCP, it just gives you more options for your network configuration mechanism.
Your options: a) IPv6 network autoconf + manual host configuration b) IPv6 network autoconf + stateless DHCPv6 for host configuration c) Full stateful DHCPv6, just like with IPv4 IPv6 network autoconfiguration provides: a) 64-bit prefix (roughly comparable to an IPv4 network & subnet mask) b) default gateway (the device performing the autoconf announcements is assumed to be the defalut gw) c) MTU d) The host part of the IPv6 address which is derived from the network adapter's mac address Notice how there are some really, really important details missing... like the DNS server IP. Hence DHCPv6. Also note that you don't HAVE to use a /64 prefix, you can go smaller (larger?) (say, a /80 or /96 or /112 or ...). My test environment uses /96 prefixes with stateful DHCPv6. There is the caveat that if you go with a prefix other than a /64 you are ABSOLUTELY REQUIRED to run a stateful DHCPv6 server. If you need a stateful DHCPv6 server for Windows, I recommend dibbler (http://klub.com.pl/dhcpv6/). It is far more flexible than Microsoft's, at least as of Server 2008. It also provides a DHCPv6 client for operating systems that support IPv6 but do not have a native DHCPv6 client (specifically Windows XP). Matthew W. Ross wrote: > Has anybody done any work on IPv6 for their internal networking? -- Phil Brutsche [email protected] ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
