Tracert and Number of Hops

Tracert and Number of Hops
NewsGroups | Search | Tools
User Password
Register Now! Lost Password?
 comp.dcom.modems.cable  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Tracert and Number of Hops geoff 01-30-2006
Posted by geoff on January 30, 2006, 5:09 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Sometimes, things are dog slow, my provider is earthlink and it goes through
road runner's network. The ip address is supposed to be dynamic but I have
left my cable modem off for like a day and when I turn it on, I get the same
ip address as before. It seems sprintlink is really slow, can anything be
down about it? Here is the tracert for a server in the usa:

1 1 ms 2 ms 1 ms user-10lfea9.cable.mindspring.com
[65.87.185.73]
2 8 ms 16 ms 8 ms 10.42.32.1
3 9 ms 9 ms 18 ms gig2-2.rlghncj-rtr1.nc.rr.com [24.25.1.33]
4 9 ms 12 ms 8 ms srp5-0.rlghncg-rtr1.nc.rr.com [24.25.2.148]
5 9 ms 19 ms 10 ms pos1-0.rlghnca-rtr1.nc.rr.com [24.25.20.17]
6 9 ms 12 ms 10 ms pos14-0.rlghncrdc-rtr1.nc.rr.com [24.25.0.5]
7 8 ms 17 ms 9 ms son0-0-3.rlghncrdc-rtr3.nc.rr.com
[24.93.64.34]
8 27 ms 24 ms 34 ms so-8-1.car1.Washington1.Level3.net
[67.29.172.5]
9 26 ms 26 ms 25 ms ae-14-51.car4.Washington1.Level3.net
[4.68.121.17]
10 22 ms 31 ms 21 ms sprint-level3-te.Washington1.Level3.net
[4.68.111.170]
11 22 ms 22 ms 23 ms sl-st21-ash-5-0.sprintlink.net
[144.232.29.206]
12 25 ms 23 ms 22 ms sl-bb26-rly-6-0.sprintlink.net
[144.232.20.135]
13 48 ms 47 ms 45 ms sl-bb25-chi-3-0.sprintlink.net
[144.232.20.89]
14 46 ms 45 ms 48 ms sl-bb24-chi-14-0.sprintlink.net
[144.232.26.82]
15 66 ms 67 ms 68 ms sl-bb20-che-2-0.sprintlink.net
[144.232.20.161]
16 66 ms 65 ms 65 ms sl-gw10-che-9-0.sprintlink.net
[144.232.15.146]
17 94 ms 95 ms 92 ms sl-lesea-4-1-0.sprintlink.net
[144.232.141.42]
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.



Posted by BigJim on January 30, 2006, 6:16 pm
time out is not good and anything under lets say 125ms is ok
for cable
> Sometimes, things are dog slow, my provider is earthlink and it goes
> through road runner's network. The ip address is supposed to be dynamic
> but I have left my cable modem off for like a day and when I turn it on, I
> get the same ip address as before. It seems sprintlink is really slow,
> can anything be down about it? Here is the tracert for a server in the
> usa:
>
> 1 1 ms 2 ms 1 ms user-10lfea9.cable.mindspring.com
> [65.87.185.73]
> 2 8 ms 16 ms 8 ms 10.42.32.1
> 3 9 ms 9 ms 18 ms gig2-2.rlghncj-rtr1.nc.rr.com [24.25.1.33]
> 4 9 ms 12 ms 8 ms srp5-0.rlghncg-rtr1.nc.rr.com [24.25.2.148]
> 5 9 ms 19 ms 10 ms pos1-0.rlghnca-rtr1.nc.rr.com [24.25.20.17]
> 6 9 ms 12 ms 10 ms pos14-0.rlghncrdc-rtr1.nc.rr.com [24.25.0.5]
> 7 8 ms 17 ms 9 ms son0-0-3.rlghncrdc-rtr3.nc.rr.com
> [24.93.64.34]
> 8 27 ms 24 ms 34 ms so-8-1.car1.Washington1.Level3.net
> [67.29.172.5]
> 9 26 ms 26 ms 25 ms ae-14-51.car4.Washington1.Level3.net
> [4.68.121.17]
> 10 22 ms 31 ms 21 ms sprint-level3-te.Washington1.Level3.net
> [4.68.111.170]
> 11 22 ms 22 ms 23 ms sl-st21-ash-5-0.sprintlink.net
> [144.232.29.206]
> 12 25 ms 23 ms 22 ms sl-bb26-rly-6-0.sprintlink.net
> [144.232.20.135]
> 13 48 ms 47 ms 45 ms sl-bb25-chi-3-0.sprintlink.net
> [144.232.20.89]
> 14 46 ms 45 ms 48 ms sl-bb24-chi-14-0.sprintlink.net
> [144.232.26.82]
> 15 66 ms 67 ms 68 ms sl-bb20-che-2-0.sprintlink.net
> [144.232.20.161]
> 16 66 ms 65 ms 65 ms sl-gw10-che-9-0.sprintlink.net
> [144.232.15.146]
> 17 94 ms 95 ms 92 ms sl-lesea-4-1-0.sprintlink.net
> [144.232.141.42]
> 18 * * * Request timed out.
> 19 * * * Request timed out.
> 20 * * * Request timed out.
> 21 * * * Request timed out.
> 22 * * * Request timed out.
> 23 * * * Request timed out.
> 24 * * * Request timed out.
> 25 * * * Request timed out.
> 26 * * * Request timed out.
> 27 * * * Request timed out.
>
>



