06-25-2013 7:58 AM
I ran an IPv6 tunnel from Hurricane Electric (he.net) for a while with my U-verse account and a 3800 HGV-B. The latest software upgrade (22.214.171.124-plus.tm) seem to block IP protocol 41, and I no longer see traffic from he.net coming into the gateway (and no encapsulated IPv6 packets going out).
Is there a way to turn off that block? Or get a software version that does not block protocol 41?
Solved by: Go to Solution.
11-19-2013 11:04 AM
11-19-2013 11:05 AM
I filed a complaint some time ago but have not been contacted by ATT I'm afraid. The fact that they contacted you, however, gives me hope for a solution.
- edited 11-21-2013 9:07 PM
I was also contacted by the same office with regards to my FCC complaint. AT&Ts "solution" was to turn on IPv6 on the 2Wire gateway. But even with that the gateway is still blocking my own tunnels (and thus violating FCC rules). I was using DMZPlus with my own router and naturally was hoping to use DHCP-PD (Prefix Delegation). In the end we know that with AT&T's 6RD setup there is a /60 prefix for each subscriber. But instead the gateway only hands out a single /64 via SLAAC. DHCP can be enabled in the gateway, but is clearly broken. You can even see in the gateway's logfiles a message "dhcpd6: configuration update - No such file or directory".
It's really pathetic how clueless AT&T appears to be and how incompetent they end up being. Just as a reminder: Free, the second largest ISP in France rolled out 6RD to its 40 mio. customers within 5 weeks in 2007.
12-16-2013 9:53 AM
Turns out that the Motorola NVG 589 does connect to an ONT (Fibre-to-the-premise). But in general AT&T won't give you such a gateway for a ONT deployment. They will only give it out for higher speed DSL deployments which need the second line.
You might therefore be a bit persistent until they finally install it. And even then most technicians won't know that it's possible and might claim it's not possible. Just because they have never done it.
12-16-2013 9:56 AM
Certainly seems like ATT has a solution available but is just unwilling to allow for it. That's a shame. I'm not sure what else I can do apart from file an complaint with the FCC and spend hours in support chat/phone limbo.
Come on ATT, it's the Holidays!
12-19-2013 12:46 PM
Was contacted by AT&T today to schedule a replacement if the CPE gateway device. I accepted but explained that it would not address the FCC compliant and I would not consider that compliant resolved. Simply because they are still in violation of rule 09-191 section ii.
ii. No blocking. Fixed broadband providers may not block lawful content, applications, services, or non-harmful devices; mobile broadband providers may not block lawful websites, or block applications that compete with their voice or video telephony services.
01-05-2014 2:11 PM
I've been waiting since July for this to be fixed.
I switched to Uverse from Comcast in August of 2012, and I'm pretty disappointed with the overall IPv6 rollout. Using 6rd as the migration strategy is kind of a joke, but I was willing to chuckle a little and deal with it as long as my tunnels kept working. Now we're in month 7 of this very basic functionality being broken, and I'm not entirely confident that we're going to see a fix any time soon.
I'm a software developer and I know you can't avoid bugs, but you either fix them or roll back. You don't let them languish for half a year, especially if it's as serious as filtering an entire protocol. This is amateur hour stuff here.
I filed my FCC complaint, and now it looks like it's time to see if Comcast has resolved their service delivery issues in my area and switch back.
02-04-2014 1:18 PM
I just received a bizarre call from AT&T regarding my FCC complaint. Even though this doesn't really affect me any more because I've found a workaround, I just thought everyone would like to know what's really going on and why we haven't seen a fix after 8 months now.
They said they are blocking IPv6 tunnels intentionally because it exposed a "vulnerability in their network" that allows one to access other networks. I said that sounds like the entire purpose of the Internet -- accessing other networks -- and she yelled back "THAT'S NOT TRUE!" She clarified that by creating an IPv6 tunnel you are being allocated a static IPv6 address from a third party that you can use to get back into your network, bypassing AT&T and without paying AT&T extra for a static address.
So, I don't know if this is just some customer service person reading off of a script without really knowing what the words mean and getting it all wrong, or if AT&T just admitted to me that they're not filtering IPv6 tunnels by accident but because they haven't found a way to extract money from us for the privilege. Either way, pretty weird.
05-15-2014 12:36 PM
Any updates on this? It's been a while and, unfortunately, I show protocol 41 is STILL being blocked by ATT, at least on my connection
06-03-2014 9:53 AM
Thanks for all the info and feedback, guys. I would have wasted a lot of time trying to get ATT service hooked up for the simple need of an ipv6 connection, and likely never would have got it. Going back to search for another vendor - ATT's award-winning customer service costs them another potential customer!
|02-07-2019 4:46 PM|
|10-27-2014 8:14 PM|
|12-28-2016 5:04 PM|
|01-24-2013 2:16 PM|
|04-15-2015 5:32 AM|