[186962] in North American Network Operators' Group
Re: IPv6 Implementation and CPE Behavior
daemon@ATHENA.MIT.EDU (James R Cutler)
Mon Jan 11 13:23:17 2016
X-Original-To: nanog@nanog.org
From: James R Cutler <james.cutler@consultant.com>
In-Reply-To: <49EE1A35457387418410F97564A3752B013694D930@MSG6.westman.int>
Date: Mon, 11 Jan 2016 13:23:10 -0500
To: Graham Johnston <johnstong@westmancom.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
> 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?
I can=E2=80=99t speak regarding =E2=80=9Cmost CPE devices=E2=80=9D but =
for CPE =3D Apple Airport Extreme
=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.
=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.
=E2=80=A2 No DHCPv6 is provided to the LAN through firmware up =
to the current version 7.7.3.=20
For all recent Windows, OS X, and. IOS versions, IPv6 =E2=80=9Cjust =
works=E2=80=9D with the Airport default IPv6 configuration. Most users =
can not tell the difference.=20
For those connected to ISPs that still can=E2=80=99t spell IPv6, I do =
manually set Internet Options to Configure IPv6: Link-local only. This =
should not make any difference, but it makes me and some eyeballs =
happier.
James R. Cutler
James.cutler@consultant.com
PGP keys at http://pgp.mit.edu
