50
-
-
ICMP responses can get queued giving the appearence of net latency. Download a file or pull up web pages to test speed.Originally posted by AndrewKanuck
Traceroutes != speeds
Don't look here for the joke. It's in your pants.
South O - World Class surfer destination since 2001.Comment
-
I think you meant when tracerouting - but whatever - no I wouldn't take that as an issue, as I know carriers will asign a very low priority to non-essential packets (ie. ICMP). The star will represent a single packet timed out, which is quite possible consdering the numerous factors. You want to run a true test on packet delivery? Do an extended ping - I just ran one for a few minutes:Originally posted by cocky
So educate me Andrew. When pinging verio you wouldn't see line 12 as a problem.
tracing path from www.net.princeton.edu to 192.217.194.37 ...
traceroute to 192.217.194.37 (192.217.194.37), 30 hops max, 40 byte packets
1 gigagate1 (128.112.128.114) 0.462 ms 0.305 ms 0.290 ms
2 vgate1 (128.112.12.22) 0.353 ms 0.324 ms 0.318 ms
3 209.92.72.201 (209.92.72.201) 11.955 ms 9.735 ms 9.972 ms
4 165.113.8.66 (165.113.8.66) 19.277 ms 11.378 ms 10.214 ms
5 4.78.164.9 (4.78.164.9) 10.671 ms 7.740 ms 7.356 ms
6 ge-6-0-0.mp1.Philadelphia1.Level3.net (64.159.0.145) 5.308 ms 8.700 ms 9.818 ms
7 so-6-1-0.bbr2.NewYork1.Level3.net (209.247.8.66) 10.213 ms so-0-1-0.bbr1.NewYork1.Level3.net (64.159.1.41) 11.511 ms so-6-1-0.bbr2.NewYork1.Level3.net (209.247.8.66) 15.479 ms
8 ge-2-0.core2.NewYork1.Level3.net (4.68.97.9) 15.005 ms ge-5-2.core2.NewYork1.Level3.net (4.68.97.169) 11.191 ms ge-2-0.core2.NewYork1.Level3.net (4.68.97.9) 10.416 ms
9 oc12.Level3.nycmny01.us.bb.verio.net (209.244.160.150) 9.159 ms 15.552 ms 8.783 ms
10 p16-1-1-0.r20.nycmny01.us.bb.verio.net (129.250.2.36) 13.209 ms 10.889 ms 13.087 ms
11 p16-0-1-1.r20.mlpsca01.us.bb.verio.net (129.250.5.112) 98.321 ms 109.663 ms 106.321 ms
12 mg-1.a00.mlpsca01.us.da.verio.net (129.250.24.194) 99.883 ms * 79.424 ms
13 192.217.198.37 (192.217.198.37) 84.726 ms 82.892 ms 80.693 ms
Ping statistics for 168.143.187.47:
Packets: Sent = 143, Received = 143, Lost = 0 (0% loss),
0% packet loss here, nothing to complain about on 0% packet loss.
Comment
-
You're telling that to the wrong person fucktardOriginally posted by Ad3pt
ICMP responses can get queued giving the appearence of net latency. Download a file or pull up web pages to test speed.Comment
-
But it only happens every 1 out of 3. If it a priority issue should you notice some latency on that hop each time?Originally posted by AndrewKanuck
I think you meant when tracerouting - but whatever - no I wouldn't take that as an issue, as I know carriers will asign a very low priority to non-essential packets (ie. ICMP). The star will represent a single packet timed out, which is quite possible consdering the numerous factors. You want to run a true test on packet delivery? Do an extended ping - I just ran one for a few minutes:
Ping statistics for 168.143.187.47:
Packets: Sent = 143, Received = 143, Lost = 0 (0% loss),
0% packet loss here, nothing to complain about on 0% packet loss.Comment
-
Dooood - seriously, pick up a fucking book - I ain't tech support for your ass.Originally posted by cocky
But it only happens every 1 out of 3. If it a priority issue should you notice some latency on that hop each time?
The priority is based on the amount of incoming packets at that time, and the current queue. If you can't already fucking tell, packet counts change every second. Christ you people drive me nutsComment
-
Originally posted by korzon
i love your sig Rich
Comment
Comment