Comments on: Lowering Latency

By: Tarvitz

Tarvitz — Fri, 21 Jan 2011 19:32:57 +0000

So well, it seems blizzard changed something around thier protocols. WoW data is now broadcasting via multiply address range and ports.
For example we could get the connecton on x.x.x.177:3724 and after restarting on x.x.x.x.175:4000 and so on.

Socat method as it was describe above is broken, but it realy helps within single server ip.

By: Amairgin

Amairgin — Mon, 18 Oct 2010 01:36:38 +0000

Thanks for the replay Upy. Seems as though mine is using port 1119 now and the previous Fail(Dread)Maul server IP of 12.129.254.152 is now either .150 or .153. I'm coming to the thought that it might just be easier to forward all the wow ports to my linux box. IPtables should handle that ok. I've never multi instanced SOCAT before - so I'll give that a crack tonight. AmA

By: upyursh

upyursh — Sun, 17 Oct 2010 22:20:27 +0000

@Amairgin
It looks like Bliz has changed some ports etc I was looking last night and was connecting of port 1900. If this was happening to you then the forwarding wouldnt be occuring. Run your command prompt (in admin on Win7) and type

netstat -b

Check what port wow is connecting to the server on

Upy

By: Amairgin

Amairgin — Sun, 17 Oct 2010 08:31:29 +0000

Hail South Aussie up river Victorian here,

I've been using this method for at least 12 months but patch 4.0 seems to have broken it? None of my friends bother with this technique. Can I ask if it still works correctly for you? Or has blizzard changed ports/realm ip's on us without our knowledge. btw your guide is the best one - the startup scripts make everything just that little bit easier - pro work!

By: Druidious

Druidious — Thu, 28 Jan 2010 01:34:34 +0000

@upyursh Thanks mate, looks like i have a fun weekend ahead of me trying it all out!!

By: upyursh

upyursh — Thu, 28 Jan 2010 01:04:46 +0000

@Druidious
There should not be any reason why it wouldnt work having 2 PCs connected to wow, but you will have to try it, I dont have 2 wow accounts so hard for me too

If you wanted to be connecting to different servers you would need to create multiple socat instances, one for each server.

@SMP
I use this as well, it works well.

@Druidious
You will never get NO latency, if you understand what these fixes are doing you are not actually reducing the connection time to the server. But what you are doing is telling windows to not wait for the response prior to sending the next. You will always have the latency especially when running in Australia etc.

I have had better results using my unix solution simply because the unix Network Stack is much more efficient than windows but whatever works for you

Upy

By: Druidious

Druidious — Thu, 28 Jan 2010 00:52:30 +0000

I guess the next question will be if we used both methods would they work in harmony and provide almost nil latency?
Ie, Home Server for lowering ping + Leatrix for increasing the frequency of TCP traffic???
Hmmm Lets nut this out together!! KGO

By: Druidious

Druidious — Thu, 28 Jan 2010 00:40:10 +0000

@SMP
Whoa, i will definetley give this bad boy a try tonite when i get home!!
That kind of latency reduction would make my life as a healer a great deal easier. The idea behind it seems so simple im amazed no-one has done it earlier???
Now, how to get out of work early today?? ;p

By: SMP

SMP — Sun, 24 Jan 2010 14:44:09 +0000

@SMP Just found a great fix for this. Easy for the non-techno types. Leatrix Latency Fix. We went from 400+ latency to 118 to 130. Easy to install, takes about 30 seconds and a restart and voila, you have the tcp-ack-frequency fix with no hassles. Works with Win 7 and Vista too.

By: SMP

SMP — Fri, 22 Jan 2010 02:41:54 +0000

@Druidious I'd be interested to see an answer to this too. We have a family of 4 WoW addicts and latency can be an issue. We've tried all the other tricks and fixes... no luck.