 NormanSPremium,MVM
join:2001-02-14
San Jose, CA
kudos:9
 ·SONIC.NET
·Pacific Bell - SBC
| reply to eagleknight
said by eagleknight:I am at my aunt and uncles house for a wedding. Their Charter cable service is terrible and it doesn't seem to be congested time problems. Check out this packet loss. Tried power cycling their router and modem, but that didn't help.
...
...
11 18 ms 21 ms 17 ms ord08s06-in-f1.1e100.net [74.125.225.33]
Trace complete.
I don't see any packet loss where it counts. Check out this packet loss:
C:\>tracert www.aol.com
Tracing route to v6v4.portal-standard.aol.akadns.net [207.200.111.13]
over a maximum of 30 hops:
1 <1 ms <1 ms 1 ms homeportal [192.168.42.1]
2 25 ms 25 ms 26 ms 173-228-7-1.dsl.static.sonic.net [173.228.7.1]
3 25 ms 24 ms 24 ms gig1-4.cr1.lsatca11.sonic.net [70.36.243.13]
4 35 ms 24 ms 25 ms 0.xe-5-1-0.gw.pao1.sonic.net [69.12.211.1]
5 28 ms 26 ms 26 ms xe-1-0-6.ar1.pao1.us.nlayer.net [69.22.130.85]
6 24 ms 24 ms 24 ms ae0-90g.cr1.pao1.us.nlayer.net [69.22.153.18]
7 25 ms 26 ms 25 ms ae1-70g.cr1.sjc1.us.nlayer.net [69.22.143.165]
8 29 ms 30 ms 26 ms ae1-40g.ar2.sjc1.us.nlayer.net [69.22.143.118]
9 28 ms 26 ms 26 ms TenGigE0-2-2-0.GW3.SJC7.ALTER.NET [152.179.48.21]
10 28 ms 25 ms 25 ms 0.xe-4-0-2.XL4.SJC7.ALTER.NET [152.63.50.161]
11 25 ms 25 ms 24 ms 0.ae4.BR1.SJC7.ALTER.NET [152.63.51.42]
12 93 ms 93 ms 94 ms 204.255.168.182
13 94 ms 94 ms 95 ms dar1-ntc-xe-1-1-0.atdn.net [66.185.152.88]
14 95 ms 95 ms 95 ms edge1-ntc-xe-0-0.net.aol.com [66.185.142.130]
15 * * * Request timed out.
...
...
...
30 * * * Request timed out.
Trace complete.
Despite this severe packet loss, www.aol.com comes up with decent snap in my browser.
Some things to consider WRT trace route:
• Endpoint may block diagnostic packets, as does AOL in my trace. It is a basic defense against DoS by the "Ping of Death".
• Intermediate routers may de-prioritize, or even ignore, diagnostic packets, as your trace suggests. Transit routers have more important work to do than answer every diagnostic packet which comes their way.
• If the final hop shows no packet loss, then all that apparent packet loss on the way is phantom packet loss.
The only sure way to know if there is packet loss on any given route is to run a reverse trace from the destination. That would require either a "looking glass" server on the destination (which most don't have), or the cooperation of a technician at the destination.
Trace route isn't totally useless, but it does have its shortcomings.
"Their Charter cable service is terrible ..." isn't a helpful problem statement. In what manner is the service so terrible?
--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum |
