Packet loss with Continuum Client, but NOT WinMtr

[Guest James Fischer]

When linking to the SSCX zones (Chaos, Powerball, WarZone...)

there was a sudden case of extreme (-90%) packet loss that

forced me to "spectate" after noon on Monday, 09/13/04.

Using the Continuum client's built-in traceroute facility, the losses

appeared to be within AT&T's infrastructre, as shown below:

 

Tracing Zone: SSCX Chaos/League Zone SVS IP Address: 64.85.65.229

 

Hop IP Address Host Name Loss(%) Min/Avg/Max Ping

--- --------------- -------------------------------- ------- ----------------

1 10.95.224.1 <unknown> 0.0 0 0 10

2 24.197.0.1 bed-va-gw.cablenet-va.com 0.0 0 10 30

3 24.197.0.106 bed-va-0-106.cablenet-va.com 0.0 0 0 10

4 12.124.65.21 <unknown> 0.0 10 20 30

5 12.123.21.82 gbr5-p90.attga.ip.att.net 83.3 10 10 10

6 12.122.12.41 tbr2-p013501.attga.ip.att.net .0 10 10 10

7 12.123.20.253 ggr1-p370.attga.ip.att.net .0 10 10 10

8 192.205.32.118 dcr1-so-4-0-0.atlanta.savvis.net 0.0 10 10 30

9 208.172.82.62 acr2-loopback.Seattle.savvis.net 0.0 70 110

10 208.172.81.222 bhr2-pos-0-0.Tukwilase2.savvis.n 0.0 90 90 100

11 216.34.64.42 csr11-ve241.Tukwilase2.savvis.ne 0.0 90 90 90

12 64.85.65.229 <unknown> 0.0 70 90 110

 

Cycles: 5

 

But this loss cannot be verified with the popular "WinMtr"

traceroute tool, which around here, is the defacto standard

for measurement. See below for the output from WinMtr.

 

What possible difference would there be between the built-in traceroute

tool, and another traceroute tool running on the same workstation?

 

Might this be a "bug" in the most recent release?

 

Does the game client, or the game server decide who must be forced

into "spectator" mode?

 

Please reply by e-mail, as I am not a gamer, I am the network

admin for the ISP downstream of AT&T wondering how we can

"prove" that this is a tangible problem to AT&T, and support our

customer's need for 24-hour space battles.

 

But the game is pretty decent, so maybe I >>AM<< now a "gamer".

 

Danke!

 

jfischer@supercollider.com

james.fischer@gmail.com

 

 

 

|------------------------------------------------------------------------------------------|

| WinMTR statistics |

| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |

|--------------------------------------------|-------|------|------|------|------|------|

| 10.95.224.1 - 0 | 519 | 519 | 0 | 11 | 78 | 15 |

| bed-va-gw.cablenet-va.com - 0 | 519 | 519 | 0 | 5 | 63 | 15 |

| bed-va-0-106.cablenet-va.com - 0 | 519 | 519 | 0 | 5 | 78 | 16 |

| 12.124.65.21 - 0 | 519 | 519 | 15 | 26 | 78 | 31 |

| gbr5-p90.attga.ip.att.net - 0 | 519 | 519 | 15 | 27 | 78 | 32 |

| tbr2-p013501.attga.ip.att.net - 0 | 519 | 519 | 15 | 29 | 78 | 31 |

| ggr1-p370.attga.ip.att.net - 0 | 519 | 519 | 15 | 27 | 94 | 31 |

| dcr1-so-4-0-0.atlanta.savvis.net - 0 | 519 | 519 | 15 | 28 | 94 | 31 |

| acr2-loopback.Seattle.savvis.net - 0 | 519 | 518 | 93 | 98 | 157 | 109 |

| bhr2-pos-0-0.Tukwilase2.savvis.net - 0 | 518 | 518 | 93 | 97 | 141 | 94 |

| csr1-ve242.Tukwilase2.savvis.net - 0 | 518 | 518 | 93 | 108 | 407 | 109 |

| 216.34.65.142 - 0 | 518 | 518 | 93 | 100 | 157 | 110 |

|_________________________________|_____|_____|____|_____|__

___|____|

 

WinMTR - 0.8. Copyleft @2000-2002 Vasile Laurentiu Stanimir ( stanimir@cr.nivis.com )

[Bargeld]

5 cycles on a traceroute won't give you a very accurate reading of the connection's long term integrity... let it run for about 10 mins, and get 100 cycles or so, then post the log.