News for hackers. Stuff that matters.
Re:Mac OS X 10.7, still no DHCPv6 by wmf on Sunday February 27, 2011 @02:47PM (#2268714)
The issue here is that there are two different ways to assign addresses in IPv6: SLAAC and DHCPv6. Apple only wants to support SLAAC; they think it's a waste of their time to have two different protocols to do the same thing. Unfortunately, a lot of ISPs want to only support DHCPv6, because it (easily) supports an audit trail and SLAAC doesn't.

I predict that things will turn out fine because people will converge on speaking SLAAC between OS X and the router and DHCPv6-PD between the router and the ISP. But you have to have a router.

Re:Mac OS X 10.7, still no DHCPv6 by sharkey on Sunday February 27, 2011 @06:15PM (#2269296)
Depending on DHCP to audit trail is flawed, because it is easy to spoof addresses.

Unless, of course, you're restricting traffic to prevent spoofing: in which case you could be doing the same for addresses assigned by SLAAC just as easily.

SLAAC also has a lot to offer for faster configuration of mobile devices roaming between networks.

Re:Mac OS X 10.7, still no DHCPv6 by pieter on Sunday February 27, 2011 @02:52PM (#2268733)
Apparently OS X now supports supplying DNS servers through SLAAC. Previously this wasn't supported, so you'd still need a DHCP(v4) server to fully support a client.
Re:Mac OS X 10.7, still no DHCPv6 by signa11 on Sunday February 27, 2011 @07:32PM (#2269461)
> Apparently OS X now supports supplying DNS servers through SLAAC

i thought this was done via router-advertisements only. slaac is used to configure v6 host addresses, and once that is done, other network parameters e.g. rdnss etc. can be obtained either via RA or DHCPv6 (the 'O' flag in RA messages)

Re:Mac OS X 10.7, still no DHCPv6 by wmf on Sunday February 27, 2011 @02:59PM (#2268753)
This isn't really a problem, since you'll need to run dual-stack for years to come anyway.