MWEB Gaming Feedback

Beanbag said:
Now I know that Blizzard wont ban you if you use it, its just that their EULA doesnt seem to approve.


Oh well, since when do people actually obey a EULA anyways?
Click to expand...

Can any gamer HONESTLY tell me they read ANY of the EULA's they agree to?

Anyway, back on topic, in light of the cover story regarding Exchange congestion, could Telkom not be possibly prioritising SAIX accounts on overloaded exchanges? I generally don't have lag issues, so it does seem to depend on where one lives etc, not just MWeb...
 
Last edited:
Ignorance of the EULA doesn't nullify the terms that you accept when you click "I Agree".

Whether Blizzard (or any company) decides to pursue, they are well within their rights to do so.

Just to add: AxxessLite with lower MTU works a treat lol, all I need is for MWEB to come to the party once more.
 
Does anyone here play HoN? Does this still happen when using Mweb:

 
On a non-WoW topic anyone who is interested in winning a copy of Blackops should visit the MWEB Facebook page :)
 
On a non-WoW topic I would like some answers to my questions (post #859, its the long one, you cant miss it) on this page Will.... Or even just an acknowledgement of them. When I created a fault ticket for my latency in October, I was told that they are going to close the ticket and that Mweb will communicate with the customers via the MyBroadband forums on the WoW latency issue.
 
@Beanbag

I'm not sure why the MTU fix works, it seems that the Wow traffic is quite prone to packet loss and adjusting the packet size addresses some of the symptoms of this. Why the packetloss occurs is a question I can't answer right now. If it was related to shaping I would have expected the testing done with unshaped accounts to deliver a successful fix, as with attempts we have made to completely bypass our traffic managers for connections to certain realms. I am however not convinced that this testing was conclusive and I now have two 4mb accounts available to me, one shaped and one unshaped that I will do extensive testing with over this weekend to produce some conclusive results in this area.

We have not approached Blizzard directly, from everything I have read in terms of responses from the major UK isps affected they are not offering any significant support to isps on the matter. Our networks team need to take the matter further with the vendors of our traffic management systems who should have all the neccesary expertise to tackle the issue and may very well be dealing with it already. As soon as I have feedback on the progress of this I will let you know.

In terms of your tracert results there is something not quite right with that trace, but it's possible there was a some brief network issue involved at the time this was taken and it's not indicative of the test reuslts we've been seeing. . Hop 8 should actually be the London landing point for our Seacom traffic as you can see in the trace below, you will also note from my trace that there is almost no change in latency from there to the next hop so I think it's safe to say the geo trace you are looking at for this IP is misreporting it's location, seeing as how it would be physically impossible for the traffic to move from London, to the US and then back in a single hop.

1 1 ms <1 ms <1 ms home.gateway [192.168.0.254]
2 7 ms 7 ms 7 ms 41-133-112-1.dsl.mweb.co.za [41.133.112.1]
3 9 ms 8 ms 8 ms 196-28-178-202.adsl.mweb.co.za [196.28.178.202

4 69 ms 63 ms 52 ms gig-0-0-0.vic-hscore-3.mweb.co.za [196.22.169.

5 30 ms 31 ms 30 ms 196.22.169.61
6 35 ms 33 ms 32 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.
225]
7 34 ms 33 ms 33 ms tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.21

8 267 ms 266 ms 266 ms pos-0-0-0-0.lon-1.mweb.co.za [196.22.163.230]
9 276 ms 275 ms 276 ms 149.6.98.17
0 287 ms 417 ms 421 ms te7-2.ccr01.lon01.atlas.cogentco.com [154.54.3
5]
1 * 275 ms 275 ms te1-2.mpd01.lon01.atlas.cogentco.com [130.117.
5]
2 267 ms 267 ms 269 ms ldn-b4-link.telia.net [213.248.70.237]
3 276 ms 276 ms 276 ms ldn-bb2-link.telia.net [80.91.251.14]
4 286 ms 283 ms 283 ms prs-bb2-link.telia.net [80.91.247.240]
5 285 ms 286 ms 286 ms prs-b4-link.telia.net [80.91.251.45]
 
just got mweb account ,seems my router was broken my adsl was working all along >.<

so far soo good on 512kps line and 512kps mweb uncapped account shaped

my ms atm is 318 waiting for wintergrasp to start to test it fully, using reduce your lagg proxy
 
Last edited:
still crap lag,ping for BFBC2 on igame is 130 Wage:400 FFL:200 SGS:500.

Seems i'm going to be playing on igame for a while.
 
well with all this fiddling from mweb, now my wow ping is fine but everything else is f%^&*d, http downloads, torrents, etc etc yay <3 this
 
need to rememer to set the server eu test something on reduce the lagg website, and ping takes like up to 30min to settle in normally .

yeha i did not do any mtu fixes to connection to get my normal ms, im trying icc 25 tonight, did 10 onyxia, toc 10 and voa 25 fine.
 
Last edited:
ok syndragosa 25 man herioc was fine no lagg or dc, just dc when pullign both groups of trash maxed the 512kps connection , was about 350ms fight.

lk hc get some spikes getting near the 512kps limit, did not dc at all just spike or 2 , all is fine :)
 
@Will, maybe this aint mweb related but everytime I try connect to Eve through their client ( patch or game ) , my line disconnects. Any ideas?
 
i jsut hooked up a 5GB shaped account from mweb and since then i have been unable to play wow on it.
I log in, success, select one of my toons, loading screen, then sits there for ages, i either eventually log in with seriously bad latency, with nice fat lag spikes ranging from 500ms to 1600ms, or i jsut get disconnected..
Is anyone else having this with mweb, on my WA account everything is 100%.
i called and then they were telling me i must get an unshaped line and my line is noisy nfrom the test they did.but yet i still get 300ms on WA shaped account. Maketh no senseth!!

please help me out here, wtf is goin on!?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X