dslreports logo
    All Forums Hot Topics Gallery


how-to block ads

Search Topic:
share rss forum feed


Riverside, CA

3801 and IPv6

It would be nice to get a status update on this. I only just noticed that my HE.net tunnel stopped working today due to the new 3801 firmware update which seems to block protocol 41 entirely, and it would be kind of nice to have some sort of IPv6 working again.

I realize that there is a reason for not enabling it by default, namely that 2wire/Pace devices such as mine may still have a memory leak to resolve. If I can't have 6rd without my residential gateway device flaking out on regular intervals, then can I at least have a workaround to get my old tunnel working?

Hell, the reason I was using my original tunnel instead of the 6rd posted in some topics on this forum was that the 6rd server posted was frequently overloaded, resulting in IPv6 connectivity that was flaky at best, downright unusable at worst. I hope at least that much of it has been resolved by now.

Dallas, TX
·AT&T U-Verse
I haven't heard any updates on the issue. I was told that the fixes are actively being developed by Pace in coordination with engineers from AT&T. I would guess that it will be at least another 4-6 weeks, until they have something solid enough for real beta testing. I expect the fix won't be released before the end of the year and we won't see it show up in a firmware update before end of Q1 2014.
Scott, CCIE #14618 Routing & Switching