MWEB Gaming Feedback

Peer 2 peer gaming on Xbox Live is a mess. We can't play with a Mweb guy in the lobby if the host is SAIX or vice versa.
 
So anyway, i tried DRTCP program, set my MTU to 960, 1100, 1400 and a few in between.
NO CHANGE.

I am running win7 x64, on 384 line with mweb uncapped shaped. I did run as administrator and restarted my pc before checking. I also have the latency fix installed.
So what now Will?

Oh yeh, btw, 1gig mweb unshaped account = good latency
What does that tell anyone?

Also, have the blizzard hotfix been released? cause it doesnt seem to have any effect here.

Edit: As SOON as the port which the server uses gets changed, BOOM instant 290ms. As soon as the default port is used BOOM 3-4k latency with spikes. Im no network genius but that has to tell you something.
I know we have been over this before, but when the only change is the port and instant good latency it has to mean something more concrete....
 
Last edited:
Is there anyone that minds giving us a link to this DrTCP fix thingy someone suggested? i downloaded but pretty unsure to what i should enter in some of the fields, such as tcp receive window
 
Peer 2 peer gaming on Xbox Live is a mess. We can't play with a Mweb guy in the lobby if the host is SAIX or vice versa.

Bokka this is due to MWeb cancelling all paid peer-to-peer connections. So those links have to now run Internationally ie crazy latency...
 
Well well, this is a turn up for the books. Set my MTU to 960 and lo and behold, my latency on MWEB uncapped has dropped down to 400-600ms in heavily populated areas and battlegrounds. Responsiveness is quite quick as well, so it looks like the "higher priority" is still in effect for most of WoW traffic. Lets hope it stays like this, I was getting pretty despondent!

Will test it out in a 25 man raid tonight which starts in about 30 min (DST, I haet j00!)
 
Good luck Steven :)

You jinxed it =(

It is fine for 95% of the time, I just get a weird lag timeout every now and then where everything just goes dead for about 20-30 seconds, get disconnected from vent and possibly from WoW. I suspect this has to do with severe packet loss which is a side product of lowering MTU (which decreases packet size which means more packets), so this isn't what I would call a permanent solution. However, it is working really nicely other than that 1 problem. Maybe I shall keep a lower MTU after this lag schite is over with just for better responsiveness.
 
hmm im still trying to figure out what to set my TCP Receive window to.... ive tinkered around with the MTU but so far ive yet to find a decent setting :/ any suggestions?
 
Well A: im using the Dr.TCP incorrectly or B: im just damn unlucky... i tried the following MTU's 1400 1000 960 900 750 and most of them gave the same results, my latency would go down then shoot right back up... absolutly no stability... it would go from 1400ms to 900ms then shoot back to 2000ms

By the time stabiltiy is reached ill be A: bored of wow or B: dead from frustration or C: just plain insane...
 
Well A: im using the Dr.TCP incorrectly or B: im just damn unlucky... i tried the following MTU's 1400 1000 960 900 750 and most of them gave the same results, my latency would go down then shoot right back up... absolutly no stability... it would go from 1400ms to 900ms then shoot back to 2000ms

By the time stabiltiy is reached ill be A: bored of wow or B: dead from frustration or C: just plain insane...

i just changed the mtu manually

in Command Promt With admin Rights

type : netsh interface ipv4 show subinterfaces

to show your network inteface's name

To change or set a new MTU value, execute the following command:

netsh interface ipv4 set subinterface "Local Area Connection" mtu=NNNN store=persistent

Where NNNN is the new value
 
Last edited:
Essentially those programs do the wetwork for you.

Just reporting back - after that serious d/c earlier on in the night, raiding was perfect all the way to the end. So it appears to have worked for the most part for me!
 
I also changed my MTU to 960. Only got one DC. Rest of the night was fine. I just have one question for Mweb: I know that latencies in the 280-320ms is possible in South Africa, I got it most of the time on my 384k shaped uncapped service. Will we see that again? Were the Mweb tech guys able to get hold of Blizzard?
 
Change ISP's

You seriously don't want them to block torrents, thats how you get your patch data! And it is part of the WoW traffic so it will go from unplayable to ummm...unplayable? :P

What I am finding works well at the moment is an AxxessLite account, R19 a GB and because WoW traffic is minimal it doesn't burn through it quickly.

If this holds up for much longer, I might switch to another ISP. As much as I love MWEB, I don't see the point of paying for something I can't use, which for me is playing WoW in a hardcore raid guild 5 nights a week.

Let's see what this morning's rolling restart brings, hopefully a hotfix.

I just cancelled Mweb and changed to Axxess Lite too. R19 per GB and unshaped - getting the lowest pings (~ 300ms) I've ever got playing on US servers. :D
 
Well I played WOW last night on mweb for the first time in weeks and all was groovy sub 400 ms all night not sure who fixed what but it worked for me
hopefully tonight will be a repeat performance.

ps.. I would leave M-Web too but it would involve a Gun to my head and a few big bruisers with low foreheads.
 
Here is something interesting, Monday, my ping was f^&ked(changed my account to a prepaid shaped axxess account), but Tuesday, I had my Mweb account in and all was fine, 250-300 ping after 6. There was no changes on my network, it was before the Wednesday Weekly WoW maintenance, and there was no hotfixes applied to the game

last night, 11 PM got back from work and all is fine, will check today again when I get off from work.

as I said, I did absolutely NOTHING on my network or my router or anything on my system, and all was fine for 2 days now, today will be the third....

Will I hope this helps with the fault finding............

I live in Durbanville, Kenridge area, CT
 
Here is something interesting, Monday, my ping was f^&ked(changed my account to a prepaid shaped axxess account), but Tuesday, I had my Mweb account in and all was fine, 250-300 ping after 6. There was no changes on my network, it was before the Wednesday Weekly WoW maintenance, and there was no hotfixes applied to the game

last night, 11 PM got back from work and all is fine, will check today again when I get off from work.

as I said, I did absolutely NOTHING on my network or my router or anything on my system, and all was fine for 2 days now, today will be the third....

Will I hope this helps with the fault finding............

I live in Durbanville, Kenridge area, CT

Piet, your good latency has nothing to do with mweb fixing something, cause they didnt. Your tunneling service "WTfast" found a way to bypass whatever was wrong on the network. Mine is good now also on WTfast with the new port they implemented to bypass the port trouble (call it what you will)
 
Sillicur please test tonight for me without your tunneling service and any mtu change applied.
 
Top
Sign up to the MyBroadband newsletter
X