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 (18.104.22.168-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.
10-09-2013 1:09 AM
Apparently I got the upgrade today, was trying to figure out why my tunnel broke, then happened upon this thread.. Called CS about this, got transferred to level2, explained the issue and got hung up on. Not exactly thrilled about this...
10-09-2013 2:04 PM
Please let us know how it goes, and what v6 you wind up with. Especially if the tunnel works with this new gateway.
10-09-2013 3:03 PM
I actually just got a shipping notification, but it shows Item Shipped: 2Wire3801HGV, I sure hope that is not what they actually sent after being told they were sending a NVG589..
10-09-2013 3:24 PM
10-09-2013 3:43 PM
Well, its very poor service when I specificlly tell them something, they call me back and tell me they are sending a 589, but send a 3801 anyway. Breaking ipv6 one day, hanging up on me the next day, and flat out lying to me is not really good customer service, If in this case I'll wait until whatever they sent shows up, and decide what to do then.
- edited 10-09-2013 4:51 PM
By the way, my 3800HGV-B gateway has been upgraded to firmware 22.214.171.124 and I have lost IPv6 tunneling capability just like everyone else.
I can also confirm that protocol 41 is blocked even to my block of static IP addresses.
There is one more configuration option that I'm going to try (the new cascaded router option) and see if that works any differently, but I'm not hopeful.
10-09-2013 8:06 PM
10-09-2013 8:32 PM
Requiring someone to pay more to fix a problem introduced by a change on your side isn't exactly what most people would consider a solution. If it's a firmware bug, fine. Bugs happen. Give us some hope that there's a fix in QA for deployment.
10-09-2013 8:53 PM
They should not of offered me the 589 in the first place then. Also looking at another forum, kind of looks like the 3801 has the same problem, so sending me someting that has the same issue is not going to have much effect. If they want to roll the 3800 firmware back to something that works, I'll be happy with that too, but that does not seem to be possible, and was already told I can get a 589. Having to pay more to upgrade to 45mb like the OP did to basically get my full service restored is not really a good solution.
10-09-2013 10:46 PM
10-10-2013 7:33 PM
I was in the same boat as everyone here. 3800 gateway, 6.9 firmware and no more IPv6 tunnel through HE. i talked to AT&T support and they confirmed the 3800 doesnt support it. I stewed over it and decided to follow OP's lead, I requested the new 45Mbit connection. a 5 hour service call later, I now have the motorola gateway and my IPv6 capability is back. this shouldnt cost me much of anything because I can now call and downgrade back to my 18Mbit connection. i might be charged a little for the prorated use of 45Mbit but there were no other charges for the upgrade.
10-11-2013 8:46 AM
They sent a tech out today, and he replaced the 3800 with a NVG589,native IPv6 is not enabled on it, but my tunnel is back in working order.
- edited 10-11-2013 11:51 AM
It may not be a deliberate, but my 3800 blocks protocol 41 not only for packets addressed to the box's own IP address, but also to any address in the separate /29 block for which I pay extra.
This is the last straw; I've ordered Time Warner (which at 5/50 is now faster than Uverse at 3/24) and will dump U-verse when I have everything reconfigured.
Yet another promising technology ruined by corporate incompetence. What happened to AT&T, anyway? They once knew what they were doing.
10-11-2013 1:54 PM
That is what upset me the most is it was blocked for my /29, I'm paying for, I mainlhy have the /29 so I could run a couple tunnels, At least I'm fixed up, but had to waste a lot of time, sad to say it would of been a lot easier to call TWC or WOW then to deal with the garbage CS put me through.