wierd lag

whacknut · Post by **whacknut** » Tue May 11, 2010 2:03 am

I was wondering if you guys changed any of the server settings when you added the new maps as I, and from what Ive heard a few other players, are haveing wierd red vertical lines on the lag o meter showing up. When its real bad it has 5 or 6 of them on it at a time and then other times it goes away. I only ask because it started around the time the new maps came in and I havent changed or done anything to cause it on my end. On the other hand i am on comcast and you never know what they get up to also and this is out there but that flooding in tennessee happened around the same time and im in florida so maybe the routeing got screwed. If anyone else is haveing the same issue would you mind posting if your on comcast and what state, thanks

CannonFodder · Post by **CannonFodder** » Fri May 14, 2010 8:41 pm

Same exact thing, also on Comcast but in Washington state. Always had a butter-smooth connection to BBA1 before. Now it's all hurky-jerky-lurchy.

Post by **Zeus** » Fri May 14, 2010 8:45 pm

Nope no changes, all same as usual.

More then likely your seeing some sort of routing issue and problem with one particular hop, with all the weird weather going on, wouldnt surprise me if some of your routes to the server havent been changed.

Try a tracert to the server when you see the issues and see what it says.

CannonFodder · Post by **CannonFodder** » Fri May 14, 2010 8:52 pm

Traceroute looks fine, if a bit wordy. Too many damn hops in the internet these days:

Code: Select all

traceroute to bba1.badassservers.net (74.53.29.121), 64 hops max, 40 byte packets
 1  73.98.2.1 (73.98.2.1)  7.205 ms  8.699 ms  7.314 ms
 2  ge-3-27-ur01.olympia.wa.seattle.comcast.net (68.87.205.129)  7.101 ms  7.481 ms  16.379 ms
 3  te-5-3-ur02.olympia.wa.seattle.comcast.net (68.86.96.14)  9.302 ms  8.325 ms  13.393 ms
 4  te-0-9-0-4-ar01.seattle.wa.seattle.comcast.net (68.86.96.18)  12.312 ms  11.143 ms  12.533 ms
 5  pos-1-4-0-0-cr01.seattle.wa.ibone.comcast.net (68.86.90.209)  10.913 ms  11.792 ms  11.236 ms
 6  pos-0-10-0-0-cr01.portland.or.ibone.comcast.net (68.86.85.106)  16.178 ms  22.462 ms  17.223 ms
 7  pos-1-15-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.85.197)  29.901 ms  28.063 ms  28.344 ms
 8  pos-1-9-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.86.254)  38.496 ms  37.514 ms  38.240 ms
 9  pos-0-13-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.146)  71.914 ms  74.433 ms  73.395 ms
10  pos-0-0-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.86.90)  72.762 ms  75.222 ms  72.989 ms
11  theplanet-cr01.dallas.tx.ibone.comcast.net (75.149.228.2)  73.196 ms  72.663 ms  74.246 ms
12  1e.ff.5746.static.theplanet.com (70.87.255.30)  73.238 ms
    te9-1.dsr01.dllstx3.theplanet.com (70.87.253.6)  83.198 ms
    te9-1.dsr02.dllstx3.theplanet.com (70.87.253.22)  74.129 ms
13  te1-3.dsr02.dllstx2.theplanet.com (70.87.253.122)  73.239 ms
    86.fd.5746.static.theplanet.com (70.87.253.134)  76.675 ms
    te1-3.dsr02.dllstx2.theplanet.com (70.87.253.122)  74.655 ms
14  te1-1.car05.dllstx6.theplanet.com (70.87.254.170)  73.945 ms
    te1-2.car05.dllstx6.theplanet.com (70.87.254.174)  72.721 ms
    te1-1.car05.dllstx6.theplanet.com (70.87.254.170)  74.520 ms
15  79.1d.354a.static.theplanet.com (74.53.29.121)  74.880 ms  74.032 ms  75.419 ms

CannonFodder · Post by **CannonFodder** » Fri May 14, 2010 8:57 pm

Some medium-sized packet pings. Looks nice and stable.

Code: Select all

PING bba1.badassservers.net (74.53.29.121): 1024 data bytes
1032 bytes from 74.53.29.121: icmp_seq=0 ttl=112 time=75.597 ms
1032 bytes from 74.53.29.121: icmp_seq=1 ttl=112 time=75.656 ms
1032 bytes from 74.53.29.121: icmp_seq=2 ttl=112 time=76.562 ms
1032 bytes from 74.53.29.121: icmp_seq=3 ttl=112 time=74.904 ms
1032 bytes from 74.53.29.121: icmp_seq=4 ttl=112 time=76.654 ms
1032 bytes from 74.53.29.121: icmp_seq=5 ttl=112 time=75.001 ms
1032 bytes from 74.53.29.121: icmp_seq=6 ttl=112 time=74.565 ms
1032 bytes from 74.53.29.121: icmp_seq=7 ttl=112 time=75.047 ms
1032 bytes from 74.53.29.121: icmp_seq=8 ttl=112 time=75.080 ms
1032 bytes from 74.53.29.121: icmp_seq=9 ttl=112 time=76.051 ms
1032 bytes from 74.53.29.121: icmp_seq=10 ttl=112 time=75.615 ms
1032 bytes from 74.53.29.121: icmp_seq=11 ttl=112 time=73.941 ms
1032 bytes from 74.53.29.121: icmp_seq=12 ttl=112 time=75.667 ms
1032 bytes from 74.53.29.121: icmp_seq=13 ttl=112 time=74.895 ms
1032 bytes from 74.53.29.121: icmp_seq=14 ttl=112 time=75.370 ms

