Pinging Armagoshdarn II

Lackadaisical · Post by **Lackadaisical** » Tue Mar 23, 2004 10:52 pm

Hey,

Lately I've been getting a huge ping (800+) on goshdarn, this doesnt happen on other servers, just on goshdarn... Anybody knows what could be the problem? / how to solve it? darnish 2.6 is too easy

Lack

n54 · Post by **n54** » Wed Mar 24, 2004 2:17 am

ignore ping from armagoshdarn, the server has a permanent ailment

(my ping is always 180 but that's seldom what's shown)

locutus · Post by **locutus** » Wed Mar 24, 2004 5:22 am

mine shows as 12 which I know is impossible, darn is unplayable for me these days and no one seems to be there to administrate it, look for me on any other server till the situation changes

subby · Post by **subby** » Wed Mar 24, 2004 6:08 am

Like most things, if you live away from the usa, your latency will be crap, and you have to learn how to predict in the brain what will happen and not trust that diamond thingy. Are you trusting that diamond ? If so you will be cutting it very tight, especially with the current state of gosh's reporting of pings.

Im sure Bm, node etc would agree ?

locutus · Post by **locutus** » Wed Mar 24, 2004 8:43 am

well I live in Albuquerque, New Mexico, USA and it is still all screwed up for me, u cannot predict what you cant see till 20 secs after it's happened. I have been in the open and then died from a box I never saw, I have seen walls dissappear and reappear, I have seen bikes go thorugh walls and keep playing.

This aint your normal laggy state of affairs, something in the line or on the server it technically screwed up. The only ppl that seem to be able to deal with it well are those with normal ping readings, everyone else with impossible ping readings is complaining.

normally I can predict with a heavy amount of lag, belive me, I started on 56k and got pretty good trying to out-guess people as it was necessary, darn is not like this, somethings wrong, very wrong

come to ish or 3d2 and see how i can play without that stuff happening to me..

n54 · Post by **n54** » Wed Mar 24, 2004 10:00 am

btw on the ping issue:

