[138021] in North American Network Operators' Group
Re: Mac OS X 10.7, still no DHCPv6
daemon@ATHENA.MIT.EDU (Leigh Porter)
Sun Feb 27 09:53:52 2011
From: "Leigh Porter" <leigh.porter@ukbroadband.com>
In-Reply-To: <20110227140321.GM9424@angus.ind.WPI.EDU>
Date: Sun, 27 Feb 2011 14:47:37 +0000
To: "Chuck Anderson" <cra@WPI.EDU>
Cc: nanog@nanog.org, I2 IPv6 working group <wg-ipv6@internet2.edu>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Does anybody have anything neat to keep logs of what host gets what ipv6 add=
ress in an SLAAC environment?
This is often required for legislation compliance. DHCP does this well.
--
Leigh Porter
On 27 Feb 2011, at 14:04, "Chuck Anderson" <cra@WPI.EDU> wrote:
> On Sat, Feb 26, 2011 at 09:46:17PM -0800, Joel Jaeggli wrote:
>> On 2/26/11 9:27 PM, Mikael Abrahamsson wrote:
>>> On a more serious note, I can on my Ubuntu machine just "apt-get install=
>>> wide-dhcpv6-client" and I get dhcpv6, it'll properly put stuff in
>>> resolv.conf for dns-over-ipv6 transport, even though the connection
>>> manager knows nothing about it, at least dual stack works properly.
>>>=20
>>> Can one do the equivalent easy addition to OSX?
>>=20
>> You can, the actual integration issue is that network mangler (on
>> ubuntu/fedora etal) and the osX airport connection manager will give up
>> on a subnet on which they can't obtain an ipv4 address in prefernce to
>> one where they can... this can also be worked around but it makes
>> v6-only operation (Assuming that were desired, or even a good idea at
>> this point) something that the majority of the users wouldn't be able to
>> achive without the default behavior changing.
>=20
> NetworkManager on Fedora fully supports IPv6 now, including DHCPv6. =20
> You can easily configure it to require an IPv4 address or an IPv6=20
> address or both to consider the connection successfull.
>=20
