S3 Series

IF one has the proper information, finding out WHERE the problem lives is actually relatively easy and FREE. Fixing that problem might be a different discussion.

What program did you use?

The above is a "generic" screenie. Free "ping test" apps are available all over the internet. The "wrinkle" is that someone has to know the proper IP for iEN. Honestly, I would not publish it on a public forum, and am personally unable to as a matter of fact. (I can't "ping" it because I can't find out what it is) That means that each player that has a perceived connection problem has to "know someone" or they will never be able to "ping" the WBs IP. IF I happened to KNOW which hop was failing, I would publish the IP of that hop in a heartbeat and encourage iEN to figure out a way to have THEIR service provider eliminate that routing.

Thanks brothe!

In the past WBs was the target of DoS attacks, which as you can imagine wreaked havoc on the arena's. So I'm pretty sure they don't share the IPs out like they used to. Could be wrong, maybe just need to ask them for it?

Back inn the 90s I lived 60 miles from the servers in Raleigh. My connect was so piss poor it wasn't funny. You want to know where my packet loss was? In Raleigh....it was crazy. Now I'm blessed with a stable connect, relatively fast, and don't see a ton of warping.

There are a few Euro and Asia players who LAG so bad its not funny, but its not their fault...it just is what it is.. For example, last night I saw a plane explode, then saw tracers come out from the attacking plane. Was watching the whole thing....had to laugh. Been on the recieving end of that in the past with Garn. You see him, he attacks, it looks like he is d15 from you and you break, and then roll out..and then blow up...and to him you never moved. So your whole break/guns defense never existed. I would have loved to get some of his ACM cam and compare the two....but lets just say he did very well as a result of the LAG. Hope you guys get the disco's sorted out!

^ ^ ^
Welcome to my WB world.Can't get my mind to sync with that altered time state
it can be entertaining to watch others fight from afar. two planes turn to joust, both flame out more than several plane lengths before merging, and read on 100... RAM! lol

I saw a good one in the main the other night. We were hitting 3 from field 21, I dove in on 3 and strafed the remaining fuel that was keeping it open. After I closed 3 (with no planes upping or gvs on field at time of closing) I extended and turned around which took about 10 seconds in a 190D.As I was flying back over the field at 3 I looked down and I see a plane upping and a gv rolling from the spawnpoint! easily 8-10 seconds after the base had closed. WTH would cause that? I just started laughing and told my squad on TS about what I just witnessed.Been seeing some weird things lately.

<S>

Dave K.

I worked with Wolf for quite a while on this last night via a TeamViewer session.

First of all, from what I saw from Wolf's end, it isn't an iEN problem. It also isn't his ISP's problem. Here's why:

Wolf is located in the hills of Santa Barbara. I'll let him fill in the exact location if he chooses. I then ran a constant ping (ping -t IP) to the iEN IP from a command prompt in Windows. It was sprinkled with numerous "request timeout" errors. Great! iEN's IP times out, it is on their end, get them to fix it!

Not so fast. I also ran a constant ping (for hours) from my machine. Over a multiple hour period I had a *single* timeout from Seattle.

We both ran a TRACERT to iEN's server. My route which went from Seattle to Denver to Chicago to D.C. traced fine. Wolf's route to iEN's server which went from his home to L.A. to Dallas to Atlanta to D.C. frequently timed out in Atlanta.

Trying to eliminate the ISP, I also ran a constant ping from his location to the 352nd TS server in Seattle, Yahoo (which appears to be in Chicago), and Oracle (which appears to be in L.A.). His ping to Seattle and Chicago (and iEN in the D.C. area) also had numerous timeouts. However, very few were at the same time which to me indicates that it *NOT* an ISP issue. Additionally, his PING to L.A. never timed out.

From what I can tell is that there is an overloaded regional router in the South/Southeast that is causing the problem. I feel this is further evidenced by the fact that when we started the test (early evening Pacific) his round trip PING was ~150ms. 2 am Pacific his PING was closer to 100ms.

