Announcement

Collapse
No announcement yet.

Read this if you've been lagging out

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

  • Read this if you've been lagging out

    So wyz suggested that we try to figure out where this problem has been occuring, as a number of us seem to be experiencing frequent lag-outs. If we all trace the route we're using to reach TG, we might be able to find the common link. Not sure what we do at that point, but at least we'll know something. So if you've been lagging out for upwards of 10 seconds at a time, please post your results in this forum so we can try to find the common link. The first one in the shared path of the people with problems should be the culprit. To find this info, use 'tracert tgns.tacticalgamer.com'. I find that the easiest way is to pipe the output into a text file rather than into stdout, which you do with "tracert tgns.tacticalgamer.com >> test" where test is whatever file name you care to use. Then, open the file, and copy and paste the results here. For a better chance of finding this specific problem, please ONLY do this if you've lagged out for more than 10 seconds at least twice in the last few weeks. Don't post your info because "OMGZ my sh0tz never r3g!!!" or whatever. Incidentally, I blame Al Gore.

    1 <1 ms <1 ms <1 ms 192.168.0.1

    2 11 ms 10 ms 10 ms adsl-75-5-15-254.dsl.irvnca.sbcglobal.net [75.5.15.254]

    3 10 ms 10 ms 10 ms dist4-vlan50.irvnca.sbcglobal.net [67.114.50.2]

    4 11 ms 10 ms 10 ms bb2-g4-0.irvnca.sbcglobal.net [151.164.43.143]

    5 11 ms 11 ms 11 ms core2-p6-0.crrvca.sbcglobal.net [151.164.43.227]

    6 12 ms 11 ms 11 ms bb1-p1-0.crrvca.sbcglobal.net [151.164.40.254]

    7 13 ms 13 ms 13 ms ex2-p8-0.eqlaca.sbcglobal.net [151.164.41.33]

    8 13 ms 13 ms 13 ms asn3549-glbx.eqlaca.sbcglobal.net [151.164.248.106]

    9 49 ms 56 ms 49 ms so1-3-0-2488M.ar1.DAL2.gblx.net [67.17.79.185]

    10 48 ms 48 ms 49 ms The-Planet.ge-4-3-0.ar1.DAL2.gblx.net [64.210.104.58]

    11 94 ms 49 ms 150 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

    12 49 ms 49 ms 50 ms vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]

    13 49 ms 49 ms 49 ms gi1-0-1.car07.dllstx4.theplanet.com [67.19.255.26]

    14 51 ms 53 ms 52 ms aa.5a.1343.static.theplanet.com [67.19.90.170]

  • #2
    Re: Read this if you've been lagging out

    I'd love to help, but when I try to tracert while I'm experiencing problems, it doesn't even give me my first IP.
    Last edited by Slayer of Hippies; 06-02-2006, 11:02 PM.

    Comment


    • #3
      Re: Read this if you've been lagging out

      You don't necessarily need to do it while the problem is occuring, most of the path seems to be the same or very similar when I try at different times, what we're looking for here is a correlation between the people experiencing these problems, not just trying to catch the problem as it happens, which would be much more difficult.

      Comment


      • #4
        Re: Read this if you've been lagging out

        Ag, could you edit that first post to include line breaks? Break the message into multiple paragraphs?
        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


        • #5
          Re: Read this if you've been lagging out

          Dark -
          Tracing route to tgns.tacticalgamer.com [67.19.90.170]
          over a maximum of 30 hops:

          1 1 ms <1 ms <1 ms aa.5a.1343.static.theplanet.com [67.19.90.170]

          2 27 ms 17 ms 18 ms 10.66.224.1

          3 15 ms 11 ms 17 ms d226-8-209.home.cgocable.net [24.226.8.209]

          4 40 ms 14 ms 22 ms cgowave-0-121.cgocable.net [24.226.0.121]

          5 34 ms 21 ms 26 ms qix-tor-gw.peer1.net [69.28.230.245]

          6 14 ms 14 ms 34 ms OC48POS1-0.tor-core-1.peer1.net [216.187.114.133]

          7 51 ms 25 ms 25 ms OC48POS0-0.chi-dis-1.peer1.net [216.187.114.141]

          8 37 ms 39 ms 43 ms ge-4-1-0.mpr1.ord7.us.mfnx.net [206.223.119.86]

          9 36 ms 36 ms 27 ms so-1-0-0.cr2.ord2.us.above.net [64.125.30.142]

          10 53 ms 67 ms 57 ms so-5-1-0.cr2.dfw2.us.above.net [64.125.29.5]

          11 60 ms 51 ms 54 ms 216.200.6.237.theplanet.com [216.200.6.237]

          12 76 ms 58 ms 59 ms vl32.dsr01.dllstx3.theplanet.com [70.85.127.61]

          13 50 ms 63 ms 51 ms vl41.dsr01.dllstx4.theplanet.com [70.85.127.83]

          14 62 ms 60 ms 60 ms gi1-0-1.car07.dllstx4.theplanet.com [67.19.255.26]

          15 100 ms 63 ms 67 ms aa.5a.1343.static.theplanet.com [67.19.90.170]
          Trace complet
          Seems to me i'm good until after I get off the OC-48 trunk outa toronto... (i live just outside toronto btw)
          Ambriento for comm! Vote today!

          Comment


          • #6
            Re: Read this if you've been lagging out

            Code:
            Tracing route to tgns.tacticalgamer.com [67.19.90.170]
            over a maximum of 30 hops
              1     1 ms    <1 ms    <1 ms  192.168.2.1 
              2     9 ms    10 ms     7 ms  73.166.80.1 
              3     8 ms    10 ms     *     ge-1-40-ur02.derry.nh.boston.comcast.net [68.87.151.221] 
              4     *        9 ms     *     10g-9-3-ur01.lawrence.ma.boston.comcast.net [68.87.144.149] 
              5    11 ms     *        9 ms  10g-9-1-ur02.lawrence.ma.boston.comcast.net [68.87.144.141] 
              6    10 ms     *       13 ms  10g-7-1-ar01.woburn.ma.boston.comcast.net [68.87.144.137] 
              7    10 ms    10 ms     9 ms  te-4-1-cr01.boston.ma.cbone.comcast.net [68.86.72.25] 
              8    11 ms    11 ms    11 ms  te-0-4-0-4-cr01.boston.ma.ibone.comcast.net [68.86.88.13] 
              9    17 ms    17 ms    18 ms  te-0-4-0-4-cr01.newyork.ny.ibone.comcast.net [68.86.88.9] 
             10    16 ms    16 ms    15 ms  64.215.24.85 
             11    68 ms    68 ms    68 ms  so1-3-0-2488M.ar1.DAL2.gblx.net [67.17.79.185] 
             12    60 ms    60 ms    60 ms  The-Planet.ge-4-3-0.ar1.DAL2.gblx.net [64.210.104.58] 
             13    64 ms    60 ms    62 ms  vl31.dsr01.dllstx3.theplanet.com [70.85.127.29] 
             14    59 ms    60 ms    60 ms  vl41.dsr01.dllstx4.theplanet.com [70.85.127.83] 
             15    61 ms    60 ms    61 ms  gi1-0-2.car07.dllstx4.theplanet.com [67.19.255.154] 
             16    62 ms    62 ms    61 ms  aa.5a.1343.static.theplanet.com [67.19.90.170] 
            Trace complete.
            Lag every few minutes. Timeouts, 4000+ lagspikes
            birdie_in_Texas:ok..i feel stupid here..what is "NS"..? Wyzcrak:Natural Selection. Don't feel at a loss for not knowing the acronym. Feel at a loss for not having experienced the game.

            Comment


            • #7
              Re: Read this if you've been lagging out

              I ran a traceroute by both the HLSW and the command in the command prompt.
              HLSW gave me a much more intresting result.


              As you can see there is a lot of black near the end, and the key says this is a differnt route.
              This is not good, as i ran it for only about 2 minutes, as i looked for the active screen, screen shot key. One of these shows around 40 or so changes. That can not be good for the connection and must be the source of the lag.

              The first one on the route is the computer my dad is using as a firewall.

              Here the windows traceroute.

              Tracing route to tgns.tacticalgamer.com [67.19.90.170]

              over a maximum of 30 hops:



              1 <1 ms <1 ms <1 ms gate.dslutz.ne.client2.attbi.com [10.2.1.1]

              2 6 ms 7 ms 7 ms 73.171.64.1

              3 7 ms 9 ms * ge-1-42-ur02.milford.ma.boston.comcast.net [68.87.157.45]

              4 7 ms * 9 ms 10g-9-1-ur01.milford.ma.boston.comcast.net [68.87.144.237]

              5 7 ms * 7 ms 10g-8-3-ar02.needham.ma.boston.comcast.net [68.87.144.241]

              6 7 ms * * po-12-ar02.woburn.ma.boston.comcast.net [68.87.146.46]

              7 7 ms * 7 ms po-10-ar01.woburn.ma.boston.comcast.net [68.87.146.41]

              8 8 ms 12 ms 9 ms te-4-1-cr01.boston.ma.cbone.comcast.net [68.86.72.25]

              9 10 ms 11 ms 10 ms te-0-4-0-4-cr01.boston.ma.ibone.comcast.net [68.86.88.13]

              10 29 ms 15 ms 18 ms te-0-4-0-4-cr01.newyork.ny.ibone.comcast.net [68.86.88.9]

              11 17 ms 14 ms 13 ms 64.215.24.85

              12 82 ms 82 ms 82 ms so1-3-0-2488M.ar1.DAL2.gblx.net [67.17.79.185]

              13 73 ms 76 ms 73 ms The-Planet.ge-4-3-0.ar1.DAL2.gblx.net [64.210.104.58]

              14 77 ms 77 ms 76 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

              15 75 ms 85 ms 76 ms vl41.dsr01.dllstx4.theplanet.com [70.85.127.83]

              16 76 ms 80 ms 79 ms gi1-0-1.car07.dllstx4.theplanet.com [67.19.255.26]

              17 78 ms 105 ms 82 ms aa.5a.1343.static.theplanet.com [67.19.90.170]



              Trace complete.
              Current game name : Lost, Phantom Thief

              Comment


              • #8
                Re: Read this if you've been lagging out

                Every single time I traceroute to TGNS, my route changes literally every second. When I'm tracing with PingPlotter, the list of routes just grows and grows and grows.
                Originally posted by Eternaly_Lost
                That can not be good for the connection and must be the sorce of the lag.
                Agreed, changing routes are not desirable, but it's premature to assume them the cause of the major lag. In fact, the kind of lag Ag outlined ("lagged out for more than 10 seconds") is not going to be caused merely by these type of route changes. Route changes like that add a fraction of a second to your latency, not several, several whole seconds.
                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


                • #9
                  Re: Read this if you've been lagging out

                  perhaps a problem with the router(data center) that holds that IP. If they've been having problems, or undergone major retrofit, it could be hicups over hte last few weeks...

                  http://theplanet.com/ <-- that's where we should be looking I think.
                  Ambriento for comm! Vote today!

                  Comment


                  • #10
                    Re: Read this if you've been lagging out

                    Code:
                    Tracing route to tgns.tacticalgamer.com [67.19.90.170]
                    over a maximum of 30 hops:
                    
                     1     2 ms     1 ms     1 ms  192.168.1.1
                      
                     2    57 ms    58 ms    64 ms  12-10-27-250.ptcnet.net [12.10.27.250]
                      
                     3    54 ms    57 ms    55 ms  12-10-27-249.ptcnet.net [12.10.27.249]
                     
                     4    56 ms    58 ms    55 ms  192.168.1.2
                     
                     5    63 ms    60 ms    59 ms  12.126.92.169
                      
                     6    90 ms    88 ms    91 ms  12.123.209.202
                     
                     7    83 ms    88 ms    84 ms  tbr1-p012502.sl9mo.ip.att.net [12.122.11.97]
                    
                     8    89 ms    86 ms    89 ms  tbr2-cl6.dlstx.ip.att.net [12.122.10.90]
                    
                     9    84 ms    84 ms    82 ms  ar8-p3110.dlstx.ip.att.net [12.123.16.165]
                    
                     10    84 ms    81 ms    87 ms  12.119.136.14
                     
                     11    96 ms   145 ms    93 ms  vl31.dsr01.dllstx3.theplanet.com [70.85.127.29]
                    
                     12    85 ms    85 ms    87 ms  vl42.dsr02.dllstx4.theplanet.com [70.85.127.91]
                    
                     13    90 ms    84 ms    86 ms  gi1-0-2.car07.dllstx4.theplanet.com [67.19.255.154]
                    
                     14    87 ms    88 ms    88 ms  aa.5a.1343.static.theplanet.com [67.19.90.170]
                    
                    Trace complete.
                    Looks like more than one person has a linksys router lol

                    Comment


                    • #11
                      Re: Read this if you've been lagging out

                      heh, my tgns trace route

                      Originally posted by tracert
                      1 1 ms 1 ms 1 ms 192.168.0.1

                      2 7 ms 10 ms 8 ms 73.60.64.1

                      3 15 ms 7 ms * GE-1-2-ur01.G4snellville.ga.atlanta.comcast.net[68.86.109.165]

                      4 8 ms * 6 ms 10g-9-1-ur01.G5snellville.ga.atlanta.comcast.net[68.86.106.182]

                      5 7 ms * 7 ms 10g-9-1-ur01.D2lithonia.ga.atlanta.comcast.net [68.86.106.186]

                      6 8 ms * * 10g-9-2-ur01.D1stonemtn.ga.atlanta.comcast.net [68.86.106.190]

                      7 9 ms * 9 ms 10g-9-2-ar01.D1stonemtn.ga.atlanta.comcast.net [68.86.106.158]

                      8 12 ms 8 ms 11 ms 12.124.64.73

                      9 26 ms 29 ms 26 ms tbr2-p013801.attga.ip.att.net [12.123.20.174]

                      10 28 ms 27 ms 26 ms tbr1-cl13.dlstx.ip.att.net [12.122.2.89]

                      11 24 ms 24 ms 29 ms gr1-p350.dlstx.ip.att.net [12.123.16.169]

                      12 25 ms 28 ms 26 ms 12.119.136.14

                      13 75 ms 207 ms 25 ms vl31.dsr02.dllstx3.theplanet.com [70.85.127.30]

                      14 24 ms 26 ms 24 ms vl41.dsr01.dllstx4.theplanet.com [70.85.127.83]

                      15 26 ms 27 ms 26 ms gi1-0-2.car07.dllstx4.theplanet.com [67.19.255.154]

                      16 27 ms 24 ms 28 ms aa.5a.1343.static.theplanet.com [67.19.90.170]
                      --------

                      Zephyr: Besides Wyzcrak and his godly voice; the kind of voice that you will expect to say "Zephyr, I need you to build an ark at Marine Start, with room for two of every structure so that I may turret spam for 40 days and 40 nights" that is.

                      Squeak:Sometimes I'm awed by zibs genius. Then I remember he's Canadian and I feel significantly less threatened.

                      Comment


                      • #12
                        Re: Read this if you've been lagging out

                        So wuss, lost and I all go through the same pair of DAL2.glbx.net addresses: 67.17.79.185 and 64.210.104.58. I know lost, nine hells and myself always lag out simultaneously, whereas the same is not true for dark and keres. I haven't determined yet whether dude is lagging out at the same time, but my hypothesis is no. If he isn't, that will be enough evidence for me to be fairly confident that the problem is at those glbx.net addresses. The next one on the path is the start of the theplanet addresses( 70.85.127.29/30), and is shared between people having this problem and people not having this problem, making it unlikely that this address is the location of the problem. If it turns out dude is lagging out at the same time, I will need to check with keres again, and take a closer look at the 70.85.127.29/30 possibility.

                        Comment


                        • #13
                          Re: Read this if you've been lagging out

                          Apophis, any recommendations as we work together to collect and look through this data?
                          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


                          • #14
                            Re: Read this if you've been lagging out

                            I think what's also interesting about Lost's, Wuss', and my traceroute is there are a lot of packets being dropped by the comcast addresses. If you look at the three, we seem to drop about the same amount.
                            --------

                            Zephyr: Besides Wyzcrak and his godly voice; the kind of voice that you will expect to say "Zephyr, I need you to build an ark at Marine Start, with room for two of every structure so that I may turret spam for 40 days and 40 nights" that is.

                            Squeak:Sometimes I'm awed by zibs genius. Then I remember he's Canadian and I feel significantly less threatened.

                            Comment


                            • #15
                              Re: Read this if you've been lagging out

                              i do nopt really lag much... at end game there is a HUGE lag!

                              that is about it.

                              do you serve a purpose or do you purposely serve

                              Comment

                              Connect

                              Collapse

                              TeamSpeak 3 Server

                              Collapse

                              Advertisement

                              Collapse

                              Twitter Feed

                              Collapse

                              Working...
                              X