Posted by Warren on January 30, 2006, 6:34 pm
BigJim wrote:
> time out is not good and anything under lets say 125ms is ok
> for cable

Request timed out just means a response was not received. That doesn't mean
anything is wrong. A device can be up and running perfectly, but simply
configured not to respond to ICMP.

Also, the ICMP packets that are sent for pings and traceroutes are very
small. The amount of time it takes to go from point a to point b is not
related to whether you have cable, or what the bandwidth is. Having
broadband affects how much you can move at one time, not the speed at which
it moves.

Think of it this way: Dial-up like putting your data in the trunk of a Kia.
DSL is like putting your data in the back of a station wagon. Cable is like
putting your data in the back of a pick-up truck. If you're sending a lot of
data, that pick-up truck comes in handy. But if you're sending a single
number 10 envelope (your ICMP packet), the capacity of the vehicle is not an
important factor. The size of the driver's bladder is more relevant.

--
Warren H.

==========
Disclaimer: My views reflect those of myself, and not my
employer, my friends, nor (as she often tells me) my wife.
Any resemblance to the views of anybody living or dead is
coincidental. No animals were hurt in the writing of this
response -- unless you count my dog who desperately wants
to go outside now.

Compare and buy TaxCut and TurboTax Software:
http://www.holzemville.com/taxes/




Posted by geoff on February 2, 2006, 12:55 am
> Think of it this way: Dial-up like putting your data in the trunk of a
> Kia. DSL is like putting your data in the back of a station wagon. Cable
> is like putting your data in the back of a pick-up truck. If you're
> sending a lot of data, that pick-up truck comes in handy. But if you're
> sending a single number 10 envelope (your ICMP packet), the capacity of
> the vehicle is not an important factor. The size of the driver's bladder
> is more relevant.

Lol, I like that analogy but also, the pick-up truck goes faster than the
station wagon, and the station wagon faster than the kia. However, as you
said, the driver of the pick-up may be having some bladder control issues.

. . . so, in a gaming situation, the player might hit the command 'shoot'
but the driver is still flushing the urinal . . .

-g



Posted by Warren on February 2, 2006, 3:29 am
geoff wrote:
>> Think of it this way: Dial-up like putting your data in the trunk of a
>> Kia. DSL is like putting your data in the back of a station wagon. Cable
>> is like putting your data in the back of a pick-up truck. If you're
>> sending a lot of data, that pick-up truck comes in handy. But if you're
>> sending a single number 10 envelope (your ICMP packet), the capacity of
>> the vehicle is not an important factor. The size of the driver's bladder
>> is more relevant.
>
> Lol, I like that analogy but also, the pick-up truck goes faster than the
> station wagon, and the station wagon faster than the kia. However, as you
> said, the driver of the pick-up may be having some bladder control issues.

No. Electrons travel down copper, and light through fiber at the same speed
whatever that copper or fiber is connected to. They don't magically go
faster because they originated or are destined for a cable subscriber. Cable
networks didn't change the laws of physics.

> . . . so, in a gaming situation, the player might hit the command 'shoot'
> but the driver is still flushing the urinal . . .

The driver of the pick-up may need to relieve his bladder as well. There
probably is a greater tendency for dial-up to have more latency because of
the way the client modem is connected to the modem rack at the ISP, but if
you have a low enough latency on that first hop, dial-up should be able to
send a shoot command as quickly as someone on an over-subscribed cable
network, or on DSL at the maximum distance from the CO (or if the DSLAM is
oversubscribed). (Unless the game designer has decided that a lot more
information needs to be up and downloaded, instead of being on the client
machine already.)

--
Warren H.

==========
Disclaimer: My views reflect those of myself, and not my
employer, my friends, nor (as she often tells me) my wife.
Any resemblance to the views of anybody living or dead is
coincidental. No animals were hurt in the writing of this
response -- unless you count my dog who desperately wants
to go outside now.

Compare and buy TaxCut and TurboTax Software:
http://www.holzemville.com/taxes/





other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map