ACME is moving to a new server!!!!

Go to http://acmectf.com for more info and file downloads!

[WORM]

As you guys know we have been running two dedicated servers in two locations, ACMEctf.com from Superb in McLean, VA. and ACMEgamers.com with Softlayer in Dallas, TX. That is quite a bit of expense and work to keep both going sooooooo........I am very happy to announce that we will be consolidating Acmectf & Acmegamers into one server. It will save me some work as well as many headaches....and yowza is very happy to cut costs too! 

We have decided to go with Softlayer in their new location just outside Washington, DC so everything will be based on East Coast. From the experience with both Superb and Softlayer there is no comparison, Softlayer offers better connectivity, better hardware, much better support and competitive pricing.

Hardware is dual processor, Xeon-Harperstown 5430 Quad Core @ 2.66GHZ, 4GB RAM, (2) 250GB HDD, and 100Mbps network ports for both public and private networks...this allows me to manage server on VPN, transfer files etc. without impacting public network or our bandwidth allocations. This box has the horsepower to run plenty of Q2 ports, the newer games we run now in Dallas and still have room to expand.

I have already completed some of the set-up and over the next few days should have everything ready to go. At this time we have all the games from acmegamers.com Dallas server running on DC box and the new IP's are as follows:

CoD4 TDM Pub - 208.43.95.242:28930

CoD4 Hardcore - 208.43.95.248:28930

Team Fortress 2 - 208.43.95.242:27015

Counter Strike: Source - 208.43.95.248:27015

Today I will drop TF2 & CS:S servers in Dallas. The CoD4 servers will remain up until I finish moving other files and cancel that server.

CoD4 Pub has been very, very popular and I hope that players follow us to DC. I do have an in game notice showing regularly with the new IP and have talked to some regulars there that say they will play on it. We depend on our regular players to keep all servers going.

There are quite a few Euro's that have been playing on CoD4 pub and even though ping is not as critical in that game the move will make their ping look better. Hopefully some of you guys from Q2 can join in there too!

I hope to get Q2 servers going on new box today. I have assigned IP 208.43.95.250 for Q2 servers. If all goes well I will probably force reconnects from the existing acmectf to the new server...players connecting to 66.36.243.128 will see an extra reconnect before entering new server.

I plan on setting up another port for No Tech CTF also, this probably will be the first one we get going.

Soon after Q2 servers are going I will point acmectf.com to 208.43.95.250 so domain can be used to connect, i.e. acmectf.com:27910 and so forth. Acmegamers.com domain is already changed for new location.

There are a lot of files on acmectf.com download page that I will have to move over so I will disable ftp access to it while I move them. It will be enabled on the new IP once I have all the files moved.

If all goes as I have planned there will be minimal disruptions. I do ask that you all help us to spread the word of the change so everyone knows where to find us once we shut down the old locations.

Thanks to everyone that supports us and plays on the servers, you guys make it the servers!

Constructive comments, suggestions, etc. are always welcome.

[yowza]

Thx as always for all the work my friends. 

[~simmeth~]

Kudos!

DC is closer to me than VA, good work!   

Still looks to be a 20 ping, hopefully less PL now tho!   

[amarris]

hope its just cause of downloads/moving that i get 355 ping to new server


 355   0 208.43.95.250   27910 -=ACME CTF ~ The La rtctf1a  ctf       0 of 24

[alka]

