$ traceroute 1.1.1.1
traceroute to 1.1.1.1 (1.1.1.1), 64 hops max, 52 byte packets
1 192.168.2.1 (192.168.2.1) 2.229 ms 1.205 ms 0.993 ms
2 one.one.one.one (1.1.1.1) 2.345 ms 1.864 ms 1.705 ms
$ traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 64 hops max, 52 byte packets
1 192.168.2.1 (192.168.2.1) 3.110 ms 1.618 ms 1.186 ms
2 192.168.1.254 (192.168.1.254) 2.041 ms 1.861 ms 1.814 ms
3 99-125-112-1.lightspeed.nsvltn.sbcglobal.net (99.125.112.1) 29.172 ms 22.802 ms 34.993 ms
4 99.174.25.10 (99.174.25.10) 24.747 ms 28.078 ms 23.434 ms
5 99.131.205.130 (99.131.205.130) 24.744 ms * *
6 12.83.112.17 (12.83.112.17) 26.656 ms
12.83.112.9 (12.83.112.9) 25.386 ms 24.526 ms
7 12.122.117.97 (12.122.117.97) 30.676 ms 33.010 ms 31.229 ms
8 192.205.36.218 (192.205.36.218) 30.014 ms 29.280 ms 29.730 ms
9 64.86.113.90 (64.86.113.90) 29.330 ms 34.309 ms 31.055 ms
10 one.one.one.one (1.0.0.1) 29.730 ms 29.970 ms 29.746 ms
For what it is worth, I’m also unable to connect to 8.8.8.8. But 8.8.4.4 is ok. But that is not relevant to this forum.
Interesting. Thanks for the information. It looks like there is nothing I can do to fix it. I’ll just use 1.0.0.1 for now.
For completeness, I tried running a traceroute directly from the router using the web interface on the router. Here is the result:
To 1.0.0.1 (good):
traceroute 1.0.0.1 with: 64 bytes of data
1: 99.125.112.1(99-125-112-1.lightspeed.nsvltn.sbcglobal.net), time=20 ms
2: 99.174.25.10(99.174.25.10), time=23 ms
3: 99.131.205.130(99.131.205.130), time=23 ms
4: 12.83.112.17(12.83.112.17), time=23 ms
5: 12.122.117.97(12.122.117.97), time=28 ms
6: 192.205.36.218(192.205.36.218), time=26 ms
7: 64.86.113.90(64.86.113.90), time=39 ms
8: 1.0.0.1(one.one.one.one), time=31 ms
And to 1.1.1.1 (bad):
traceroute 1.1.1.1 with: 64 bytes of data
1: 1.1.1.1(one.one.one.one), time=0 ms
In one of the articles someone mentioned a possible patch being released by AT&T to address that issue. Maybe check if there is such a patch available. You have to use their router I presume, right? Its the DSL modem, isnt it?
The AT&T router (as the dslreports links mention) is using 1.1.1.1 for some internal routing. It seems some updates have fixed this, but broken other things. The current workaround is to bypass the router with another box that’s forwarding the ethernet authentication pings to the router. Otherwise, the router isn’t handling any traffic. It’s ridiculous. This is also for their 1 Gig fiber products, I imagine they share modems to some extent.