01-19-2012 12:11 PM
So it appears that AT&T is at long last planning on rolling out IPv6 support this year ( http://www.att.com/ipv6 ). For the last year I've configured my home as folows:
RG in DMZPlus mode, targeting system X in my house
System X acting as an IPv4 nat router and ipv6 router over a 6in4 tunnel to Hurricane Electric
Now that AT&T is going to be supporting IPv6, I'd love to get rid of the tunnel overhead and just start directly routing ipv6, but I've had trouble getting any answers out of tech support on the phone or via online chat. Hoping one of the moderators or someone who has already rolled out the update can answer these questions. Specifically:
1) How is AT&T serving IPv6 addresses to residential customers? Are they sending Route adverisements and expecting SLAAC configuration on clients or doing dhcpv6? I'm guessing the latter, but I'd like to hear that for certain.
2) How do multiple devices work? Does the RG just act as a bridge that all home devices DHCP or SLAAC accross? Or is AT&T assigning a single address to an RG and implementing IPv6 NAT? Or do they assign a large subnet to the RG and let it manage local address configuration for connecting clients?
3) Will it be possible to use DMZplus or bridge mode operation under the updated firmware so that we can use a private router to manage ipv6 address subnetting?
4) Depending on the outcome of these questions, it may be desireable to just stick with my Hurricane Electirc provided tunnel. If that turns out to be the case can we simply disable IPv6 networking on the RG? Will we still have a globally routable IPv4 address that we can use to establish a tunnel to another provider?
If Anyone from AT&T (or someone who already has the service could answer these questions, I would certinaly appreciate it. Thanks!
05-15-2013 12:48 PM - edited 05-15-2013 12:52 PM
Here are ATT's plans:
Every device and website on the Internet needs an address, known as an Internet Protocol (IP) address, in order to communicate. The IPv4 addressing structure has been the standard for many years. Since IPv4 only provides about 4 billion usable addresses, a new protocol called IPv6 was developed to allow continued growth of the Internet. IPv6 has so many unique IP addresses available (virtually unlimited) that the Internet can continue to grow well into the future.
You will be happy to know the slow rollout of IPv6 will bring no immediate or near-term impact to your AT&T U-verse service. You will still be able to access your email, favorite Internet websites, and content as you do today for quite some time. In fact, IPv4-based networks are expected to co-exist with IPv6-based networks for many years. AT&T has been planning for the IPv6 transition since 2006.
We will make your U-verse Wireless Gateway IPv6-capable by automatically updating its firmware*. These updates began in 2011 and are expected to continue through end-of-year 2012. If you have one of the following models, you do not need to take any action to receive this routine and automatic update:
Please do not call Customer Care requesting for the firmware update sooner or for an exact date, as we cannot provide this information.
Motorola 2210 modems, 2Wire/Pace 2701 AT&T High-Speed Internet Wireless Gateways, and Cisco e1000 or e1200 routers cannot be updated to become IPv6-capable. Instead, replacement IPv6-compatible equipment is available for purchase through the AT&T Equipment Shop.
Edit: Must be going slow as my 3800 still is not IPv6 ready.
Please NO SD stretch-o-vision or 480 SD HD Channels
Need Help? 1-800-288-2020, After he gets acct info, press # a bunch of times, get a menu from Mr. Voice recognition
Your Results May Vary, In My Humble Opinion
I Call It Like I See It, Simply a U-verse user, nothing more
08-29-2013 11:33 AM - edited 08-29-2013 2:14 PM
"Please do not call Customer Care requesting for the firmware update sooner or for an exact date, as we cannot provide this information."
Ok, well bear with me because I'm serious here. 2013 is just about two-thirds over. I use a Pace 3801 HGV and I'm still waiting for this update.
If I'm considering a competitor's offer to replace AT&T's services, does Customer Care still not want to be contacted before I make the switch? So far I have been patient, however there are limits and 1 - 2 years late really pushes that envelope.
08-29-2013 12:10 PM
Well, it is after end-of-year 2012. I'd say that you can call customer service for an update. But 95 out of 100 of them will have no idea what you're talking about.
08-29-2013 3:24 PM - edited 08-29-2013 3:26 PM
Here's an update: I called AT&T's Customer Care. You were correct in that the technician answering my call had no idea what IPV6 is. Now here's where it gets better. His claim is this: because my system is set to receive nightly updates from AT&T, my 3801HGV must not be hardware-compatible with IPV6. He also ran a compatibility test on my hardware and he said it shows my hardware is not compatible. He offerred to transfer me to someone else who might be able to supply IPV6-compatible equipment. At that point, I declined and ended the call. I have registered at the Pace support website and opened a support ticket asking them for a definitive answer as to whether or not this modem would be compatible with a firmware upgrade. Stay tuned for more details after I receive a reply from Pace...
08-30-2013 6:59 AM
Here is the reply from Pace's support technician:
Response by Robert B.: on 08-29-2013 09:35 pm
08-30-2013 8:39 AM
Somewhere in these forums is a post from a customer who discovered that IPv6 was working for him. However, I don't know what kind of gateway he has.
08-30-2013 10:25 AM
My guess is that whether Pace is capable of IPv6 or not is not the only factor. When I first got the Pace (returned it) I got it because the claim it supports static IP configuration. Of course, I should have known that the claim is for static IP blocks and not legacy customers. But I hoped any way and it was the wrong decision. So shortly after that I had a tech here (this some quite time ago) and what he told me is while hardware might be supported it does not matter as ADSL customers are not in fact going to get IPv6 - or at least they weren't at that point.
I see that this is in the Uverse forum but I thought the Pace gateway was for ADSL. Maybe there exists some for Uverse and some for ADSL but if you do happen to have ADSL then it might be that you simply do not get it (there's also been the suggestion that AT&T is rolling out more equipment and trying to get customers off the old circuits which may or may not be a problem depending on the customer - no idea how true the suggestion is though). In that case I would suggest either setting up a tunnel broker account (though if your IP Is dynamic that's more of a problem though not necessarily impossible).
As for techs I would say that - through my experience, because of the fact a legacy customer - if you are to get any where you need to escalate to at least tier 2 support. They would have more info (though again that is not a guarantee: despite IPv6 original specification [RFC 1883] was proposed in 1995 we're still on IPv4 because of the workaround of dynamic allocation and NAT; I mean in the 90s AT&T gave customers single static IPs by default). Tier 1 will try to help you and they will often insist upon it (as it is their job) but you need to persist. For me I usually told them it was something to do with the redback (the routers) configuration or similar things (sometimes it was not much work to get to them and other times it was more work). I think at one point I had a direct # to tier 2 support but even if I still did I can hardly imagine AT&T would be impressed with it being posted here. On the other hand you might be able to get help from David here on the forum? He works for AT&T and (I can only assume) he is the same one on broadbandreports.com (dslreports.com too I believe) and over there there is a private forum so you can give your information (contact info etc) and no one but the techs can see it (well and you for your post). Note on that: don't respond to your post until they respond because they will think (as it has a response) that one of the other techs may be helping you already.
Hopefully that helps you some. Sad as it may be I think my main frustration (usually only) with AT&T is that their telephone support is not that great (and loops... that drive you crazy [local loops? heh]) and if they could improve there it would be a really good thing because for I cannot even imagine the frustration that non-experienced customers go through given that I know what the problem is (some times telling them the exact thing they need to do) and yet I get frustrated with the support line. I do know that there's techs and even engineers in the company that really do care and really want to help but getting to the right person can be frustrating at times.
08-31-2013 9:41 PM
A few months back we started getting stickers with the RGs that said IPv6 compatible.
I believe it will show IPv6 disabled in the RG settings unless your account is provisioned for IPv6. No idea when they will release that...
09-02-2013 10:55 AM - edited 09-02-2013 10:56 AM
Apparently there is a memory leak situation with IPv6 on the 2Wire/Pace gateways that is being actively worked on for resolution. Hence, why the widespread IPv6 rollout to existing RGs has been kind of stalled. The new firmware is also breaking customers with existing IPv6 tunnels passing thru from a router behind the RG which is also in the dev pipeline for fixing. These issues do not appear to exist on the new Motorola NVG589 platform but, regardless, the IPv6 profile is not being enabled by default, yet. You can ask the AT&T social media team very nicely to have it enabled or post in the AT&T Direct forum on DSLReports.com. http://www.dslreports.com/forum/sbcdirect
10-04-2013 7:48 AM - edited 10-04-2013 7:50 AM
We are working to enable IPv6 for all of our consumer broadband customers and when we have a firmware update for IPv6, we will push it to our devices and enable it. For more information, please refer to www.att.com/ipv6.
Did a post have a solution that worked for you? Help other people find solutions faster by marking posts that helped you as an "Accepted Solution". Learn about accepted solutions: Learn More.
10-04-2013 10:43 AM
Thanks, I know you're trying, but unfortunately, you're not doing a very good job of it:
In your efforts to roll out ipv6 you've pushed an interim firmware update to the 2wire gateways that drops ip protocol 41. That means that, for anyone who set your gateway in bridge mode to run their own ipv6 tunnel, you've just broken their ipv6 connectivity.
I know you guys are trying, but this makes AT&T look extreemly like amateurs
10-09-2013 10:44 PM
A couple months later and still no IPv6. IF they weren't ready to roll out IPv6 they should have not have upgraded the firmware on my 3800 router since the firmware update broke my IPv6 tunnel and in the mean time I have absolutely no IPv6 connectivity here because the router now blocks Protocol 41 (required for the Hurricane Electric IPv6 Tunnel).
10-18-2013 6:01 AM
I just got the firmware upgrade last night, and it is also blocking IPv6 on my network. I use Microsoft Direct Access, which requires IPv6 tunneling, and now my Direct Access connection is dead in the water. The firewall should provide a way for the customer to add protocol 41 for allowing traffic, so that we can keep tunneling.
Fortunately my work has native IPv6, so IF I ever get IPv6, I can just modify Direct Access to use native IPv6 and IPsec tunneling. But having IPv6 blocked, and also not being offered native IPv6 puts me in a very bad place. I designed and installed the Microsoft Direct Access infrastructure for my work, and I can no longer support it from my own home. Worse yet, all other employees on U-Verse in my area will also likely be blocked, which breaks our ability to remotely manage our work-owned devices that are used at home.
This isn't just about a few customers who were using IPv6 tunnels, this is about breaking RFC compliant tunnels, that have useful purposes.
10-18-2013 6:36 AM
I agree, I spent a few hours on the phone with AT&T, and between the fact that no one on the phone understood what a tunnel was, or that the RG had a DMZ mode, and that there is no acutal process for reporting a firmware bug ni the RG, I gave up. I wound up upgrading to the 45MBs service, which came with the new Motorolla RG kit, and it still passes protocol 41 traffic. It works fine now with my personal tunnel
Welcome to the AT&T TV Hub!We have some helpful articles located under TV Hot Topics.On the left you will see DIRECTV and U-verse TV links. Click on those links for more information regarding Apps, Billing, and TV troubleshooting tips.