Packet Loss

[Pannono]

I signed in to the online arenas page and I noticed lots of packet loss when I checked my ping



Anything I can do on my end to fix this?
My internet has been running slow lately; i have had the same 1.5 mbps internet since '07 and it ran AH before with no problems. Should I upgrade to 3 mbps? Or make the leap to 15 mbps?  its $15 more than 3 mbps.
This happened when i first bought my older computer; it was suggested that I change to the high performance power setting back then. I tried it now and it did not work.

[Skuzzy]

The packet loss may be out on the Internet (usually is) in which case, upgrading the speed of your local connection will simply mean you get to see the packet loss faster.

Try running a Ping Plot to 206.16.60.38 and see where, if any, packet loss may be occurring.

The Internet has changed quite a bit in the last year.  High data demand services have taken a chunk out of the overall bandwidth availability and the various communications services have not been able to keep up with the increasing demand.

[MutleyBR]

Hi friends!

Having the same problem here since last night, when ping went over 1200 and I gave up playing.

Waited until now, hoping it would be fixed but it wasn´t.

Already did traceroutes to different AH Arena's IP's.

The problem seems to be at 12.122.138.1, Dallas, ggr1.dlstx.ip.att.net

Thanks Skuzz in advance for calling Admin there.    

Take care all!!

Mutley.

PS: Skuzz if you want, I can post traceroutes to other IP's through the same node, the problem is constant for 12.122.138.1, Dallas, ggr1.dlstx.ip.att.net

================================================================

Node Data
Node Net Reg IP Address      Location            Node Name
   1   -   - ROUTED PC       Rio de Janeiro      ORION
   2   1   - CABLE MODEM     Unknown            
   3   2   - 201.17.0.8      Unknown            
   4   2   - 201.17.0.2      Unknown            
   5   3   1 200.209.203.33  Rio de Janeiro      embratel-t0-0-2-0-tacc01.rjo.embratel.net.br
   6   3   1 200.230.252.238 Rio de Janeiro      ebt-t0-1-2-0-tcore01.rjo.embratel.net.br
   7   3   1 200.230.220.42  Rio de Janeiro      ebt-bundle-pos1211-intl01.nyk.embratel.net.br
   8   4   2 173.241.128.133 New York            xe-10-2-0.nyc20.ip4.tinet.net
   9   5   - 192.205.37.37   Unknown            
  10   6   3 12.122.86.10    New York            cr2.n54ny.ip.att.net
  11   7   3 12.122.3.38     WASHINGTON D.C.     cr2.wswdc.ip.att.net
  12   8   3 12.122.1.173    Atlanta             cr1.attga.ip.att.net
  13   9   3 12.122.28.174   Dallas              cr2.dlstx.ip.att.net
  14  10   3 12.122.138.1    Dallas              ggr1.dlstx.ip.att.net
  15  11   - 12.122.251.66   Unknown            
  16  12   4 63.241.193.10   Dallas              mdf001c7613r0003-gig-10-1.dal1.attens.net
  17  13   - 206.16.60.41    Irving              


Packet Data
Node High Low  Avg  Tot  Lost
   1    0    0    0    1    0
   2   40   40   40    1    0
   3   13   13   13    1    0
   4   21   21   21    1    0
   5   12   12   12    1    0
   6  126  126  126    1    0
   7  137  137  137    1    0
   8  137  137  137    1    0
   9  145  145  145    1    0
  10  170  170  170    1    0
  11  196  196  196    1    0
  12  191  191  191    1    0
  13  201  201  201    1    0
  14  835  835  835    2    1
  15  198  198  198    1    0
  16  190  190  190    1    0
  17  835  835  835    1    0

[Skuzzy]

The sample size is too small to be helpful.  This is where Ping Plot comes in handy as you can specify a count or time to run and capture more data points.  The more data points, the more reliable the results are.

This could be an asynchronous route problem, more than anything else.  I happen to know all the AT&T nodes use asyn routing, where the path back is different than the path going to the destination.

I will have to run the reverse to you to get that information.

[MutleyBR]

Firewalls hard and soft are set not to answer ICMP do you want me to change that?

Mut

[Skuzzy]

No, I do not go directly to the end IP, I use the ISP router IP's.

[MutleyBR]

Roger, thanks.

BTW, ping now to to all arenas are over 1200, except for SE I and II which are normal.


Mut

[Skuzzy]

Here is the trace back to your ISP's first router in your trace.  Note the jump in times at the overseas gateway.