CannonFodder · Post by **CannonFodder** » Fri May 14, 2010 9:06 pm

HAHA! I found something.

Code: Select all

# traceroute -nq 10 -P UDP bba1.badassservers.net
traceroute to bba1.badassservers.net (74.53.29.121), 64 hops max, 40 byte packets
 1  73.98.2.1  15.607 ms  15.451 ms  9.107 ms  25.396 ms  15.122 ms  12.978 ms  8.673 ms  14.250 ms  22.862 ms  7.499 ms
 2  68.87.205.129  8.295 ms  16.401 ms  9.079 ms  17.253 ms  14.751 ms  20.657 ms  17.713 ms  28.843 ms  9.554 ms  12.548 ms
 3  68.86.96.14  16.201 ms  12.959 ms  12.120 ms  17.244 ms  7.820 ms  16.367 ms  9.578 ms  17.707 ms  8.979 ms  15.271 ms
 4  68.86.96.18  31.635 ms  11.646 ms  13.433 ms  17.248 ms  15.570 ms  13.403 ms  27.150 ms  13.367 ms  13.852 ms  16.378 ms
 5  68.86.90.209  12.749 ms  18.548 ms  12.550 ms  15.537 ms  11.285 ms  12.540 ms  13.409 ms  13.411 ms  12.122 ms  13.407 ms
 6  68.86.85.106  16.651 ms  15.905 ms  16.416 ms  17.673 ms  17.314 ms  18.558 ms  15.982 ms  16.043 ms  17.622 ms  15.092 ms
 7  68.86.85.197  29.037 ms  29.245 ms  26.737 ms  28.413 ms  27.982 ms  27.568 ms  27.523 ms  30.186 ms  30.989 ms  27.977 ms
 8  68.86.86.254  38.936 ms  37.374 ms  39.154 ms  38.725 ms  39.142 ms  37.859 ms  50.674 ms  38.291 ms  38.719 ms  36.566 ms
 9  68.86.85.146  72.809 ms  74.687 ms  73.401 ms  73.897 ms  73.313 ms  73.312 ms  73.728 ms  72.068 ms  72.859 ms  74.620 ms
10  68.86.86.90  73.294 ms  73.742 ms  73.747 ms  73.722 ms  74.184 ms  74.606 ms  75.026 ms  74.193 ms  73.732 ms  74.195 ms
11  75.149.228.2  78.003 ms  78.031 ms  77.132 ms  76.794 ms  75.883 ms  76.731 ms  77.184 ms  77.623 ms  78.038 ms  86.602 ms
12  70.87.253.6  75.015 ms
    70.87.253.22  78.875 ms
    70.87.253.90  77.164 ms
    70.87.253.2  74.563 ms
    70.87.253.18  77.589 ms
    70.87.253.86  72.857 ms
    70.87.255.26  76.725 ms
    70.87.253.22  77.579 ms
    70.87.253.90  77.584 ms
    70.87.255.30  81.851 ms
13  70.87.253.114  79.298 ms  76.760 ms  75.882 ms  76.326 ms
    70.87.253.122  81.462 ms
    70.87.253.114  76.713 ms  75.861 ms
    70.87.253.122  75.439 ms
    70.87.253.114  78.010 ms
    70.87.253.134  77.182 ms
14  70.87.254.174  75.803 ms
    70.87.254.170  73.726 ms
    70.87.254.174  76.701 ms
    70.87.254.170  75.023 ms  74.553 ms *
    70.87.254.174  77.870 ms  77.093 ms  77.168 ms  78.490 ms
15  74.53.29.121  73.289 ms  73.726 ms  74.171 ms  74.730 ms  74.900 ms  73.724 ms  74.602 ms  81.896 ms  79.758 ms  75.024 ms

Take a look at hop 14 (te1-1.car05.dllstx6.theplanet.com). This appears to be a redundant router or load balancer. For those following along, this is a "hop" that can be serviced by different physical machines each time a packet goes through.

I set traceroute to send 10 UDP packets 40 bytes each to each hop. On hop 14, it hung for a sec during one of the packets and dropped it. Smells like a malcontent amongst one of the arrays.

CannonFodder · Post by **CannonFodder** » Fri May 14, 2010 9:12 pm

Hmmm, every hop in the route is giving me rock-solid responses EXCEPT 70.87.254.170 and 70.87.253.114. Most of the time the response is 75-76ms. But every once and awhile (couple of seconds during heavy packet rates), they go to 100+, 200+, or drop the packet entirely.

Code: Select all

13  70.87.253.122  74.161 ms
    70.87.253.134  75.009 ms
    70.87.253.122  74.565 ms
    70.87.253.126  74.579 ms
    70.87.253.114  77.163 ms  73.730 ms
    70.87.253.134  74.580 ms
    70.87.253.114  76.827 ms  208.817 ms
    70.87.253.126  74.529 ms
    70.87.253.114  141.066 ms
    70.87.253.122  76.274 ms
    70.87.253.134  76.721 ms
    70.87.253.114  82.312 ms
    70.87.253.134  73.717 ms  74.574 ms
    70.87.253.114  133.950 ms
    70.87.253.122  73.198 ms
    70.87.253.134  74.968 ms
    70.87.253.114  251.734 ms

CannonFodder · Post by **CannonFodder** » Fri May 14, 2010 9:23 pm

Ok, I can get consistent packet drops from 70.87.254.170 if I run heavy UDP packet rates/sizes though it. This does not show up with ping or Windows tracert (they use IGMP packets, not UDP), so there is that...