Nah, it's just the new r1cf you're running into. (r1ch's new anti canadian filter) 

Seriously though, new server is looking really good so far. Nice and smooth!

Thanks WORM. et al.

[angry]

ping is the same but i lag more

at least so far

[WORM]

I would like to see some tracerts from you guys. That would tell me more that "ping is same but i lag more." 

Hope you are luckier than I am....my route to Dallas server gives me 20-ish ping....now to the new one I route Memphis -> Dallas -> Los Angeles -> Washington, DC and get ~80-ish. Fn Comcast routing sux. 

But, even with that crappy route I see 0% packet loss where I have been getting some on route to the old ACMEctf.com server.

[angry]

Hope you are luckier than I am....my route to Dallas server gives me 20-ish ping....now to the new one I route Memphis -> Dallas -> Los Angeles -> Washington, DC and get ~80-ish. Fn Comcast routing sux. 

But, even with that crappy route I see 0% packet loss where I have been getting some on route to the old ACMEctf.com server.

haha I'll get that for you tonight if i remember.

i remember a west coast lithium server i used to play... my route there was like
Los Angeles, Dallas, Chicago, Memphis, Atlanta, Oklahoma City, San Francisco
talk about wtf routing.

[WORM]

Everyone should start connecting to the proper IP's now. I am redirecting players that connect to the old acmectf box to new one but this won't last long so update your shortcuts, server address lists or whatever you use to connect to us with new IP and ports.

Server list is updated on the home page here.. http://www.wormlair.com/forum/index.php

Dallas servers will be dropped by end of week too.

Public FTP access is now closed. I am in the process of compressing files to move and will give an update when FTP access is available again. Damn, there are lot of demos to move! 

Still much more to do but the basics for servers are running and I'm sure you guys will find what I miss and let me know.

Thanks to everyone for your help and patience!

[yowza]

A lot of work.
 I will look around and see what I can find to complain about. 

[angry]

Everyone should start connecting to the proper IP's now. I am redirecting players that connect to the old acmectf box to new one but this won't last long so update your shortcuts, server address lists or whatever you use to connect to us with new IP and ports.

don't know if you have or not (haven't connected to the old ip since the new one went up), but make sure to put both the new ip and the forum url in a message there (if possible) so people learn to keep updated on stuff like this.

[YellowFire]

43 ping?! NOOOOOOooooooooo!!!!

[The Cleaner]

My ping went from 38 all the way to 40.  This has already caused my rails to drop from 70+% down to 70% even. 


Ugh.  Guess it's time to retire.  I'll miss you Q2.

[angry]

43 ping?! NOOOOOOooooooooo!!!!

cry me a river.

[amarris]

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users>tracert 208.43.95.250

Tracing route to acmegamers.com [208.43.95.250]
over a maximum of 30 hops:

  1     1 ms    <1 ms     1 ms  home [192.168.1.254]
  2   22 ms    20 ms    15 ms  d66-222-160-1.abhsia.telus.net [66.222.160.1]
  3    21 ms    21 ms    20 ms  154.11.197.65
  4    54 ms    52 ms    52 ms  chcgildtgr00.bb.telus.com [154.11.11.34]
  5    52 ms    52 ms    52 ms  chgobbrj01pos010100.r2.ch.cox.net [68.105.30.193]
  6    87 ms    88 ms    88 ms  ashbbrj02-as0.0.r2.as.cox.net [68.1.1.232]
  7    86 ms    86 ms    85 ms  border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]
  8    85 ms    86 ms    86 ms  te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
  9    85 ms    86 ms    86 ms  po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
 10    86 ms    86 ms    85 ms  acmegamers.com [208.43.95.250]

Trace complete.

[angry]

looks like no lag for the moment... we'll see if that holds up when i connect in a bit


Target Name: acmegamers.com
         IP: 208.43.95.250
  Date/Time: 8/12/2008 8:00:12 PM

 2   19 ms   21 ms   20 ms   20 ms  [10.35.103.1]
 3   20 ms   19 ms   20 ms   18 ms  P6-6.LCR-01.LSANCA.verizon-gni.net [130.81.34.12]
 4  142 ms   19 ms   17 ms   20 ms  so-7-1-0-0.BB-RTR1.LAX01.verizon-gni.net [130.81.17.145]
 5   23 ms   19 ms   27 ms   20 ms  [68.105.30.185]
 6   93 ms   92 ms   92 ms   92 ms  ashbbbrj02-ae0.0.r2.as.cox.net [68.1.0.221]
 7   92 ms   94 ms   92 ms   95 ms  border1.te7-1-bbnet1.wdc008.pnap.net [216.52.127.36]
 8  105 ms   92 ms   94 ms   92 ms  te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
 9   92 ms   94 ms   94 ms   92 ms  po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
