Creating this in a test lab is mandatory for a successful migration. Tunnels behind a CPE and 4to6 NAT seem like bandaid fixes as they do not give the benefit of true end to end IPv6 connectivity in the sense of every device has a one to one global address mapping.
Seems that my initial thoughts of dual stack and v4 overloading using private addresses to ensure compatibility is the way to go. Any input on good, possibly application aware, CGN solutions? Maybe even some policy-based DHCP/NAT product? Thanks, Joshua Moore Network Engineer ATC Broadband 912.632.3161 > On Jul 5, 2015, at 5:35 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. > > -w
