and a bunch ofįolk are considering not turning things off after that day.

Provide an ipv4 nameserver at the very minimum for a long timeĪpple is gonna look very very st00pid on world ipv6 day. You're going to have to perform stateless autconfiguration in ipv6 and On Feb 27, 2011, at 6:27 AM, Randy Bush wrote: Means they won't be getting IPv6 anytime soon. Really too bad that OS X doesn't support it because on our network it It works great for Windows and Linux systems,Īnd even Android devices (I believe the iPhone even supports DHCPv6), Respond to hosts and do a phased deployment, enabling IPv6 on aĮven though we have good native IPv6 available, we've adopted a DHCPv6 Talking IPv6, by disabling SLAAC and using DHCPv6, you can selectively With SLAAC, as soon as you enable it every host on a network starts Networks, and maybe even the opposite end: very very large (mobile)īut DHCPv6 is a powerful tool and one that shouldn't be thrown out. Once again, SLAAC and RDNSS is great for quick, small, plug-and-play Has implemented that yet, making Apple a 'special case' host onceĪgain (I don't even think Cisco supports the option in their T series Server information in an IPv6-only environment. Mac OS X 10.7 does support RDNSS (RFC 5001) so it is able to get DNS I'm not really sure what about DHCPv6 is difficult. Signals whether a prefix can be used for SLAAC or not) of an RA, so ofĬourse you can disable SLAAC (right from the prefix you advertise).Īpple has said before that they don't want to use DHCPv6 because IPv6 Every OS I've tested so far respects the A flag (which Saw some mention of being unsure that it was possible to disable

For a lot ofĮnterprise (or in our case, academic) networks you really want theĬentral control of what addresses hosts get. SLAAC is fine (even great) for small environments. By Thread Re: Mac OS X 10.7, still no DHCPv6

Toast for mac 10.7