WoW, certain routers causing network problems
by Mike Schramm 
Jan 17th 2008 at 1:45PM
Datth on the forums confirms that WoW is causing some home networks to go down completely. After hearing reports that on some networks, logging into or playing the game would cause the entire network to lose their internet connection, Blizzard asked players to report technical specs if the problem happened. And after researching, they've reported now that the problem supposedly lies with folks who have a "Siemens, 2wire or older model Motorola modem or Netgear router."So if you have one of those and are having this problem, Blizzard has at least identified the cause. They say they're working with the router manufacturers to come up with a fix, but if there really is a problem in the router itself, odds are Blizzard won't be able to hotfix it on their site, so you may have to go to the router's manufacturer for a fix (all that information, when it becomes available, will likely be on their site).
I am surprised, however, that this problem didn't appear before now. Blizzard says that the most recent patch (would that be 2.3.3 and the improvements to load time?) is responsible for "revealing a bug in the hardware," so if the router manufacturers don't release a fix, Blizzard may have to reverse whatever changes were made. At any rate, a fix is coming, no matter where it comes from.
Thanks, Jonate!
Filed under: Patches, Bugs, Blizzard, News items
Reader Comments (Page 1 of 2)
Jonathan Jan 17th 2008 1:59PM
Spending most of my time on the tech forums, this is related to patch 2.3.2. When they disabled Nagels algorithm it caused a huge increase on the amount of traffic that is sent over your network. This stress on the network reveals some flaws in some older hardware. Most people can get by with a firmware update (for the routers that are having problems).
For the people with affected modems, a simple call to the ISP requesting a different modem should take care of them.
It sucks that this happened, but please dont ask to re-enable the algorithm as the Aussies, overseas players might come a knockin.
Another solution is to go post on the suggestions forum to add a toggle to either enable or disable the algorithm. This may help some people with the chronic disconnects.
--Wideruled
Corrodias Jan 17th 2008 2:32PM
Surely it's not just the VOLUME of traffic, as such an issue would have easily been revealed earlier, whenever the user tried to download or upload anything of significant size at a web site. There must be something far more interesting at work, here.
Brennith Jan 17th 2008 2:41PM
Since I can't reply to the reply, I'll reply to the original.
From personal experience, I'll confirm that volume of data would crash my old modem. I had a DSL modem in my last apartment, and had to replace it twice (same model all times) that would crash over volume spikes. It wasn't pure volume, but volume spikes. If I turned in a quest, or if I logged on after a patch, it would down the modem from time to time. It started around 2.1, I believe.
Calaana Jan 17th 2008 6:35PM
As one of your overseas folk, I'm yet to meet anyone down under who doesn't want it re-enabled. I don't know about you American folk, but all Australia got was more lag, not less.
Cal Jan 17th 2008 9:25PM
I'm sorry, but my latency hasn't changed that much all after 2.3.2. Neither have any of my guildie's (they are primarily Oceanian). Sure, there are times when I get ~300ms, but it still usually hangs at ~500ms, which is what I've usually had prior to 2.3.2.
theRaptor Jan 17th 2008 9:51PM
I get lower lag at non-peak times. I have actually regularly seen sub-300ms pings at off peak times, and it doesn't climb much about 500ms on peak now.
xtrout Jan 17th 2008 2:13PM
I had this problem right after the most recent patch, but if cleared up within a couple of days. When I would get disconnected from WoW, my whole internet connection failed. Seems better now.
Lex Jan 17th 2008 2:23PM
Wow; this has been a problem with my router since I started to play post BC release. Patch day would come my computer would bug out and dc and after many tears, deleteing of WTF folders; and reinstall laters; I'm glad to see someone is trying to fix the problem. I still bug out from time to time; so if anyone has any temp fixes please share!
Falconner Jan 17th 2008 3:26PM
I think you may be talking about a different problem. Do you have issues where you'll start to log in, and it will freeze up and DC, or you'll get in far enough but everyone shows as "unknown" ? If so, that for me proved to be a problem with my network card drivers, and when I updated the very old drivers, it was fine from then till now. If you logging in doesn't reset the router, or DC anyone else in the house, it probably isn't this same problem.
Brandon Tilley Jan 17th 2008 2:25PM
I bet this had to do with disabling Nagle's algorithm in a previous patch. Decreases latency but increases network traffic.
Brandon Tilley Jan 17th 2008 2:26PM
Sorry #1 -- posted then read. :
Lab Monkey Jan 17th 2008 2:27PM
I'm having this issue too, with game freezes and occasional disconnects when using in-game mail or interacting with quest givers etc. It causes a simultaneous freeze on my cable tv too. It was fine before the 2.3.2.
What's the issue with the algorithm and the Aussies?
Dave Jan 17th 2008 2:28PM
I have a 2Wire and I haven't had any issues. Must only affect certain models I suppose.
Zumwalah Jan 17th 2008 2:46PM
im willing to bet this only happens on Older routers, where people havent Updated thier Firmware.. i used to have an issue similar to this with COunter Strike.. a simple Frimware Update fixed it.
Nathanael Jan 17th 2008 2:48PM
I ran into this while on XMas vacation with my Macbook Pro. The Mac WoW client apparently sends out a packet during logon that is interpreted by some Linksys Routers as a Service Mode packet, which switches the router into Service Mode, thus D/Cing everyone on the network. Perhaps not the exact same issue, but seemed to be tied to 2.3.
The ultimate solution is to buy a new router, but my temporary solution was to suffer through XMas break playing WoW on a crappy Dell - BLAH!
Moral of the story: Buy a Mac - jj
Phrostbyte/Rejuvenathan/Demondaycare - Gnomeregan
Legendary Legends FTW!
Jay Jan 17th 2008 2:49PM
I've been having latency and discoonnect issue since the patch. Its been soo much of a pain that i haven't been playing nearly as much. i experience it the most when engaged in battle with a mob, or when crafting goods my spell casts get just keep on going but game play freezes.
seanmentzer Jan 17th 2008 2:55PM
Nagle's algorithm (very basically) takes what would normally be a bunch of small packets and makes a big packet out of it. So disabling it will result in an increase in traffic volume, but more importantly causes an increase in the number of very small packets to hit these cheap routers. In routers big and small, small packets are the worst case scenario as far as performance is concerned. I am guessing we are seeing the issue on routers that choke on these small packet sizes, rather than choke on amount of traffic itself.
Pie Pants Jan 17th 2008 10:00PM
Nagle's algorithm will delay actually sending a packet until it's got enough of them to send all in one hit. Although pinging Blizzard's servers from a command prompt reports about 180ms for most Aussies, our in-game ping is more like 500ms at least.
One major Aussie ISP (Internode) has actually set up a SOCKS proxy for WoW players that sets the TCP_NODELAY flag on the connection (which sends packets as soon as they're ready) - effectively bypassing Nagle's Algorithm completely. Even post 2.3.2, this gets us pings of closer to 200ms.
Blizzard should probably just turn Nagle's Algorithm back on for now until they can properly fix it - some Aussie players are now seeing pings of closer to 1000ms for no particular reason since the patch.
guesswho? Jan 17th 2008 3:25PM
the issue quite clearly is the junky switches depicted in the screenshot. buy cisco noob.
Ktok Jan 17th 2008 3:45PM
A few things…
Yes, it was the Nagle Algorithm in 2.3.2. I was one of the people with a crashing modem. Also, yes, it’s been crashing for years when two PCs on the same network try to both download very large files, such as MMO patches.
Second, I did not have the gear that Blizzard has highlighted. They need to add old Version 2 Linksys modems to the list, because replacing mine with a brand new Linksys solved the problem completely.
Lastly, to everyone on the official forums that told us we were crazy and it couldn’t be the 2.3.2 algorithm changes… Ha! We told you so :P