traceroute to 201.17.0.8 (201.17.0.8), 30 hops max, 40 byte packets
 1  206.16.60.46 (206.16.60.46)  0.394 ms  0.302 ms  0.244 ms
 2  mdf001c7613r0002-gig-10-2.dal1.attens.net (63.241.193.17)  0.367 ms  0.522 ms  0.317 ms
 3  12.122.251.61 (12.122.251.61)  1.133 ms 12.122.251.57 (12.122.251.57)  1.091 ms 12.122.251.61 (12.122.251.61)  1.088 ms
 4  cr2.dlstx.ip.att.net (12.122.138.190)  3.505 ms  4.068 ms  3.091 ms
 5  12.122.212.13 (12.122.212.13)  1.306 ms 12.122.212.9 (12.122.212.9)  179.338 ms  1.397 ms
 6  192.205.37.126 (192.205.37.126)  1.489 ms  1.470 ms  1.465 ms
 7  0.ae1.XL3.DFW7.ALTER.NET (152.63.96.46)  1.505 ms  1.545 ms  1.585 ms
 8  0.ge-7-3-0.XL3.MIA4.ALTER.NET (152.63.1.110)  38.640 ms  39.017 ms 0.so-5-1-0.XL3.MIA4.ALTER.NET (152.63.80.38)  39.042 ms
 9  GigabitEthernet6-0-0.GW9.MIA4.ALTER.NET (152.63.81.249)  38.925 ms  39.644 ms  38.713 ms
10  embratel-gw.customer.alter.net (63.65.191.90)  418.197 ms  441.007 ms  425.592 ms
11  ebt-Bundle-POS1213-tcore01.rjo.embratel.net.br (200.230.220.17)  161.506 ms  163.021 ms  161.083 ms
12  ebt-T0-3-0-0-tacc01.rjo.embratel.net.br (200.244.40.65)  151.236 ms  151.482 ms  151.164 ms
13  netservicos-T0-0-2-0-tacc01.rjo.embratel.net.br (200.209.203.34)  161.815 ms  161.805 ms  162.221 ms
14  * * *
15  * * *
16  * * *
17  *^C

There is definately something going on here, but it looks like multiple things.  Your hop #5 seems to be the deepest I can trace to.

I'll file a trouble ticket with AT&T, but I think you need to file one with your ISP as well.

[MutleyBR]

Will do, thanks again.

Mutley

[Pannono]

Here are my ping plotter results. I set it to do 1 sample per second I did 300 samples.

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 11/29/2011 5:45:49 PM to 11/29/2011 5:50:53 PM

Hop Sent Err  PL% Min Max Avg  Host Name / [IP]
 1   299  44 14.7   0   1   0  [192.168.0.1]
 2   298  48 16.1  43  53  45  phnx-dsl-gw28-220.phnx.qwest.net [67.40.227.220]
 3   297  44 14.8  42 148  48  phnx-agw1.inet.qwest.net [216.160.199.217]
 4   298  43 14.4  54 149  61  lap-brdr-03.inet.qwest.net [67.14.22.78]
 5   297  51 17.2  54 129  58  [192.205.36.17]
 6   135  16 11.9  82 121  86  cr2.la2ca.ip.att.net [12.123.30.150]
 7   297  44 14.8  82 139  88  cr2.dlstx.ip.att.net [12.122.28.177]
 8   297  47 15.8  81 266  95  ggr1.dlstx.ip.att.net [12.122.138.1]
 9   157  21 13.4  80 249  85  [12.122.251.66]
10   297  45 15.2  79 380  88  mdf001c7613r0004-gig-12-1.dal1.attens.net [63.241.193.14]
11   298  46 15.4  81  86  82  [206.16.60.38]


Edit: 600 samples
Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 11/29/2011 5:45:49 PM to 11/29/2011 5:56:06 PM

Hop Sent Err   PL% Min Max Avg  Host Name / [IP]
 1   608  88  14.5   0   1   0  [192.168.0.1]
 2   608 105  17.3  42 500  49  phnx-dsl-gw28-220.phnx.qwest.net [67.40.227.220]
 3   608  93  15.3  42 461  52  phnx-agw1.inet.qwest.net [216.160.199.217]
 4   608  94  15.5  54 422  65  lap-brdr-03.inet.qwest.net [67.14.22.78]
 5   608 103  16.9  54 385  62  [192.205.36.17]
 6   310  54  17.4  82 479  92  cr2.la2ca.ip.att.net [12.123.30.134]
 7   608 107  17.6  82 442  92  cr2.dlstx.ip.att.net [12.122.28.177]
 8   608  96  15.8  81 522 101  ggr1.dlstx.ip.att.net [12.122.138.1]
 9   282  43  15.2  81 488  93  [12.122.251.70]
