Many (most?) routers deprioritize ICMP meesages. Direct pings against the router are not informative re transit failures.
On Sep 26, 2012, at 11:37 AM, Derek Ivey wrote: > After some further troubleshooting, I believe I have narrowed down the issue > to one of Verizon's routers (130.81.28.255). > > ping 130.81.28.255 repeat 100 > Type escape sequence to abort. > Sending 100, 100-byte ICMP Echos to 130.81.28.255, timeout is 2 seconds: > ?!!!!!!!!?!!!!!!!?!!!!!!!!?!!!!!!!!!!!!!!!?!!!!!!!!!!!!!!?!!!!!!!!!!!? > !!!!!!!!!!!!!!!!!!!!!!?!!!?!!! > Success rate is 91 percent (91/100), round-trip min/avg/max = 20/26/30 ms > > I had my client send me the output of the ping command (100 pings) and a > trace route. > > Their 5th hop is 130.81.28.254 and one of the response times in their trace > route was 175ms so the issue seems to be around there. > > I asked them to open a ticket with Verizon to take a look. > > Thanks, > Derek > > On Sep 26, 2012, at 1:54 PM, Derek Ivey <[email protected]> wrote: > >> Thanks guys. That was an informative read. I will do some more >> troubleshooting. >> >> Derek >> >> On Sep 26, 2012, at 1:16 PM, Darius Jahandarie <[email protected]> wrote: >> >>> On Wed, Sep 26, 2012 at 1:10 PM, Blake Dunlap <[email protected]> wrote: >>>> This is not the proper way to interpret traceroute information. Also, 3 >>>> pings is not sufficient to determine levels of packet loss statistically. >>>> >>>> I suggest searching the archives regarding traceroute, or googling how to >>>> interpret them in regards to packet loss, as what you posted does not >>>> indicate what you think it does. >>> >>> Agreed. Derek should read "A Practical Guide to (Correctly) >>> Troubleshooting with Traceroute": >>> http://www.nanog.org/meetings/nanog45/presentations/Sunday/RAS_traceroute_N45.pdf >>> >>> -- >>> Darius Jahandarie >> > > -- Jo Rhett Net Consonance : net philanthropy to improve open source and internet projects.
