madler
join:2000-04-07
Saint Louis, MO
1 edit | [HSI] Packet loss problem, timeouts pinging google. Help!
I've been having lots of packet loss issues with random timeouts on just certain routes. For example, pinging yahoo.com has no packet loss while pinging google does. Here's my traceroute, ping and modem signal levels. Any ideas? Why are my packets being routed through multiple Charter DHCP servers?
Receive Power Level
8.8 dBmV
Transmit Power Level
47.0 dBmV
Tracing route to www.google.com [64.233.167.104]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 10.29.208.1
3 9 ms 9 ms 9 ms 24-217-4-45.dhcp.stls.mo.charter.com [24.217.4.4
5]
4 10 ms 9 ms 10 ms 24.217.3.1
5 10 ms 9 ms 10 ms 24-217-58-82.dhcp.stls.mo.charter.com [24.217.58
.82]
6 341 ms 9 ms 9 ms 24.217.2.130
7 18 ms 18 ms 17 ms so-1-2-0.gar2.chi1.bbnplanet.net [4.79.74.1]
8 22 ms 19 ms 19 ms ae-11-51.car1.Chicago1.Level3.net [4.68.101.2]
9 31 ms 19 ms 17 ms GOOGLE-INC.car1.Chicago1.Level3.net [4.79.208.18
]
10 19 ms 20 ms 19 ms 66.249.94.133
11 20 ms 36 ms 20 ms 72.14.232.70
12 21 ms 19 ms 19 ms py-in-f104.google.com [64.233.167.104]
Trace complete.
Pinging www.google.com [64.233.167.99] with 32 bytes of data:
Reply from 64.233.167.99: bytes=32 time=22ms TTL=242
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Request timed out.
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Reply from 64.233.167.99: bytes=32 time=21ms TTL=242
Reply from 64.233.167.99: bytes=32 time=21ms TTL=242
Request timed out.
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Request timed out.
Request timed out.
Reply from 64.233.167.99: bytes=32 time=21ms TTL=242
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Request timed out.
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Request timed out.
Request timed out.
Reply from 64.233.167.99: bytes=32 time=20ms TTL=242
Request timed out.
Request timed out.
Reply from 64.233.167.99: bytes=32 time=383ms TTL=242
Request timed out.
Request timed out.
Reply from 64.233.167.99: bytes=32 time=21ms TTL=242
Reply from 64.233.167.99: bytes=32 time=19ms TTL=242
Request timed out.
Reply from 64.233.167.99: bytes=32 time=19ms TTL=242
Request timed out.
Request timed out.
Reply from 64.233.167.99: bytes=32 time=21ms TTL=242
Reply from 64.233.167.99: bytes=32 time=19ms TTL=242
Reply from 64.233.167.99: bytes=32 time=19ms TTL=242
Request timed out. |
|
CBN Tech
Premium
join:2006-11-10
Louisville, KY | WHere do u see multiple DHCP servers???
--
CBN TECH |
|
CBN Tech
Premium
join:2006-11-10
Louisville, KY
1 edit | reply to madler
.... |
|
madler
join:2000-04-07
Saint Louis, MO | reply to CBN Tech
hop 3 & 5
3 9 ms 9 ms 9 ms 24-217-4-45.dhcp.stls.mo.charter.com [24.217.4.4
5]
4 10 ms 9 ms 10 ms 24.217.3.1
5 10 ms 9 ms 10 ms 24-217-58-82.dhcp.stls.mo.charter.com [24.217.58
.82] |
|
Velosity
join:2006-12-08
Cape Girardeau, MO | reply to madler
Wow, CBN just kind of dropped off the earth on this one. I am in Cape Girardeau, MO and am seeing the same thing from my Charter Fiber Connection. Just seems to be google mainly though. |
|
pbarrow
Premium
join:2003-09-16
Montgomery, AL
1 edit | reply to madler
Try pinging your CMTS 10.29.208.1 instead of google and see if you see the timeouts on your CMTS.
If so you probably have a noisy Cable Plant between you and the headend someplace.
I've had this problems off and on for 2 years with Charter on my Node.
Sometimes it's been the cables/Tap outside my apartment and other times it's been at locations farther away toward the headend. |
|
sittin_tech
join:2004-04-13
Rochester, MN
2 edits | reply to madler
I've noticed a few dropped packets for a couple years when doing a continuous ping to google. When I'm testing a connection of looking for connection problems, I ping yahoo. I assumed google was dropping low priority packets, but I guess I could be wrong.
but I never see as many dropped packets as your seeing, I see maybe 8 out of 100 |
|
CBN Tech
Premium
join:2006-11-10
Louisville, KY | reply to madler
Those are DHCP addressed not DHCP servers. DHCP IP addresses can not have a PTR record set up on them. They are just 2 routers in STL that have DHCP IP addresses.
--
CBN TECH |
|
