Jared, Tunneling gets customers onto IPv6 with little trouble. I've deployed hundred of Apple Airports in this capacity and they have no problem with speeds of 200Mbps and more, and they rarely have downtime. The firmware is auto-updating and is kept very current by Apple. The one feature they don't support well is IPv6 DNS, since Airport has no DHCPv6 support. But an IPv4 name server works fine since the customers have an IPv4 link already.
-mel > On Jul 5, 2015, at 5:24 AM, Jared Mauch <ja...@puck.nether.net> wrote: > > >> On Jul 5, 2015, at 5:32 AM, William Waites <wwai...@tardis.ed.ac.uk> wrote: >> >> On Sun, 5 Jul 2015 06:13:52 +0000, Mel Beckman <m...@beckman.org> said: >> >>> In fact, I show just how to do this using a $99 Apple Airport >>> Express in my three-hour online course “Build your own IPv6 Lab” >> >> An anectode about this, maybe out of date, maybe not. I was helping my >> friend who likes Apple things connect to the local community >> network. He wanted to use an Airport as his home gateway rather than >> the router that we normally use. Turns out these things can *only* do >> IPv6 with tunnels and cannot do IPv6 on PPPoE. Go figure. So there is >> not exactly a clear path to native IPv6 for your lab this way. > > The airport devices/airport express class are not that good of devices > as the embedded software doesn’t handle a lot of traffic or long uptime > well. > > Most devices that are over 3 years old likely are not suitable for > IPv6 testing aside from understanding what is broken. Keep in mind > that software on a CPE device may be 6 months out of date by the time > it comes out of a container stateside. > > Expecting people to use tunnels, etc doesn’t really scale properly. > > I do wish that I could get static IPv6 prefixes along with my > static IPv4 at home, but having IPv6 at all took precedence. > > - Jared