some ppl keep insisting that what i'm saying is all wrong, if they want to they are welcome to prove me wrong but i'm not accepting stuff that isn't backed up by hard facts (ie. links and solid reasoning). they can claim mcse, ccna or whatnot - it doesn't matter (4 years ago i briefly teached some networking mcp's and ccna so don't believe me to be easily impressed - most ppl with those certifications don't have a clue)

0ms is only possible for a player sitting at a non-dedicated server and playing
18 to 25ms+ is otherwise the lowest pings possible technically when connecting to a server to play (if you're playing on a very nice lan you might see values like this)
50ms+ would be a more normal "low" ping for internet play where you're close to the server in the internet topology
most internet routers use at least 5-10ms routing you a hop closer to your destination on long stretches but on short stretches this can be down to 1-2ms
50 to 150ms+ is normal ping which most netenabled games should be able to handle with absolutely no lag imo

my armagoshdarn ping still has an average of 180ms (15 hops to a server in california), as a comparison when i ping guru3.sytes.net i have an average of 78ms (21 hops to a server in sweden) - i'm located in oslo norway btw (if somebody didn't know)

ping difference and the neccessary mental calculation of where players are as opposed to where they seem to be is fairly steady and most advanced players (like for example Communist etc.) do this almost instinctively - sure it's because of latency but it's not the erratic unpredictable stuff which makes players cry out lag (or not cry out for that matter).

simple truth is that armagoshdarn is actually a shitty server except for the brilliant setup - it's enjoyable though, and probably the most challenging server around

Lackadaisical · Post by **Lackadaisical** » Wed Mar 24, 2004 1:02 pm

well.. I've tried pinging to the server via dos, and the results were:

Code: Select all

Pingen naar armagetron.mars.org [209.126.142.251] met 32 byte gegevens:

Antwoord van 209.126.142.251: bytes=32 time=488ms TTL=241
Antwoord van 209.126.142.251: bytes=32 time=491ms TTL=241
Antwoord van 209.126.142.251: bytes=32 time=520ms TTL=241
Antwoord van 209.126.142.251: bytes=32 time=483ms TTL=241

Pingstatistieken voor 209.126.142.251:
    Packets: verzonden = 4, ontvangen = 4, kwijtgeraakt = 0 (0% verlies),
Retourtijd bij benadering in milliseconden:
    Minimum = 483ms, Maximum =  520ms, Gemiddeld =  495ms

And then I did a tracert like n54 did here

Code: Select all

C:\>tracert armagetron.mars.org

Bezig met tracen van route naar armagetron.mars.org [209.126.142.251]
voor maximaal 30 hops:

  1     2 ms     2 ms     2 ms  ...
  2    13 ms    13 ms    14 ms  ...
  3    22 ms    16 ms    16 ms  ...
  4    16 ms    15 ms    15 ms  iawxsrt-m6-bb14a.wxs.nl [195.121.0.149]
  5    15 ms    15 ms    15 ms  asd-sara-ias-ur10.nl.kpn.net [195.121.253.2]
  6    15 ms    14 ms    36 ms  asd-dc2-ias-ur10.nl.kpn.net [195.190.227.7]
  7    22 ms    23 ms    22 ms  ldn-kq-ias-pr10.uk.kpn.net [194.151.244.192]
  8   414 ms   418 ms   416 ms  lndnuk1icx1.wcg.net [195.66.224.105]
  9   481 ms   490 ms   487 ms  nycmny2wcx2-pos15-3.wcg.net [64.200.87.61]
 10   487 ms   485 ms   484 ms  hrndva1wcx2-pos5-0.wcg.net [64.200.210.97]
 11   540 ms   545 ms     *     anhmca1wcx3-oc48.wcg.net [64.200.240.29]
 12   529 ms   524 ms   528 ms  sndgca1wce2-pos3-0.wcg.net [64.200.141.18]
 13   538 ms   539 ms   533 ms  sndgca1wce1-calfregional-gige.wcg.net [65.77.90
42]
 14   537 ms   536 ms   538 ms  armagetron.mars.org [209.126.142.251]

Trace voltooid.

well, its in dutch, but as you can see there seems to be a problem at #8? Is there something I could do about it? like.. connecting to armagoshdarn via another way?
[/url]

n54 · Post by **n54** » Wed Mar 24, 2004 8:00 pm

here's my results:

Code: Select all

#:\#\#>tracert armagetron.mars.org

Tracing route to armagetron.mars.org [209.126.142.251]
over a maximum of 30 hops:

  1   <10 ms   <10 ms   <10 ms  #####
  2    16 ms    16 ms    15 ms  #####
  3    15 ms    16 ms    15 ms  #####
  4    15 ms    16 ms    15 ms  #####
  5    15 ms    16 ms    16 ms  #####
  6    31 ms    16 ms    31 ms  ge0-3-0-103.ar1.OSL1.gblx.net [208.51.41.57]
  7    31 ms    31 ms    32 ms  pos12-0-2488M.cr2.HAM1.gblx.net [67.17.74.185]
  8   125 ms   141 ms   125 ms  pos3-3-2488M.cr1.WDC2.gblx.net [67.17.74.70]
  9   140 ms   141 ms   125 ms  so7-1-0-2488M.ar1.DCA3.gblx.net [67.17.74.145]
 10   141 ms   125 ms   140 ms  208.51.74.6
 11   140 ms   125 ms   141 ms  hrndva1wcx2-pos0-0.wcg.net [64.200.89.49]
 12   188 ms   203 ms   187 ms  anhmca1wcx3-oc48.wcg.net [64.200.240.29]
 13   187 ms   203 ms   188 ms  sndgca1wce2-pos3-0.wcg.net [64.200.141.18]
 14   204 ms   187 ms   188 ms  sndgca1wce1-calfregional-gige.wcg.net [65.77.90.
42]
 15   203 ms   188 ms   187 ms  surveyor.mars.org [209.126.142.251]

Trace complete.

just to show my tracert again, for comparison...

i guess you could edit your lmhosts file or similar but i'm not sure it's such a good idea (ie. use a different (internet) gateway than the one you're currently using) the path onwards is chosen on routing metrics and is always optimized within some limitations. which gateway to alternatively use is a hard question for me to answer as i have no idea on which dutch/european isps are available for you (or if any of them would give a better result)

Prey4Me · Post by **Prey4Me** » Thu Mar 25, 2004 9:19 am

wow this is really technical talk and technical looking
im just glad im one of those ppl where the goshdarn problems only affect me occassionally and usually aren't that bad

Lackadaisical · Post by **Lackadaisical** » Thu Mar 25, 2004 2:10 pm

Thanks for the advice everybody, but strangely enough it seems that it has cured itself.

Marrow · Post by **Marrow** » Sat Mar 27, 2004 2:45 am

Here are my stats:

68-65-9-5# traceroute armagetron.mars.org
traceroute to armagetron.mars.org (209.126.142.251), 64 hops max, 40 byte packets
1 68.65.8.1 (68.65.8.1) 22.240 ms 16.769 ms 38.231 ms
2 67.21.129.201 (67.21.129.201) 18.745 ms 18.231 ms 14.702 ms
3 68.65.14.149 (68.65.14.149) 19.863 ms 25.336 ms 14.648 ms
4 68.65.14.145 (68.65.14.145) 18.382 ms 17.787 ms 18.068 ms
5 g4-2.lasalle6509.buf.adelphia.net (68.65.14.65) 20.620 ms 18.072 ms 27.842 ms
6 68.168.225.1 (68.168.225.1) 18.863 ms 16.436 ms 19.242 ms
7 g1-03-02-00.a0.buf00.adelphiacom.net (66.109.14.41) 17.869 ms 24.063 ms 18.966 ms
8 g1-02-00-00.r0.buf00.adelphiacom.net (66.109.1.37) 19.208 ms g1-03-00-00.r0.buf00.adelphiacom.net (66.1 09.1.33) 19.069 ms g1-02-00-00.r0.buf00.adelphiacom.net (66.109.1.37) 19.906 ms
9 p3-01-01-00.n0.chi75.adelphiacom.net (66.109.0.217) 37.656 ms 32.192 ms 31.514 ms
10 p3-01-02-00.n0.dfw91.adelphiacom.net (66.109.0.66) 56.346 ms 58.638 ms 55.134 ms
11 p3-00-00-00.r0.dfw91.adelphiacom.net (66.109.0.146) 57.883 ms 58.463 ms 58.133 ms
12 g1-02-03-00.p0.dfw91.adelphiacom.net (66.109.3.74) 56.440 ms 53.713 ms 54.772 ms
13 g1-00-01-00.a0.sea00.adelphiacom.net (66.109.13.130) 55.923 ms 55.082 ms 53.303 ms
14 dllstx1wcx2-oc48.wcg.net (64.200.110.81) 49.471 ms 58.367 ms 55.702 ms
15 anhmca1wcx2-pos11-0-oc48.wcg.net (64.200.240.6) 106.787 ms 97.970 ms 99.523 ms
16 anhmca1wcx3-pos10-0.wcg.net (64.200.141.66) 85.962 ms 78.853 ms 88.959 ms
17 sndgca1wce2-pos3-0.wcg.net (64.200.141.18) 96.807 ms 99.185 ms 100.453 ms
18 sndgca1wce1-calfregional-gige.wcg.net (65.77.90.42) 97.427 ms 104.406 ms 102.981 ms
19 surveyor.mars.org (209.126.142.251) 91.311 ms 98.645 ms 98.591 ms

68-65-9-5# ping armagetron.mars.org
PING armagetron.mars.org (209.126.142.251): 56 data bytes
64 bytes from 209.126.142.251: icmp_seq=0 ttl=237 time=100.235 ms
64 bytes from 209.126.142.251: icmp_seq=1 ttl=237 time=92.564 ms
64 bytes from 209.126.142.251: icmp_seq=2 ttl=237 time=92.326 ms
64 bytes from 209.126.142.251: icmp_seq=3 ttl=237 time=91.821 ms
64 bytes from 209.126.142.251: icmp_seq=4 ttl=237 time=92.107 ms
64 bytes from 209.126.142.251: icmp_seq=5 ttl=237 time=98.312 ms
64 bytes from 209.126.142.251: icmp_seq=6 ttl=237 time=95.480 ms
64 bytes from 209.126.142.251: icmp_seq=7 ttl=237 time=92.872 ms
64 bytes from 209.126.142.251: icmp_seq=8 ttl=237 time=104.880 ms
64 bytes from 209.126.142.251: icmp_seq=9 ttl=237 time=91.946 ms
^C
--- armagetron.mars.org ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 91.821/95.254/104.880/4.254 ms
68-65-9-5#

Majination · Post by **Majination** » Sat Mar 27, 2004 3:05 am

Because it has become the trendy thing to do, here are my quite nice statistics.

Wipe your chin. Stop that slobberin.

Code: Select all

Tracing route to armagetron.mars.org [209.126.142.251]
over a maximum of 30 hops:

  1    10 ms    10 ms    20 ms  adsl-67-121-225-254.dsl.chic01.pacbell.net [67.121.225.254]
  2    20 ms    10 ms    10 ms  dist2-vlan60.chic01.pbi.net [216.102.186.199]
  3    10 ms    10 ms    10 ms  bb1-g2-0.chic01.pbi.net [63.200.183.19]
  4    20 ms    20 ms    20 ms  bb1-p3-2.sntc01.pbi.net [63.200.183.38]
  5    20 ms    20 ms    20 ms  bb2-p12-0.sntc01.pbi.net [64.161.1.26]
  6    20 ms    20 ms    20 ms  ex1-p12-0.eqsjca.sbcglobal.net [64.161.1.38]
  7    20 ms    20 ms    20 ms  151.164.248.26
  8    20 ms    20 ms    20 ms  sntcca1wcx1-pos2-1.wcg.net [64.200.149.45]
  9    30 ms    40 ms    30 ms  anhmca1wcx3-pos3-0-oc192.wcg.net [64.200.240.109]
 10    30 ms    30 ms    40 ms  sndgca1wce2-pos3-0.wcg.net [64.200.141.18]
 11    30 ms    30 ms    30 ms  sndgca1wce1-calfregional-gige.wcg.net [65.77.90.42]
 12    31 ms    40 ms    30 ms  surveyor.mars.org [209.126.142.251]

Trace complete.

Code: Select all

Pinging armagetron.mars.org [209.126.142.251] with 32 bytes of data:

Reply from 209.126.142.251: bytes=32 time=30ms TTL=241
Reply from 209.126.142.251: bytes=32 time=40ms TTL=241
Reply from 209.126.142.251: bytes=32 time=30ms TTL=241
Reply from 209.126.142.251: bytes=32 time=30ms TTL=241

Ping statistics for 209.126.142.251:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum =  40ms, Average =  32ms

Marrow · Post by **Marrow** » Sat Mar 27, 2004 3:09 am

omg, is the server down the road or something? lol

Majination · Post by **Majination** » Sat Mar 27, 2004 3:24 am

Heh. Apparently they are in San Diego, as their domain contact information all points to that location. I'm in Northern California, about a 12 hour drive away. Luckily my packets don't drive the 'ol paved highway.

Post by **Tank Program** » Sat Mar 27, 2004 10:39 am

Wow, that is really good maj.