Hello,

I have completed my burn in/memtest and set up a basic game (20k). I am looking for people to break the server (heavy load) by whatever means needed. Bug use/Dupes are allowed but honestly I don't see the point. I also am looking for ping times and responsivness. The server will be up untill 12am Sunday 01/08/12 when I upgrade to Win7 and move it to it's final home.

telnet: crunchergoes.mooo.com:23

Yes legit address

(Errata) Please limit your attacks against the TWGS server.

Heh, movement delay set to a third, and 250 turns?
What do you expect to get broke?

Edit: Fixed 40k/normal delay..

Sorry about that, it's been awhile.

They say any publicity is good publicity. I'm flattered! Good luck with your new server!

Thanks did you happen to stop by yet? All feedback is valued.

The server is on Fiber and located in VA Beach.

Not yet.

From Ireland, I have no landline and in a bad cell area, don't worry about me breaking your server:


C:\>tracert crunchergoes.mooo.com

Tracing route to crunchergoes.mooo.com [108.39.100.148]
over a maximum of 30 hops:

1 418 ms 401 ms 378 ms 192.168.50.253
2 359 ms 360 ms 377 ms 192.168.50.137
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 649 ms 516 ms 521 ms pool-108-39-100-148.nrflva.fios.verizon.net [108
.39.100.148]

Trace complete.

C:\>ping crunchergoes.mooo.com

Pinging crunchergoes.mooo.com [108.39.100.148] with 32 bytes of data:

Reply from 108.39.100.148: bytes=32 time=765ms TTL=113
Reply from 108.39.100.148: bytes=32 time=804ms TTL=113
Reply from 108.39.100.148: bytes=32 time=441ms TTL=113
Reply from 108.39.100.148: bytes=32 time=424ms TTL=113

Ping statistics for 108.39.100.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 424ms, Maximum = 804ms, Average = 608ms

C:\>ping crunchergoes.mooo.com

Pinging crunchergoes.mooo.com [108.39.100.148] with 32 bytes of data:

Reply from 108.39.100.148: bytes=32 time=612ms TTL=113
Reply from 108.39.100.148: bytes=32 time=487ms TTL=113
Reply from 108.39.100.148: bytes=32 time=585ms TTL=113
Reply from 108.39.100.148: bytes=32 time=444ms TTL=113

Ping statistics for 108.39.100.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 444ms, Maximum = 612ms, Average = 532ms

C:\>tracert crunchergoes.mooo.com

Tracing route to crunchergoes.mooo.com [108.39.100.148]
over a maximum of 30 hops:

1 524 ms 420 ms 401 ms 192.168.50.253
2 383 ms 378 ms 383 ms 192.168.50.137
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 625 ms 516 ms 540 ms pool-108-39-100-148.nrflva.fios.verizon.net [108
.39.100.148]

Trace complete.

C:\>

Frontier FIos or Verizon FIos?

Verizon

500 +150 game must make any US games you play in tough? What part of Ireland?

Oh and your traceroute is wierd. Based off your paste it appears your gateway/backbones arnt playing nice with the icmp request. It goes from your class C to my fios IP without any information inbetween. Havnt seen a whole lot of those, was it retracted?

It looked weird to me also, which is why I repeated it (4 times, just pasted 2).

I live more or less dead center in Ireland, Mullingar. The real problem with my connection is greenie nonsense - they decided a few years ago that the insulation in the wall cavities would be more effective if clad in aluminium foil so I live in a Faraday Cage and cellphone reception is bad indoors.

I still have a 2400 baud brain, reactions heading south to 300 baud, so it isn't really affecting my TW playing style.

Ahhh LOVE IT! I work for Frontier we aquired 13 states from Verizon Fios and in Fort Wayne we have Fios. Actually learning about it now lol... It's really intersting. Hellafied better than Comcast! I am getting it installed in two weeks can't wait!

Your gonna love it!

ping crunchergoes.mooo.com

Pinging crunchergoes.mooo.com [108.39.100.148] with 32 bytes of data:
Reply from 108.39.100.148: bytes=32 time=84ms TTL=111
Reply from 108.39.100.148: bytes=32 time=87ms TTL=111
Reply from 108.39.100.148: bytes=32 time=84ms TTL=111
Reply from 108.39.100.148: bytes=32 time=85ms TTL=111

Ping statistics for 108.39.100.148:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 84ms, Maximum = 87ms, Average = 85ms

               / Promethius / Enigma / Wolfen /

"A man who has no skills can be taught, a man who has no honor has nothing."

Type sub-space message [<ENTER> to send line. Blank line to end transmission]
S: ping : 219 ms
S: ping : 280 ms
S: ping : 234 ms
S: ping : 265 ms
S: ping : 250 ms
S: ping : 250 ms
S: ping : 234 ms
S: ping : 249 ms
S: ping : 250 ms
S: ping : 266 ms
S: ----------------
S: Min: 219 Max: 280 Average: 249 -- On the edge
S: High/Low Removed Average: 249
S: Min:Max Split: 61 Minimal Intermittent Lag Detected

(MomBots)

ProPing

S:
S: --------------------------------
S: ProPing v1.75
S: Mode: Normal
S: Game: moomoo
S: Ran on: 01/07/12 @ 6:26:07 PM
S: --------------------------------
S: ping : 234 ms
S: ping : 312 ms
S: ping : 281 ms
S: ping : 312 ms
S: ping : 624 ms
S: ping : 265 ms
S: ping : 156 ms
S: ping : 156 ms
S: ping : 140 ms
S: ping : 156 ms
S: --------------------------------
S: Min: 140 Max: 624 Average: 263
S: High/Low Removed Average: 234
S: Min:Max Split: 484
S: --------------------------------
S: Extreme Lag Detected
S: --------------------------------
S: Gridding, not a job, an adventure!