10   608  93  15.3  79 419  92  mdf001c7613r0004-gig-12-1.dal1.attens.net [63.241.193.14]
11     7   7 100.0   0   0   0   [-]
12   608  85  14.0  81 578  89  [206.16.60.38]

[Pannono]

Here is a much larger sample size.


Target Name: N/A
         IP: 206.16.60.41
  Date/Time: 11/29/2011 6:16:24 PM to 11/29/2011 9:42:46 PM

Hop Sent  Err PL% Min  Max Avg  Host Name / [IP]
 1 12107  850 7.0   0    1   0  dslmodem.domain.actdsltmp [192.168.0.1]
 2 12107  983 8.1  42 2310  80  phnx-dsl-gw28-220.phnx.qwest.net [67.40.227.220]
 3 12106 1001 8.3  42 2269  83  phnx-agw1.inet.qwest.net [216.160.199.217]
 4 12107 1062 8.8  54 2361  96  lap-brdr-03.inet.qwest.net [67.14.22.78]
 5 12106 1063 8.8  54 2425  95  [192.205.36.17]
 6  6052  495 8.2  82 2387 121  cr2.la2ca.ip.att.net [12.123.30.134]
 7 12106  969 8.0  82 2430 124  cr2.dlstx.ip.att.net [12.122.28.177]
 8 12105  995 8.2  80 2402 132  ggr1.dlstx.ip.att.net [12.122.138.1]
 9  5974  529 8.9  80 2353 125  [12.122.251.66]
10 12106 1023 8.5  78 2279 122  mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
11 12106  969 8.0  80 2304 120  [206.16.60.41]

It seems that I am just running into problem after problem here. The cost is starting to add up. Is there anything that can be done about the packet loss or am I just going to have to live with it?

[MutleyBR]

Today, pings are back to normal(for my connection) with no significant packet loss. 

Mutley   

[Skuzzy]

Here is a much larger sample size.


Target Name: N/A
         IP: 206.16.60.41
  Date/Time: 11/29/2011 6:16:24 PM to 11/29/2011 9:42:46 PM

Hop Sent  Err PL% Min  Max Avg  Host Name / [IP]
 1 12107  850 7.0   0    1   0  dslmodem.domain.actdsltmp [192.168.0.1]
 2 12107  983 8.1  42 2310  80  phnx-dsl-gw28-220.phnx.qwest.net [67.40.227.220]
 3 12106 1001 8.3  42 2269  83  phnx-agw1.inet.qwest.net [216.160.199.217]
 4 12107 1062 8.8  54 2361  96  lap-brdr-03.inet.qwest.net [67.14.22.78]
 5 12106 1063 8.8  54 2425  95  [192.205.36.17]
 6  6052  495 8.2  82 2387 121  cr2.la2ca.ip.att.net [12.123.30.134]
 7 12106  969 8.0  82 2430 124  cr2.dlstx.ip.att.net [12.122.28.177]
 8 12105  995 8.2  80 2402 132  ggr1.dlstx.ip.att.net [12.122.138.1]
 9  5974  529 8.9  80 2353 125  [12.122.251.66]
10 12106 1023 8.5  78 2279 122  mdf001c7613r0003-gig-10-1.dal1.attens.net [63.241.193.10]
11 12106  969 8.0  80 2304 120  [206.16.60.41]

It seems that I am just running into problem after problem here. The cost is starting to add up. Is there anything that can be done about the packet loss or am I just going to have to live with it?

The packet loss starts at your first hop.  That is your router.  Are you using a wireless connection?  If not, try power cycling that router.

If you are using a wireless connection, then packet loss is going to happen and the degree it happens will vary based on many external factors.

Today, pings are back to normal(for my connection) with no significant packet loss. 

Mutley   

That is good to hear.

[Pannono]

I am currently with Quest/CenturyLink and I use a DSL modem. I have my phone line connected to my modem and the ethernet cord connected directly from the modem to the tower. However, the modem is approximately 5 years old. My dad called HP yesterday and inquired about it and HP said that a modem that old won't be able to handle Windows 7 well.
I also recently did an internet speed test that showed that I have a ping of 135ms, a download speed of 0.55 mbps, and an upload speed of 0.16 mbps. I am in Phoenix and the test is being done from somewhere in Tucson.

[Skuzzy]

It does not matter what the speed test shows.  It is clear you are losing data packets right at your connection.  Bad cable?  Modem could be going bad as well.