It would be interesting to see the TRACERT output for everyone having problems, especially during those times when they are having difficulties staying connected.

For example:

C:\Windows\system32>tracert 50.22.237.11

Tracing route to 11.237.22.50.hypernia.com [50.22.237.11]
over a maximum of 30 hops:

1 5 ms <1 ms 7 ms 192.168.51.1
2 * * * Request timed out.
3 19 ms 19 ms 19 ms te-0-0-0-8-ur05.bellevue.wa.seattle.comcast.net [68.86.113.81]
4 18 ms 19 ms 19 ms be-1-ur06.bellevue.wa.seattle.comcast.net [69.139.164.122]
5 12 ms 33 ms 21 ms ae-18-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.117]
6 24 ms 29 ms 23 ms he-1-3-0-0-11-cr01.seattle.wa.ibone.comcast.net [68.86.93.169]
7 22 ms 17 ms 31 ms be-11-pe03.seattle.wa.ibone.comcast.net [68.86.84.78]
8 13 ms 19 ms 29 ms ae13.bbr01.wb01.sea02.networklayer.com [75.149.228.38]
9 47 ms 49 ms 49 ms ae0.bbr01.cs01.den01.networklayer.com [173.192.18.145]
10 44 ms 41 ms 47 ms ae7.bbr02.cs01.den01.networklayer.com [173.192.18.169]
11 66 ms 68 ms 79 ms ae0.bbr02.eq01.chi01.networklayer.com [173.192.18.130]
12 97 ms 99 ms 99 ms ae0.bbr02.eq01.wdc02.networklayer.com [173.192.18.154]
13 119 ms 109 ms 99 ms ae1.dar01.sr01.wdc01.networklayer.com [173.192.18.193]
14 97 ms 99 ms 99 ms po1.fcr02.sr01.wdc01.networklayer.com [208.43.118.149]
15 100 ms 116 ms 106 ms 11.237.22.50.hypernia.com [50.22.237.11]

Trace complete.

C:\Windows\system32>

iEN's IP address is: 50.22.237.11

Interesting stuff, huh? The "appropriate" thing for me is to apologize to iEN for suspecting that their ISP change was the problem. "IT guys" have a knowledge that I, likely, will never understand and they can figure this stuff out with more accuracy than I obviously can. It would appear that the internet "super-highway" takes a different route to iEN's new provider than it did to the previous one. Basically, when my route to iEN used to turn left at Albuquerque, now it turns right and hits a traffic jam in Atlanta. As a mere user of the "highway", I can't have any effect on the traffic jam in Atlanta, or elect to drive around it.

This is my typical PING from London.
I have broadband connection. 20MB up / 1 MB down.


C:\Users\Simon>tracert 50.22.237.11

Tracing route to 11.237.22.50.hypernia.com [50.22.237.11]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms SkyRouter.Home [192.168.0.1]
2 * * * Request timed out.
3 31 ms 30 ms 30 ms ip-84-38-37-52.easynet.co.uk [84.38.37.52]
4 31 ms 30 ms 30 ms 87-86-69-148.easynet.net [87.86.69.148]
5 123 ms 113 ms 119 ms te0-0-0-5.gr10.eqqas.us.easynet.net [87.86.77.92]
6 114 ms 114 ms 114 ms te0-0-0-5.gr10.eqqas.us.easynet.net [87.86.77.92]
7 114 ms 121 ms 112 ms te3-5.bbr01.eq01.wdc01.networklayer.com [206.126.236.185]
8 115 ms 114 ms 151 ms ae0.dar02.sr01.wdc01.networklayer.com [173.192.18.203]
9 116 ms 116 ms 117 ms po2.fcr02.sr01.wdc01.networklayer.com [208.43.118.151]
10 115 ms 115 ms 113 ms 11.237.22.50.hypernia.com [50.22.237.11]

Trace complete.

PEAK TIME UK - 8PM on 19th Dec.