10   94 ms   94 ms   92 ms   95 ms  acmegamers.com [208.43.95.250]



[edit] this is for the old server ip, for comparison

Target Name: acmectf.com
         IP: 66.36.243.128
  Date/Time: 8/12/2008 8:01:38 PM

 2   19 ms   21 ms   17 ms   19 ms  [10.35.103.1]
 3   22 ms   19 ms   20 ms   28 ms  P6-6.LCR-01.LSANCA.verizon-gni.net [130.81.34.12]
 4   18 ms   19 ms   20 ms   20 ms  so-7-3-0-0.BB-RTR1.LAX01.verizon-gni.net [130.81.28.217]
 5   22 ms   21 ms   22 ms   19 ms  0.so-6-2-0.XT1.LAX7.ALTER.NET [152.63.112.45]
 6   27 ms   19 ms   24 ms   19 ms  0.so-5-1-0.XL1.LAX15.ALTER.NET [152.63.117.117]
 7   24 ms   21 ms   22 ms   33 ms  0.so-6-0-0.BR1.LAX15.ALTER.NET [152.63.116.21]
 8   19 ms   21 ms   21 ms   28 ms  so-7-1-0.edge1.LosAngeles1.Level3.net [209.0.227.37]
 9 -32764 ms -32764 ms   27 ms   23 ms  vlan99.csw4.LosAngeles1.Level3.net [4.68.20.254]
10 -32764 ms -32764 ms -32764 ms   23 ms  ae-83-83.ebr3.LosAngeles1.Level3.net [4.69.137.41]
11  105 ms   93 ms   92 ms   98 ms  ae-4.ebr4.Washington1.Level3.net [4.69.132.82]
12  103 ms  102 ms  105 ms   99 ms  ae-74-74.csw2.Washington1.Level3.net [4.69.134.182]
13   93 ms   94 ms   95 ms   92 ms  ae-22-79.car2.Washington1.Level3.net [4.68.17.68]
14   *       *       *       *       [-]
15   *       *       *       *       [-]
16   96 ms   98 ms   96 ms   96 ms  acmectf.com [66.36.243.128]

[angry]

looks like no lag for the moment... we'll see if that holds up when i connect in a bit

yeah, it didn't hold up... had 1-2% pl on my downstream on both the no-tech server and the pub... 0% pl upstream... which means on my end it plays choppy as shit but that everyone else on the server sees me smooth as silk

which makes it impossible to aim or evade/dodge accurately

case in point: on the no-tech server last night i was playing Guderian and every shot that went right through his model missed, but i hit him with a shot that was like 3 feet off his shoulder

i mean wtf m8

[Golgo13]

you talking about when i was there oh yea i seen that beating   

[angry]

you talking about when i was there oh yea i seen that beating   

yeah... it was pretty much like the time i beat you on your own server 

[Golgo13]

didn't know who you were. i usually get new players  who come. if i kill them too quick they leave.
so i just make it seem competetive  on their end. or a 'fun' game. believe what you want of course  don't make any difference to me.

[l3ft0verz]

im totally impressed with new server

my lag stats went from ~1.5% to zero
but thats not always relavent anyway

it 'feels' smoother, which to me is only true test
moreover a smooth grapple, one that isnt always sticking b/c it lost packet that told iit to release
just smoother movement overall

for a while lag at old server was getting so bad it just wasnt even worth playing, though i would anyway

thx worm, yowza, acme admins

here are some screenshots of tracert and in game netgraph
sometime late at nite, after midnight the netgraph will become patchy invisible, little islands of small green line interlaced with just nothing, that is really really nice ))

[angry]

lol @ blind-ass motherfuckers with neon skins

also that's a hell of a lot of hops for a 21-ping traceroute.

[Vidmaster]

You suffer from the Wake curse leftovers... 8 hops just in Richmond.

Comcast is so terrible.

[angry]

