Cable users: ping your default gateway please...

Page 3 - Seeking answers? Join the AnandTech community: where nearly half-a-million members share solutions and discuss the latest tech.

futuristicmonkey

Golden Member
Feb 29, 2004
1,031
0
76
time=46ms
time=17ms
time=46ms
time=18ms
time=47ms
time=19ms
time=47ms
time=17ms
time=55ms
time=21ms
time=49ms
time=19ms
time=47ms
time=44ms
time=21ms
time=17ms
time=54ms
time=20ms
time=51ms
time=17ms
time=43ms
time=20ms
time=57ms
time=21ms
time=48ms


:( I live in Winnipeg, have Shaw Cable, and a WHOIS lookup shows the default gateway is in Calgary :|
 

kt

Diamond Member
Apr 1, 2000
6,032
1,348
136
Originally posted by: Eli
Originally posted by: TheGoodGuy
Pinging 24.10.40.1 with 32 bytes of data:

Reply from 24.10.40.1: bytes=32 time=24ms TTL=254
Reply from 24.10.40.1: bytes=32 time=115ms TTL=254
Reply from 24.10.40.1: bytes=32 time=17ms TTL=254
Reply from 24.10.40.1: bytes=32 time=23ms TTL=254
Reply from 24.10.40.1: bytes=32 time=41ms TTL=254
Reply from 24.10.40.1: bytes=32 time=15ms TTL=254
Reply from 24.10.40.1: bytes=32 time=72ms TTL=254
Reply from 24.10.40.1: bytes=32 time=12ms TTL=254
Reply from 24.10.40.1: bytes=32 time=32ms TTL=254
Reply from 24.10.40.1: bytes=32 time=12ms TTL=254
Reply from 24.10.40.1: bytes=32 time=25ms TTL=254
Reply from 24.10.40.1: bytes=32 time=14ms TTL=254
Reply from 24.10.40.1: bytes=32 time=51ms TTL=254
Reply from 24.10.40.1: bytes=32 time=24ms TTL=254
Reply from 24.10.40.1: bytes=32 time=23ms TTL=254
Reply from 24.10.40.1: bytes=32 time=16ms TTL=254
Reply from 24.10.40.1: bytes=32 time=13ms TTL=254

Ping statistics for 24.10.40.1:
Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 115ms, Average = 31ms
Ouch.

Ouch?

Look at this:

PING 69.169.32.1 (69.169.32.1): 56 data bytes
64 bytes from 69.169.32.1: icmp_seq=0 ttl=254 time=107.7 ms
64 bytes from 69.169.32.1: icmp_seq=1 ttl=254 time=41.2 ms
64 bytes from 69.169.32.1: icmp_seq=2 ttl=254 time=97.6 ms
64 bytes from 69.169.32.1: icmp_seq=3 ttl=254 time=43.6 ms
64 bytes from 69.169.32.1: icmp_seq=4 ttl=254 time=109.3 ms
64 bytes from 69.169.32.1: icmp_seq=5 ttl=254 time=76.4 ms
64 bytes from 69.169.32.1: icmp_seq=6 ttl=254 time=86.8 ms
64 bytes from 69.169.32.1: icmp_seq=7 ttl=254 time=73.4 ms
64 bytes from 69.169.32.1: icmp_seq=8 ttl=254 time=80.1 ms
64 bytes from 69.169.32.1: icmp_seq=9 ttl=254 time=78.7 ms
64 bytes from 69.169.32.1: icmp_seq=11 ttl=254 time=224.7 ms
64 bytes from 69.169.32.1: icmp_seq=12 ttl=254 time=310.4 ms
64 bytes from 69.169.32.1: icmp_seq=13 ttl=254 time=70.9 ms
64 bytes from 69.169.32.1: icmp_seq=14 ttl=254 time=75.1 ms
64 bytes from 69.169.32.1: icmp_seq=16 ttl=254 time=61.0 ms
64 bytes from 69.169.32.1: icmp_seq=17 ttl=254 time=74.3 ms
64 bytes from 69.169.32.1: icmp_seq=19 ttl=254 time=62.1 ms
64 bytes from 69.169.32.1: icmp_seq=20 ttl=254 time=71.4 ms
64 bytes from 69.169.32.1: icmp_seq=21 ttl=254 time=93.5 ms
64 bytes from 69.169.32.1: icmp_seq=22 ttl=254 time=138.1 ms
64 bytes from 69.169.32.1: icmp_seq=23 ttl=254 time=69.3 ms
64 bytes from 69.169.32.1: icmp_seq=24 ttl=254 time=64.6 ms
64 bytes from 69.169.32.1: icmp_seq=25 ttl=254 time=72.7 ms
64 bytes from 69.169.32.1: icmp_seq=26 ttl=254 time=132.7 ms
64 bytes from 69.169.32.1: icmp_seq=27 ttl=254 time=203.0 ms
64 bytes from 69.169.32.1: icmp_seq=29 ttl=254 time=117.1 ms

--- 69.169.32.1 ping statistics ---
121 packets transmitted, 102 packets received, 15% packet loss
round-trip min/avg/max = 34.4/97.6/310.4 ms


 

NikPreviousAcct

No Lifer
Aug 15, 2000
52,763
1
0
Originally posted by: ndee
Originally posted by: Nik
Originally posted by: ndee
ok, I don't get this thread. What does pinging your gateway has to do with cable?!

If you have a "slow" connection on cable, no cable company will take any ping results that are pinging anything beyond the gateway that you connect to. If your connection is/has a problem, then you'll see it there. If it's just fine but pinging, say, yahoo.com and everything else turns up with problems, it's not the ISP's problem and they'll tell you too bad.

But that doesn't have anything to do with Cable or ADSL, does it? And what's the use if I ping MY default gateway when HE has a problem?

Call in for tech support to your cable ISP for a speed problem and that's one of the first things they'll run you through. I worked for lots of cable ISPs. It's all about the structure of a cable connection. I don't have a clue when it comes to DSL.