* Mikael Abrahamsson
On Sat, 26 Feb 2011, Joel Jaeggli wrote:
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.
I'm not that interested in v6 only, I'm after requiring DHCPv6 and disallowing SLAAC, which clients can use IPv6 then?
List afaik:
Can: Windows Vista/Win7 (default) Linux (with non-default software) *BSD (with non-default software)
Actually, with Linux, you do not need any non-default software. For quite some time now, the GNOME NetworkManager have supported most IPv6 flavours: * Static addressing, * SLAAC (including the RDNSS option), * Information-only DHCPv6, * Stateful DHCPv6, and * Any combination of the above. The problem is only that IPv6 support is not enabled in the default connection profile. In the default case, the kernel will on its own do SLAAC, but you won't get any IPv6 resolvers used, nor will it be able to connect to a IPv6-only network, due to the fact that NetworkManager will shut down the interface if it do not get any IPv4 connectivity (at least on wireless connections). See: https://bugzilla.redhat.com/show_bug.cgi?id=538499 Best regards, -- Tore Anderson Redpill Linpro AS - http://www.redpill-linpro.com/ Tel: +47 21 54 41 27