actually i figured 10 in richmond (the ip address-only hop before the richmond stream, and the hop before said ip address)

[ex]

I would like to see some tracerts from you guys. That would tell me more that "ping is same but i lag more." 

Hope you are luckier than I am....my route to Dallas server gives me 20-ish ping....now to the new one I route Memphis -> Dallas -> Los Angeles -> Washington, DC and get ~80-ish. Fn Comcast routing sux. 

But, even with that crappy route I see 0% packet loss where I have been getting some on route to the old ACMEctf.com server.

man, my ping is a tiny bit better.

too bad you guys couldn't have left it in dallas.  I would have pinged nearly 0.  lol

ping and tracert:

C:\Documents and Settings\user1>ping acmectf.com

Pinging acmectf.com [208.43.95.250] with 32 bytes of data:

Reply from 208.43.95.250: bytes=32 time=49ms TTL=112
Reply from 208.43.95.250: bytes=32 time=47ms TTL=112
Reply from 208.43.95.250: bytes=32 time=47ms TTL=112
Reply from 208.43.95.250: bytes=32 time=49ms TTL=112

Ping statistics for 208.43.95.250:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 47ms, Maximum = 49ms, Average = 48ms

C:\Documents and Settings\user1>tracert acmectf.com

Tracing route to acmectf.com [208.43.95.250]
over a maximum of 30 hops:

  1     6 ms     6 ms     6 ms  cpe-76-184-176-1.tx.res.rr.com [76.184.176.1]
  2     7 ms     8 ms     6 ms  gig1-2.dllatxgar-rtr1.tx.rr.com [70.125.216.101]
  3     7 ms     8 ms     9 ms  gig9-0-0.dllatxchn-rtr5.tx.rr.com [70.125.217.114]
  4    11 ms    12 ms    11 ms  gig0-1-0.hstntxl3-rtr1.texas.rr.com [72.179.205.74]
  5    12 ms    12 ms    12 ms  ae-2-0.cr0.hou30.tbone.rr.com [66.109.6.108]
  6    13 ms    14 ms    13 ms  ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
  7    36 ms    34 ms    32 ms  ae-1-0.cr0.atl20.tbone.rr.com [66.109.6.37]
  8    29 ms    31 ms    32 ms  ae-0-0.cr1.atl20.tbone.rr.com [66.109.6.35]
  9    46 ms    48 ms    47 ms  ae-4-0.cr0.dca10.tbone.rr.com [66.109.6.33]
 10    49 ms    47 ms    47 ms  ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
 11    49 ms    56 ms    47 ms  cox-twc.pr0.dca10.tbone.rr.com [66.109.9.110]
 12    48 ms    49 ms    49 ms  ashbbbrj02-ae0.0.r2.as.cox.net [68.1.0.221]
 13    48 ms    46 ms    47 ms  border1.te7-2-bbnet2.wdc008.pnap.net [216.52.127.98]
 14    47 ms    47 ms    47 ms  te1-1.cer01.wdc01.washingtondc-datacenter.com [66.151.100.66]
 15    49 ms    46 ms    47 ms  po1.fcr01.wdc01.washingtondc-datacenter.com [208.43.118.134]
 16    49 ms    50 ms    47 ms  acmegamers.com [208.43.95.250]

Trace complete.

[yowza]

 Good point on the "smooth". My pings are about the same but the feel of the server is different - and I believe in a good way.

[angry]

Good point on the "smooth". My pings are about the same but the feel of the server is different - and I believe in a good way.

same for me when i'm not losing packets on the downstream.

[CaKe]

Comcast is so terrible.

^^

[WORM]

This is the last day for the old server. Tomorrow....Sunday, August 17th...I will close it down and the move will be complete.

After that you must use either acmectf.com:port or correct IP:port to connect to Quake 2 servers because there will be no more connection forwarding.

For other games use the correct IP:port for connects....some are on acmegamers.com domain and some are on IP.

[alka]

[yowza]

Well done alka, sniff, sniff, well done 

[Bones]

Yes well done indeed.