Upstream Provider Woes? Point the Ping of Blame - page 4
Network Admin's Best Tool
Another good tool is plain old
traceroute. Remote traceroutes are especially interesting. Find these at traceroute.org.
This is good for showing recalcitrant support techs that the problem really is theirs, and not something you are doing, because you can show traceroutes originating from different locations. I know, the old support-by-consensus is lame--"but ma'am, no one else is reporting a problem!" But we often must deal with it.
A side note on traceroute.org--a lot of the links are no longer valid, so it would be nice to politely inform them of any dead links you find.
traceroute is good for is to have your service provider run it from
their end back to you. Sometimes the return path contains problems, so
this is an important step. Especially if they are being fussy about
admitting there is a problem.
ping is still useful for network testing. Suppose that
mtr shows that your ISP is dropping packets like they were toxic waste--ping the offending host and collect some nice statistics:
$ ping ortelco.net PING ortelco.net (184.108.40.206): 56 data bytes 64 bytes from 220.127.116.11: icmp_seq=0 ttl=63 time=41.0 ms 64 bytes from 18.104.22.168: icmp_seq=3 ttl=63 time=1740.2 ms 64 bytes from 22.214.171.124: icmp_seq=4 ttl=63 time=2289.4 ms 64 bytes from 126.96.36.199: icmp_seq=5 ttl=63 time=1971.1 ms .... --- ortelco.net ping statistics --- 100 packets transmitted, 34 packets received, 66% packet loss round-trip min/avg/max = 41.0/1510.4/2289.4 ms
The interesting bits here are the dropped packets and the horrendous ping times. Anything under 100 milliseconds is good. At 150 milliseconds, you'll notice slower-loading Web pages, and possibly mail and Web timeouts. So anything in the thousands is obviously unworkable.
When you contact your
service provider, don't try to attempt a diagnosis. Just show them the
statistics you have collected. There are all kinds of things going on
behind the scenes that
traceroute cannot show you. All you want to do is show proof of a problem--it's up to them to diagnose and fix it.
- 1Linux Top 3: Fedora 24, Peppermint 7 and Solus 1.2
- 2Linux Top 3: Alpine Linux 3.4, deepin 15.2 and Linux Lite 3.0
- 3Linux 4.7 Set to Boost Live Patching, Security and Power Management
- 4Linux 4.6 Charred Weasel adds USB 3.1 Support
- 5Linux Top 3: OpenIndiana 2016.04, Ubuntu 16.04 and Debian's New Leader