If you want to configure static IPv6 addresses in CentOS, it's pretty easy. You set UPV6_NETWORKING=yes in /etc/sysconfig/network and assign an address in your /etc/sysconfig/network-scripts/ifcfg-XXX file. See this page for some more details http://www.cyberciti.biz/faq/rhel-redhat-fedora-centos-ipv6-network-configuration/. All of the available IPV6 options for the sysconfig scripts are listed in sysconfig.txt which you'll find in /usr/share/doc/initscripts-<version> on ypur CentOS boxen. This all assumes you have some router running IPv6 to configure as your default gateway.
IPv6 supports stateless autoconfiguration for non-static addresses. Basically, your routers need to provide routing advertisements with a IPv6 network prefix (this can be done on a Linux router either with the radvd package or the quagga routing suite). Basically your host comes up, sends out a notification looking routers and the IPv6 router on your submit responds with a advertisement response containing what prefix the host should use. The rest of the IPv6 address is usually derived from the MAC address. This only gets you an address though, and there is a DHCPv6 standard now for getting you things like DNS. From my understanding, you basically use stateless autoconf to get you on the network and use that address to get DHCPv6 to get the rest of your network info. The Linuxen and BSDs have decently robust support for IPv6 these days from the OS perspective. Most of the important server apps have IPv6 support and clients are coming along. Mac OS X has had decent client support I believe since about 10.4. As for Windows, XP has limited IPv6 support. If you turn on IPv6, there is no GUI configuration support (all config done through netsh command line). IIRC, you cannot configure an IPv6 address (all you get is the IPv6 address space equivalent of what your IPv4 address is). Also there is no DHCPv6 support (a grad student wrote a DHCPv6 implementation called Dibbler http://klub.com.pl/dhcpv6/ ). Also XP (last I checked anyway) doesn't make DNS queries over v6 (it'll make v4 queries and if, for example, it gets a AAAA record and the app supports v6, it will use v6 to talk for that app). Windows Server 2003 has better, but not awesome IPv6 support. Vista is the first MS OS that they claim has full IPv6 support. Most major routers (Cisco and Juniper at least) also do IPv6. As for home, the home router vendors (Linksys, Netgear, D-Link, etc) are still fairly new to implementing IPv6. I hope that's helpful! :) -Shawn On Tue, Apr 20, 2010 at 1:10 PM, John Abreau <j...@blu.org> wrote: > I'd like to begin deploying IPv6 on the BLU.ORG servers. They will need > to transparently handle both IPv4 and IPv6, at least until some distant > future time when IPv4 goes away. I suspect both will probably have to > work in parallel for a while. > > Has anyone else deployed IPv6 yet? Is there a decent HOWTO that > shows how to deploy it for a network of CentOS servers? > > Eventually I'll want to deploy it at home and at work, where MacOS and > Windows clients will presumably complicate the picture. I'm assuming > it will be easier to get my first deployment working if I do it in a pure > Linux environment. Is this a reasonable assumption? > > The three BLU.ORG servers are running CentOS; two are CentOS 4, and > the other is CentOS 5. > > > > -- > John Abreau / Executive Director, Boston Linux & Unix > AIM abreauj / JABBER j...@jabber.blu.org / YAHOO abreauj / SKYPE > zusa_it_mgr > Email j...@blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 > PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ >
_______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
