On 01/31/2017 11:26 AM, Rick Stevens wrote:
On 01/31/2017 10:56 AM, Joe Zeff wrote:
> >On 01/31/2017 10:37 AM, Rick Stevens wrote:
>> >> 1. Perform a "traceroutewww.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).
Indeed. However, using -I will often get you more data to work with,
and doesn't take much time, so it's worth trying if a regular traceroute
doesn't get much response.