After reconfiguring the lounge room to move the TV to another corner, I had to do a little bit of rewiring. As luck would have it, when I reset theResidential Gateway (RG) it didn’t come back. As part of replacing the RG, I though I’d dig a bit deeper into the getting IPV6.
- Call out to ATT,
- one missed appointment,
- a visit from an ATT tech,
- a new RG,
- another visit from a tech,
- a fixed outside line,
- another call to ATT,
- an email to customer service,
- seven emails with customer service,
- a new visit from a tech
- a new RG
I am finally on the other internet.
So now I’m on the other Internet, things seem to be working. ipv6.google.com seems to work, and http://test-ipv6.com/ and http://ipv6-test.com/ seem to report that things are good. Apparently I only need to fix ICMP and my hostname and I’ll be 20/20.
So, if you on AT&T U-Verse, then your best chance of getting on IPV6 is probably mailing ATTCustomerCare@att.com with a message like the following.
I was wondering what is needed to enable IPv6 for vDSL customers?
With luck you’ll get someone who takes the request seriously (thanks Brandon), and does his background research while responding to you. Things came together for me when I referenced online posts referencing the Motorola NVG589. When the ATT tech dropped the unit off, it dropped in and started working without an issue.
After turning off the RG firewall, and setting passthrough to my wireless router, it’s all good.
Pity, there isn’t too much that I’ve found that is different in IPv6 land, however at least I’m there…