Reachability issue on ATT with Arris BGW210


#1

Hi,

I can’t access 1.1.1.1 or 1.0.0.1 on ATT DSL in the United States with an Arris BGW210 customer gateway.

>tracert 1.1.1.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.1.1.1]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18  ^C

>tracert 1.0.0.1

Tracing route to 1dot1dot1dot1.cloudflare-dns.com [1.0.0.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dsldevice.attlocal.net [192.168.1.254]
  2  dsldevice.attlocal.net [192.168.1.254]  reports: Destination host unreachable.

Trace complete.

I tweeted at AttCares, but received unhelpful responses. They said my feedback would be taken into account and offered no follow up or comment on the issue. Given my typical experience contacting big telecom support, I won’t be trying by phone and sitting around or given the run around for hours, but I hope this report helps Cloudflare make their own contact and get this modem issue resolved. I’d love to use this service!


#2

Thanks, one of the main produce managers involved in the launch of 1.1.1.1 has the same issue. He was just as pleased :stuck_out_tongue:

You can still use 1.0.0.1 and the IPv6 DNS server addresses listed here:

Between those 3 I think you probably have enough redundancy. :smiley:


#3

Thanks for the quick reply!

I was able to confirm that the IPv6 addresses are reachable and resolve addresses on Windows. 1.0.0.1 is unreachable, however and as a consequence unusable as a resolver. The traceroute to it was included in my OP. Unfortunately, I don’t primarily use Windows, and have IPv6 disabled on my Linux installation due to it causing issues on my adapter. I suppose I’ll have to see if I can get the IPv6 stack to cooperate until I get a router or the modem firmware is updated.