[186964] in North American Network Operators' Group
Re: IPv6 Implementation and CPE Behavior
daemon@ATHENA.MIT.EDU (Owen DeLong)
Mon Jan 11 13:39:01 2016
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <4ADBA315-1048-40DF-8AD3-466B909ED515@consultant.com>
Date: Mon, 11 Jan 2016 10:37:51 -0800
To: James R Cutler <james.cutler@consultant.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
> On Jan 11, 2016, at 10:23 , James R Cutler =
<james.cutler@consultant.com> wrote:
>=20
>> On Jan 11, 2016, at 12:01 PM, Graham Johnston =
<johnstong@westmancom.com> wrote:
>>=20
>> Are most CPE devices generally not IPv6 capable in the first place? =
For those that are capable are they usually still configured with IPv6 =
disabled, requiring the customer to enable it? For those CPE that are =
capable and enabled, is there a common configuration such as full blown =
DHCPv6 with PD?
>=20
> I can=E2=80=99t speak regarding =E2=80=9Cmost CPE devices=E2=80=9D but =
for CPE =3D Apple Airport Extreme
>=20
> =E2=80=A2 At least since the AirPort Extreme 802.11n =
(AirPort5,117) was released in 2011, the hardware has supported native =
IPv6 routing and acceptance of PD from the WAN.
>=20
> =E2=80=A2 The default configuration for firmware 7.7.3 is =
automatic WAN IPv6 configuration, native IPv6 routing, and, acceptance =
of PD from the WAN. End systems on the single LAN receive a /64.
To be more clear=E2=80=A6 The LAN receives a /64 from which end systems =
are able to construct one or more end system addresses using SLAAC.
>=20
> =E2=80=A2 No DHCPv6 is provided to the LAN through firmware up =
to the current version 7.7.3.=20
>=20
The good news is that RDNSS is allegedly supported in recent firmware =
releases.
Owen
