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 (188.8.131.52-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.
06-26-2013 6:16 PM
06-29-2013 9:56 AM
I just rebooted my router this morning. It came backup. Then it rebooted again with new firmware 6.9.x. Then he.net did indeed go dead. I had such a good luck with he.net too including reverse everything.
If someone comes up with a magic incantation to fix this I would be much appreciated.
First I was thinking...what changed.
06-29-2013 10:19 AM
More info: Something is blocking it.... maybe that future ipv6 support etc..thats turning on screw. Boy.. and I thought rebooting my RG was a great idea.
Manufacturer Pace Plc
Serial Number (censored)
Hardware Version 000778-004
Software Version 184.108.40.206-enh.tm
Key Code (censored)
First Use Date March 8, 2012
Current Date & Time Saturday, June 29, 2013
Central Daylight Time
Time Since Last Boot 0 day 2:27:02
DSL Modem 8.4.C
System Password Custom
06-29-2013 1:51 PM
Yes, that looks exactly like my problem. So it seems that the "enhancement" in the new firmware is responsible for this. :-(
07-03-2013 4:38 PM
This is unfortunately, but there's likely little to be done about it... unless Hurricane Electric can offer a different protocol to use that isn't blocked. If AT&T has blocked it in the RG firmware, they won't easily or quickly unblock it; even if they want to.
08-27-2013 12:12 AM
(answering my own post)
In case you are following this thread and wonder whether there is a solution: Upgraded to the 45 MBit tier today, got a new Motorola gateway.
And it comes with native ipv6 enabled, configured, ready to use.
Which is the most perfect solution to my problem that I could think of. :-)
08-27-2013 7:02 PM
Tunneling allows you to connect clients that use IPv6 to servers that run IPv6 when there is not a direct IPv6 connection. It's sort of like VPN. Some device/software sits "between" the IPv4 and IPv6 networks on both ends of an IPv4 connection and relays packets destined for IPv6 hosts on the other side through the IPv4 connection.
It's a stop-gap solution to allow you to get your feet wet with IPv6 while the full public IPv6 network is being built out.
09-03-2013 5:16 PM
While I realize that using a tunnel is a stopgap measure, at least it was fully functional, and gave me full control over IP range delegation and reverse resolving.
Now, not only is the tunnel non-functional, but IPv6 has not been enabled yet, either:
09-10-2013 12:29 PM
I understand AT&T wanting to block tunnels because I will likely do the same at the University I work for. Kind of a difference there since I'm not an ISP and don't have to worry about FCC guidelines. Let’s see, they are blocking our access to the content /services we desire. They did not disclose these policies to their customers. Two infractions right there without much thought.
Tech Support was less than zero help. I only say negative help because the experience was draining. She wanted me to check my pc to make sure it was enabled in Windows 8. Then she was trying to explain to me how to enable it in my router. Guess AT&T hasn't told their employees they locked us out of that. Then after another few minutes I was informed that AT&T doesn't offer IPv6 in my area. Why the heck are they blocking our tunnels then???
09-10-2013 8:14 PM
When I upgraded to the 45 MBit tier, I got a Motorola modem which not only comes with native IPv6 enabled but the HE tunnel is working again (and their IPv6 peering is better than AT&T so you get better performance by using this instead of the native one).
So in the end, I now have a dual-homed network. :-) Joy.
09-17-2013 12:59 PM
I don't think it's a deliberate block. 6rd (which AT&T is using for their initial v6 deployments) and 6in4 are functionally identical on the wire. The 380x-RG likely sees the HE tunnel traffic as 6rd traffic, grabs it, realizes it's not the traffic it expects it should get, and then drops it on the floor.
My 3800 updated itself this week, and now my tunnel isn't working... and I'm the admin in charge of HE's tunnel services. Yeah, I'm thrilled.
09-27-2013 4:25 PM
This feels like a complete racket. I spent 2 hours on the phone with AT&T today trying to tell them they broke my tunnel with this stupid update. During that time I was disconnected twice (both times being told I couldn't be reconnected with the origional tech, never mind the fact they didnt' use my callback number). Not that it would have mattered, since no one there seems to have any idea what a tunnel was. One person wanted me to update my bios at one point, while the other told me to disable the firewall on my workstation. I finally got hold of the a supervisor who helpfully told me that If I upgraded my service the ipv6 that I had working would work again. This is a major slap in the face...
10-08-2013 1:30 PM
I'm having a similar issue as well. On a 3800HGV-B with the 220.127.116.11-plus.tm firmware. On live chat with ATT now to evaluate my options for trying to disable 6rd (not expecting to get very far unfortunately). I did verify that they aren't providing static network assignments for IPv6 yet - no surprises there (hence why I was previously usiing he.net - quite happily, I might add).