yeah sorry misread the tutorial, there is one very simular which used tunneling traffic with a regedit.
My mistake :P
yeah sorry misread the tutorial, there is one very simular which used tunneling traffic with a regedit.
My mistake :P
Nice find Ellay, latency down from 120+ to between 30-40
Damn I have Vista64.
Not sure if there is any additional performance improvement with this fix AFTER the patch???
There's not... I tested it, just to see. The patch basically removed the Nagle's algorithm (relative of the fisherman) itself.Originally Posted by schlange
I found this tutorial on patch day and decided to hold off seeing how the patch would fix this... the past 3-4 days I've had some terrible lag at night... my latency has been around 200ms before and after the patch, but after the patch I've seen my one or two of my character's (I'm running 5) suffer from lag issues and then DC.
I ran all 5 in the day yesterday with no problems at all, even in the day my latency is around 200ms... and then around 8-9pm the problems started, running 1 character is fine. Is there a way to tell if it's my ISP or it's just my server getting busier?
The TcpAckFrequency hack is still making a difference post patch from my tests (by disabling on one PC, these toons follow half a body length behind).
Author of Octopus (no longer being developed).
Download Ping Plotter Freeware. This is a Great Tool(tm).Then do a trace to us.logon.worldofwarcraft.com. You'll see something like this:
Look for the last line you see before you get the "destination unreachable" error. That is the last upstream server before you get into the WoW network (if one of you other folks remembers how to get the server IP, lemme know...I forget). Put that address into the "Address to trace" box, set your "# of times to trace" to 9999, set your trace delay to 1 second, set your "Samples to include" to 9999 and click the Trace button. Let that run for several minutes while you're having trouble. If you see any link in there that's got a huge spike in response time or shows any packet loss, you've probably found the culprit. If it all looks good there, then yeah, the problem is probably your server.
Now playing: WoW (Garona)
the logon server ip is 12.129.232.113
http://pewpewsquad.blogspot.com/ http://www.stage6.com/user/pewpewss/videos/
Team 1- 5 shamans <The PewPew Squad> Team2 - <Y o u Lo se> 70 druid, 70 shaman, 1 paladin, 24 mage, 1 mage
Team 1 -> <1--10--20--30--40--44--50--60--70>
Actually, I meant the actual play server IP (i.e.: the direct IP for Magtheridon). I say this because the logon server is for everyone, whereas the play servers are in different datacenters.
Now playing: WoW (Garona)
OhActually, I meant the actual play server IP (i.e.: the direct IP for Magtheridon). I say this because the logon server is for everyone, whereas the play servers are in different datacenters.
*edit* I think magetheridon is 12.129.224.113
blizzard seems to own a large range of IPs. like 12.129.210.0-12.129.240.0
*edit* n/m that isnt mag it is another lobby server.
looks like everything that ends in .113 is part of their logon server cluster.
*edit* kel'thuzad is 206.17.111.86 gimme a min to find mag's
it looks like mag is 206.16.23.44 but that makes no sense unless the registrant is outdated...
WoW servers seem to be in the range of 206.17.111.0-206.17.111.255
*edit*
if you want to try this yourself open a command prompt (start>run cmd) and type netstat and note the addresses listed. Then start wow, login and load the character on the realm you wish to identify. You should wait a minute or two to make sure you are not still communicating witht elobby servers then go back to the command window and do netstat again and look for XXX.XXX.XXX.XXX:3724 And that is your server's IP
http://pewpewsquad.blogspot.com/ http://www.stage6.com/user/pewpewss/videos/
Team 1- 5 shamans <The PewPew Squad> Team2 - <Y o u Lo se> 70 druid, 70 shaman, 1 paladin, 24 mage, 1 mage
Team 1 -> <1--10--20--30--40--44--50--60--70>
Posting Rules
Reply With Quote
Connect With Us