Announcement

Collapse
No announcement yet.

Connection issues since upgrade

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Connection issues since upgrade

    I'm quite sure this has nothing to do with the update to 3.2 at all, but that's just a landmark for when I noticed the issues happenings. It's intermittent, but I only experience it on TG servers.

    I get crazy latency spikes (from 80 (normal) spiking to ~400). It happens so fast you don't even see it on the scoreboard, but my screen I slip and jerk around a lot, not sure if others notice anything other than my voice chat stuttering or whatever.

    The three traceroutes below were taken within minutes of each other: you'll notice at one point there same nasty latency, and at others, there's packet loss.

    I guess for now, i'm just checkin to see if anyone else has noticed issues. (I spent about 3 hours trying to find out what my PC might be doing to cause this[spyware/virus] before trying to test on another server, and had no issues).

    Code:
    Tracing route to ea.9d.344a.static.theplanet.com [74.52.157.234]
    over a maximum of 30 hops:
    
      1     *        *        *     Request timed out.
      2     8 ms    11 ms    10 ms  gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]
      3     8 ms     9 ms     8 ms  gw01.slnt.phub.net.cable.rogers.com [66.185.93.201]
      4    14 ms    14 ms    15 ms  gw01.lndn.phub.net.cable.rogers.com [66.185.81.81]
      5    25 ms    15 ms    18 ms  gw02.mtnk.phub.net.cable.rogers.com [66.185.80.185]
      6    18 ms    21 ms    15 ms  gw02.bloor.phub.net.cable.rogers.com [66.185.80.142]
      7    37 ms    40 ms    36 ms  igw01.ny8th.phub.net.cable.rogers.com [66.185.81.13]
      8    35 ms    38 ms    34 ms  64.71.240.18
      9    38 ms    39 ms    71 ms  v3495.mpd03.jfk02.atlas.cogentco.com [154.54.6.45]
     10    38 ms    38 ms    38 ms  t9-4.mpd01.dca01.atlas.cogentco.com [154.54.6.138]
     11    40 ms    39 ms    41 ms  v3491.mpd01.dca02.atlas.cogentco.com [154.54.2.182]
     12    39 ms    39 ms    37 ms  v3494.mpd01.iad01.atlas.cogentco.com [154.54.5.42]
     13    37 ms    45 ms    39 ms  verio.iad01.atlas.cogentco.com [154.54.10.162]
     14    62 ms    62 ms    61 ms  p64-1-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.24]
     15    94 ms   203 ms   208 ms  xe-1-1.r03.dllstx09.us.bb.gin.ntt.net [129.250.3.122]
     16    87 ms    80 ms    96 ms  xe-0.the-planet.r03.dllstx09.us.ce.gin.ntt.net [157.238.225.6]
     17    78 ms    81 ms    80 ms  te7-1.dsr02.dllstx3.theplanet.com [70.87.253.18]
     18    82 ms    79 ms    82 ms  vl21.dsr01.dllstx2.theplanet.com [70.85.127.67]
     19    87 ms    84 ms    81 ms  po1.car03.dllstx6.theplanet.com [12.96.160.5]
     20    79 ms    91 ms    98 ms  ea.9d.344a.static.theplanet.com [74.52.157.234]
    
    Trace complete.
    
    
    
    Tracing route to ea.9d.344a.static.theplanet.com [74.52.157.234]
    over a maximum of 30 hops:
    
      1     *        *        *     Request timed out.
      2    10 ms    13 ms     9 ms  gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]
      3    11 ms     7 ms    10 ms  gw01.slnt.phub.net.cable.rogers.com [66.185.93.201]
      4    15 ms    14 ms    14 ms  gw01.lndn.phub.net.cable.rogers.com [66.185.81.81]
      5    17 ms    18 ms    21 ms  gw02.mtnk.phub.net.cable.rogers.com [66.185.80.185]
      6    14 ms    26 ms    15 ms  gw02.bloor.phub.net.cable.rogers.com [66.185.80.142]
      7    37 ms    43 ms    37 ms  igw01.ny8th.phub.net.cable.rogers.com [66.185.81.13]
      8    35 ms    33 ms    34 ms  64.71.240.18
      9    37 ms    37 ms    35 ms  v3495.mpd03.jfk02.atlas.cogentco.com [154.54.6.45]
     10    39 ms    39 ms    38 ms  t9-4.mpd01.dca01.atlas.cogentco.com [154.54.6.138]
     11    38 ms    58 ms    36 ms  v3491.mpd01.dca02.atlas.cogentco.com [154.54.2.182]
     12    37 ms    37 ms    39 ms  v3494.mpd01.iad01.atlas.cogentco.com [154.54.5.42]
     13    47 ms    37 ms    35 ms  verio.iad01.atlas.cogentco.com [154.54.10.162]
     14    73 ms    61 ms    66 ms  p64-1-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.24]
     15    60 ms    71 ms    63 ms  xe-1-1.r03.dllstx09.us.bb.gin.ntt.net [129.250.3.122]
     16    80 ms    81 ms    81 ms  xe-0.the-planet.r03.dllstx09.us.ce.gin.ntt.net [157.238.225.6]
     17    78 ms    83 ms    81 ms  te7-1.dsr02.dllstx3.theplanet.com [70.87.253.18]
     18    80 ms    79 ms    96 ms  vl21.dsr01.dllstx2.theplanet.com [70.85.127.67]
     19    95 ms    87 ms    79 ms  po2.car03.dllstx6.theplanet.com [12.96.160.37]
     20    82 ms    81 ms    79 ms  ea.9d.344a.static.theplanet.com [74.52.157.234]
    
    Trace complete.
    
    
    
    
    Tracing route to ea.9d.344a.static.theplanet.com [74.52.157.234]
    over a maximum of 30 hops:
    
      1     *        *        *     Request timed out.
      2    10 ms     9 ms     9 ms  gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]
      3     8 ms     9 ms    17 ms  gw01.slnt.phub.net.cable.rogers.com [66.185.93.201]
      4    29 ms    17 ms    16 ms  gw01.lndn.phub.net.cable.rogers.com [66.185.81.81]
      5    21 ms    15 ms    24 ms  gw02.mtnk.phub.net.cable.rogers.com [66.185.80.185]
      6    16 ms    15 ms    14 ms  gw02.bloor.phub.net.cable.rogers.com [66.185.80.142]
      7    36 ms    37 ms    44 ms  igw01.ny8th.phub.net.cable.rogers.com [66.185.81.13]
      8    58 ms    53 ms    88 ms  64.71.240.18
      9    36 ms    35 ms    38 ms  v3495.mpd03.jfk02.atlas.cogentco.com [154.54.6.45]
     10    37 ms    41 ms    39 ms  t9-4.mpd01.dca01.atlas.cogentco.com [154.54.6.138]
     11    37 ms    39 ms    38 ms  v3491.mpd01.dca02.atlas.cogentco.com [154.54.2.182]
     12    38 ms    38 ms    36 ms  v3494.mpd01.iad01.atlas.cogentco.com [154.54.5.42]
     13    51 ms    40 ms    53 ms  verio.iad01.atlas.cogentco.com [154.54.10.162]
     14    62 ms    61 ms    61 ms  p64-1-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.24]
     15    61 ms    69 ms    59 ms  xe-1-1.r03.dllstx09.us.bb.gin.ntt.net [129.250.3.122]
     16    78 ms    79 ms    78 ms  xe-0.the-planet.r03.dllstx09.us.ce.gin.ntt.net [157.238.225.6]
     17    78 ms    81 ms    80 ms  te7-1.dsr02.dllstx3.theplanet.com [70.87.253.18]
     18     *       80 ms    77 ms  vl22.dsr02.dllstx2.theplanet.com [70.85.127.76]
     19    94 ms    99 ms    81 ms  po2.car03.dllstx6.theplanet.com [12.96.160.37]
     20    91 ms    78 ms    96 ms  ea.9d.344a.static.theplanet.com [74.52.157.234]
    
    Trace complete.
    sigpic

  • #2
    Re: Connection issues since upgrade

    I have the same problem from time to time. Comes and goes as it pleases, so I just take a break for an hour or so and its usually gone.

    Comment


    • #3
      Re: Connection issues since upgrade

      Yo lush, long time no see. How old is your cable\dsl modem?
      Like the server? Become a regular! TGNS Required Reading
      Answers to every server question? Yes! TGNS FAQ

      Comment


      • #4
        Re: Connection issues since upgrade

        I have no idea if this is related, but i get choke spikes on the server, from 7-30-12-7 usually. I have tried both cl_updaterate 50 + cmdrate 100 AND updaterate 50 cmdrate 50 and it doesn't seem to fix it. It usually happens when more things are happening in/on/around the screen. Whats weird is it is only on tg. On Addiction ANSL Server #2 I do not get this choke with any of those rates above. Weirder than I am pretty sure choke is client side. I am gonna test on multiple other servers to confirm but I am pretty sure its a tg server thing.


        And finally, could any of this possible be due to running two software servers on one machine? Even if it is dual core...?

        Comment


        • #5
          Re: Connection issues since upgrade

          Originally posted by micr0c0sm View Post
          And finally, could any of this possible be due to running two software servers on one machine? Even if it is dual core...?
          On another box, yes. Not on our box, no.

          There's one very simple way to tell when a problem is the server, and these moments are very, very rare on TGNS: every single player is affected by whatever the "bad" behavior is.

          The server doesn't pick and choose its victims. If the box is suffering, everyone will feel it, pretty much equally (even if not concurrently, though that's usually the case).

          I was fooled, one night, into looking at server performance to explain high pings across the board. Turns out two player's (out of 16) pings were fine. Amazingly, 14 of us were going through the same network bottleneck that those other two players weren't. It wasn't the box at all.

          If it's the box, everyone will feel it.
          Steam Community? Add me. | Free Remote, Encrypted Backup

          Darkilla: In short, NS is pretty much really fast chess. With guns. Apophis: I haven't seen anyone say that SM's are better than non-SMs. Nordbomber: This is THE first server I've seen where either side can comeback from out of seemingly nowhere with the right teamwork. en4rcment: I have NEVER experienced the type of gameplay that I have found here. Nightly I am amazed at the personalities and gaming talent. Zephyr: Apophis is clearly a highly sophisticated self-aware AI construct that runs on a highly modified toaster oven in Wyzcrak's basement.

          Comment


          • #6
            Re: Connection issues since upgrade

            Originally posted by Wyzcrak View Post
            If it's the box, everyone will feel it.


            If it's the box, everyone will feel it?



            I'm surprised Wyz didn't mention pingplotter. He seems to drag that out everytime someone complains about their connexxion. And not for bad reasons, either. Anyway - I've upstaged tehWyz and mentioned it myselfs.
            Former TGNS admin until WoW blinded me with flashy lights.

            Comment


            • #7
              Re: Connection issues since upgrade

              heres my results from PP
              Code:
              Target Name: TGNS.TACTICALGAMER.COM
                       IP: 74.52.157.234
                Date/Time: 3/21/2007 7:43:54 PM to 3/21/2007 7:45:40 PM
              
              Hop Sent Err  PL% Min Max Avg  Host Name / [IP]
               1   126   1  0.8   1   6   1  [192.168.1.1]
               2     0   0  0.0   0   0   0   []
               3   126   0  0.0   7  29   9  gig5-0-0.orldflwrpk-rtr1.cfl.rr.com [24.95.228.81]
               4   126  20 15.9   7 194  12  145.228.95.24.cfl.res.rr.com [24.95.228.145]
               5   126  10  7.9   7 194  18  te-3-3.car1.Orlando1.Level3.net [4.79.116.145]
               6   126   0  0.0   8 237  19  ae-11-11.car2.Orlando1.Level3.net [4.69.133.74]
               7   126   1  0.8  41  83  49  ae-9-9.ebr1.Dallas1.Level3.net [4.69.133.70]
               8   124  52 41.9  42 232  53  ae-14-51.car4.Dallas1.Level3.net [4.68.122.16]
               9   126  17 13.5  42  74  46  THE-PLANET.car4.Dallas1.Level3.net [4.71.122.2]
              10    42  13 31.0  42  71  46  te7-2.dsr02.dllstx3.theplanet.com [70.87.253.26]
              11    88  34 38.6  41 128  48  vl21.dsr01.dllstx2.theplanet.com [70.85.127.67]
              12    43  17 39.5  43  65  47  po2.car03.dllstx6.theplanet.com [12.96.160.37]
              13   126  23 18.3  41  59  44  ea.9d.344a.static.theplanet.com [74.52.157.234]
              Call me crazy, but the 30+ percent packet loss numbers in dallas look like they might be the culprit.

              Comment


              • #8
                Re: Connection issues since upgrade

                trace as per ping plotter -- man, actually, it's quite nice for this stuff!

                Code:
                Target Name: ea.9d.344a.static.theplanet.com
                         IP: 74.52.157.234
                  Date/Time: 3/21/2007 8:03:04 PM to 3/21/2007 8:03:55 PM
                
                Hop Sent Err PL% Min  Max Avg  Host Name / [IP]
                 2    50   0 0.0   7   71  11  gw03.slnt.phub.net.cable.rogers.com [66.185.90.145]
                 3    50   0 0.0   8   20  10  gw01.slnt.phub.net.cable.rogers.com [66.185.93.201]
                 4    50   0 0.0  13   40  16  gw01.strfrd.phub.net.cable.rogers.com [66.185.81.77]
                 5    50   0 0.0  13   34  17  gw02.mtnk.phub.net.cable.rogers.com [66.185.80.170]
                 6    50   0 0.0  13   26  16  [64.71.240.110]
                 7    50   0 0.0  35   53  38  igw01.ny8th.phub.net.cable.rogers.com [66.185.81.13]
                 8    50   0 0.0  32   48  35  [64.71.240.18]
                 9    50   0 0.0  36  150  40  v3495.mpd03.jfk02.atlas.cogentco.com [154.54.6.45]
                10    50   0 0.0  37  236  49  t7-1.mpd01.dca01.atlas.cogentco.com [154.54.5.246]
                11    50   0 0.0  36  165  44  v3491.mpd01.dca02.atlas.cogentco.com [154.54.2.182]
                12    50   0 0.0  36  147  42  v3494.mpd01.iad01.atlas.cogentco.com [154.54.5.42]
                13    50   0 0.0  36   50  40  verio.iad01.atlas.cogentco.com [154.54.10.162]
                14    50   2 4.0  59 1116  87  p64-1-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.250.5.24]
                15    50   2 4.0  60  258  81  xe-1-1.r03.dllstx09.us.bb.gin.ntt.net [129.250.3.122]
                16    50   0 0.0  78 1121 101  xe-4-4.r03.dllstx09.us.ce.gin.ntt.net [157.238.225.6]
                17     9   0 0.0  79  243 109  te9-1.dsr02.dllstx3.theplanet.com [70.87.253.22]
                18    25   1 4.0  79  277  90  vl22.dsr02.dllstx2.theplanet.com [70.85.127.76]
                19    26   0 0.0  79  483 132  po1.car03.dllstx6.theplanet.com [12.96.160.5]
                20    50   0 0.0  78  926  97  ea.9d.344a.static.theplanet.com [74.52.157.234]
                sigpic

                Comment

                Connect

                Collapse

                TeamSpeak 3 Server

                Collapse

                Advertisement

                Collapse

                Twitter Feed

                Collapse

                Working...
                X