Forum Discussion
More evidence that CenturyLink is broken
Yes. So this is what you're looking at:
1. Your wifi/router, sometimes these show your public IP depending upon the tracert options. Not sure why the modem itself (192.168.0.1) doesn't show.
2. Gateway input from satellite
(not sure why it's showing a shared IP on yours, should be something in 69.35.184.0/21 like the other two)
3. Gateway processing
4. Gateway output to internet (may vary)
5. Upstream provider to gateway
6. [is always obfuscated by ICMP blocking for some reason on CL, but should be the provider's backbone]
...
all the other nodes to the target address.
Thanks for the info. I guess the differences may be caused by my use of the Linux version of traceroute.
- MarkJFine6 years agoProfessor
Should be the same as my Mac... FreeBSD version.
- gaines_wright6 years agoTutor
MarkJFine wrote:Should be the same as my Mac... FreeBSD version.
Well, again thanks. I may abandon my attempts to understand all of this, especially since today I did another trace to aol.com, and found that many of the hops past the first 6 had disappeared. Yesterday I had several hops to telia, which is in Sweden, and hinet which is in Taiwan. All gone today, aol.com went from 22 hops to 15 hops overnight.
Ahhh! It just occurred to me that the routing table could be constantly changing, and this makes the hops change also. Question is, do I really need to know all of this stuff while retired and 72 years old? I'll probably stick with it for a while, I've always loved useless information. :>)>
- MarkJFine6 years agoProfessor
Yes, it is dynamic and CenturyLink's backbone controls much of the routing table by virtue of where it sends you first. Sometimes it's due to known down links. Sometimes it's because they're just that screwed up. Clearly my view is the latter.
Related Content
- 5 years ago
- 2 years ago
- 2 years ago