On 01/31/2017 10:56 AM, Joe Zeff wrote: > On 01/31/2017 10:37 AM, Rick Stevens wrote: >> 1. Perform a "traceroute www.google.com" or other site you >> are having issues with. You may find a hop in the route taken >> that points to an issue. > > Sometimes, you'll get no response from most of the hops (nothing but > ***) but it gets through. If that happens, try traceroute -I instead, > although you'll need to do it as root. That uses ICMP ECHO for the > probes, and is less likely to be dropped. Yes, that is true, but keep in mind that -I may also not work. Sometimes pings are not returned (if the target has ICMP blocked for some reason, such as being the VIP for a load balanced cluster). The important thing is for the hops that return data, looking to see if some of the hops are slow. It also would be useful to let ping run for 15-20 seconds to get a fair sampling. A single ping is rarely enough except to merely check for connectivity and one may see some pings take a LOT longer to happen than others. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@xxxxxxxxxxxxxx - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - We have enough youth, how about a fountain of SMART? - ---------------------------------------------------------------------- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
