View Full Version : Help for a Blonde
Very informative Web site and the forums\threads I visit here have taught me many things.
1)Tweaking for High Speed can definetly be "Plug and Pray"
2)ALWAYS...back up registry
3)People working together CAN squeeze things out of the BIG GUYS...."Need for Speed"
4)On some subjects NOBODY has the exact answer....trial and error.
Having said all of that....can I ask someone to Please take a look at what follows and give me some answers.....not withstanding the time of day, my OS, cleaness of my system, ISP (RR..Memphis Tn.)...etc
1)Good\Bad....packets
2)Too many\Pretty good....Hops
3)Andddddd....the dreadful MTU\MSS\RWIN numbers I should use....Me and my math aren't playing together well.
Thanks in advance to ALL...both knowlegable and less knowledgeable like me for the Good and Bad questions.....makes ME think.
OZ
Guess it must be early or not enough Java
C:\WINDOWS>ping -f -n 10 -l 1472 24.24.107.1
Pinging 24.24.107.1 with 1472 bytes of data:
Reply from 24.24.107.1: bytes=1472 time=72ms TTL=19
Reply from 24.24.107.1: bytes=1472 time=42ms TTL=19
Reply from 24.24.107.1: bytes=1472 time=42ms TTL=19
Reply from 24.24.107.1: bytes=1472 time=42ms TTL=19
Reply from 24.24.107.1: bytes=1472 time=43ms TTL=19
Reply from 24.24.107.1: bytes=1472 time=42ms TTL=19
Reply from 24.24.107.1: bytes=1472 time=41ms TTL=19
Reply from 24.24.107.1: bytes=1472 time=40ms TTL=19
Reply from 24.24.107.1: bytes=1472 time=39ms TTL=19
Reply from 24.24.107.1: bytes=1472 time=61ms TTL=19
Ping statistics for 24.24.107.1:
Packets: Sent = 10, Received = 10, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 72ms, Average = 46ms
1 28 ms 19 ms 18 ms m4hMs6n1.midsouth.rr.com [24.24.107.1]
2 12 ms 6 ms 6 ms 7507ms-fe100.midsouth.rr.com [24.92.65.165]
3 28 ms 7 ms 7 ms tu-gsr02-pos02.midsouth.rr.com [24.92.65.114]
4 14 ms 6 ms 6 ms ab-gsr02-pos20.midsouth.rr.com [24.92.65.9]
5 13 ms 6 ms 6 ms 7507b-pos000.midsouth.rr.com [24.92.65.42]
6 27 ms 18 ms 15 ms 12.126.90.177
7 20 ms 17 ms 21 ms gbr2-a80s11.sl9mo.ip.att.net [12.123.24.50]
8 32 ms 15 ms 14 ms gbr4-p70.sl9mo.ip.att.net [12.122.1.213]
9 33 ms 21 ms 23 ms gbr3-p40.cgcil.ip.att.net [12.122.2.205]
10 25 ms 23 ms 19 ms ggr1-p360.cgcil.ip.att.net [12.123.5.145]
11 31 ms 27 ms 26 ms 46.ATM2-0.BR1.CHI2.ALTER.NET [137.39.23.229]
12 25 ms 23 ms 23 ms 164.at-6-0-0.XR1.CHI2.ALTER.NET [152.63.64.118]
13 32 ms 27 ms 24 ms 293.ATM3-0.TR1.CHI4.ALTER.NET [152.63.64.222]
14 48 ms 45 ms 45 ms 106.at-6-1-0.TR1.DCA6.ALTER.NET [146.188.142.42]
15 97 ms 51 ms 50 ms 287.at-5-0-0.XR1.TCO1.ALTER.NET [152.63.34.21]
16 49 ms 50 ms 52 ms 193.ATM7-0.GW9.TCO1.ALTER.NET [152.63.38.13]
17 56 ms 52 ms 51 ms verio-gw.customer.alter.net [157.130.49.214]
18 55 ms 50 ms 52 ms ge0031.ed1.wdc.dn.net [216.167.88.116]
19 55 ms 52 ms 55 ms www.speedguide.net (http://www.speedguide.net) [216.167.23.73]
Trace complete.
Kip Patterson
12-08-00, 10:22 AM
That is a lot of hops to get from Memphis to Virginia, but the latency/ping time looks pretty good. The path must be about 1000 miles or 15 milliseconds, so you are getting through the queues of 18 routers in 40 ms, not bad.
Apparently there is no eastbound route out of memphis through the RR network. I'm on RR, and when I ping your default gateway from Columbus it goes through the same route.
Powered by vBulletin® Version 4.2.0 Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.