Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Bill Merriam <lists@billmerriam.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] IPv6 on AT&T
Date: Sat, 8 Feb 2014 13:12:18 -0500	[thread overview]
Message-ID: <20140208131218.1ec07e75@giga.billmerriam.com> (raw)
In-Reply-To: <CAA93jw6u1pMiELN5ssO3_6d050D==YjOYZDSgp4hi7z4mUsOFw@mail.gmail.com>

On Thu, 6 Feb 2014 16:50:58 -0500
Dave Taht <dave.taht@gmail.com> wrote:

> I have discovered that several forms of tunnelling no longer work
> (sigh, 1 step forward, 2 back) on networks like AT&Ts. This shows some
> documentation on how people used to get 6rd up on AT&T
> 
> https://www.tunnelbroker.net/forums/index.php?topic=2293.0
> 
> And this reports it recently broken.
> 
> http://www.dslreports.com/forum/r28530086-AT-T-now-blocking-IPv6-tunnels
> 
> I have ordered a ipv6 capable dsl box for the one AT&T based network I
> have access to.
> 
> I still haven't got hurricane electric to work again on comcast,
> either, since I got an ipv6 capable modem. This has caused all sorts
> of renumbering headaches... and I don't know what to point fingers at.
> 
> Anybody have working ipv6 on AT&T?
> 

I have ATT DSL in Gainesville, Florida, USA and my ATT 6rd tunnel works
and my HE tunnel works also.  I have a Westell 6200 modem.  I put it in
bridge mode so PPPoe and the tunnels are all running from cerowrt.

I don't routinely activate either tunnel since it slows down my
traffic.

I have a long ago grandfathered fixed IP4 address.  Because of the way
6rd works that gives me fixed IPv6 addresses.

BTW.  One benefit of the HE tunnel over ATT 6rd is that HE lets me
control rDNS.  I doubt ATT will ever provide that for a residential
account.

Bill

  reply	other threads:[~2014-02-08 18:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-06 21:50 Dave Taht
2014-02-08 18:12 ` Bill Merriam [this message]
2014-02-08 19:51   ` Dave Taht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140208131218.1ec07e75@giga.billmerriam.com \
    --to=lists@billmerriam.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox