IanGuy,
Traceroute cannot be used to measure packet loss. Once you have done a trace, you need to ping each host after your STB/modem, this is also the only way to determine where the packets are being dropped. So with a trace like this:
Quote:
traceroute to www9.thdo.bbc.co.uk (212.58.224.55), 30 hops max, 52 byte packets
1 ROUTER (x.x.x.x) 1.198 ms 1.265 ms 1.184 ms
2 STB (x.x.x.x) 12.999 ms 22.547 ms 11.266 ms
3 bagu-t2cam1-a-v119.inet.ntl.com (80.5.162.77) 9.134 ms 9.980 ms 13.416 ms
4 bagu-t2core-a-ge-wan63.inet.ntl.com (80.5.161.17) 12.465 ms 9.683 ms 13.291 ms
5 ETC...
|
first ping the host immediately after your STB/modem and work outwards until you find where the packets are being lost. You also need to make sure you have a decent sample size for a % figure to be meaningful, on windows I would use:
My issue was packet loss between STB and the next hop, spoke to customer support earlier, they told me there was a power level issue and booked an engineer for Monday morning. After they ran the diagnostic AGC was down to 47% from 64 and I'm now seeing a consistant 1% packet loss (100 pkts). HTH.