On 12/11/2018 04:04 PM, Beartooth wrote:
Hoo, boy! I haven't so much as heard of traceroute in ten or fifteen years, and never did grep its uses. I can look it up, of course, but it might be worth your while to just tell me a command (and to use it as root if that should be desirable).
For all practical purposes, traceroute pings each hop along the way to the destination three times. (That's not really how it does it, but don't worry about it.) If you can't ping someplace, traceroute will show you where the problem is, because it will stop getting responses. Also, if you've got a slow connection, you can tell where the issue is because the return times will suddenly jump. The only time you need root for it is for traceroute -I, because that uses ICMP ECHO for probes, but can get response where nothing else does. Back when I was doing tech support for an ISP, we used it all the time on calls to find out why connections were slow, and usually to show the caller that it was outside our network.
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
