--------------------------------------------- The packet loss shown at hops #4, #5, and possibly #6 is either ICMP deprioritisation or high CPU utilisation on said routers. My vote is --------------------------------------------- You could know this if you used tcptraceroute instead: michael.toren.net/code/tcptraceroute There is something similar (but I can't remember the tool name) for micro$loth. scott
----- Original Message ----- From: "Scott Weeks" Sent: Tuesday, August 18, 2009 10:55 AM Subject: Re: [outages] Level3 Chicago
--------------------------------------------- The packet loss shown at hops #4, #5, and possibly #6 is either ICMP deprioritisation or high CPU utilisation on said routers. My vote is ---------------------------------------------
You could know this if you used tcptraceroute instead: michael.toren.net/code/tcptraceroute
There is something similar (but I can't remember the tool name) for micro$loth.
scott
Windows version is tracetcp.exe http://tracetcp.sourceforge.net/ --Michael
There is also lft or layer 4 traceroute http://pwhois.org/lft/index.who Richard On Aug 18, 2009, at 2:55 PM, Michael Painter wrote:
----- Original Message ----- From: "Scott Weeks" Sent: Tuesday, August 18, 2009 10:55 AM Subject: Re: [outages] Level3 Chicago
--------------------------------------------- The packet loss shown at hops #4, #5, and possibly #6 is either ICMP deprioritisation or high CPU utilisation on said routers. My vote is --------------------------------------------- You could know this if you used tcptraceroute instead: michael.toren.net/code/tcptraceroute There is something similar (but I can't remember the tool name) for micro$loth. scott
Windows version is tracetcp.exe
http://tracetcp.sourceforge.net/
--Michael _______________________________________________ outages mailing list outages@outages.org https://puck.nether.net/mailman/listinfo/outages
participants (3)
-
Michael Painter -
Richard Dunn -
Scott Weeks