Mr mweb rep thingie

Thanks so much :D WIll try tonight, Xbox live wants a MTU of like 1500 something =/

Hmm, my Xbox live works 100% on a MTU of 1492. Same router, do you use a PPPoE connection to your router? Let me know if you're having troubles connecting, I can try to help since I have the same router.
 
Hmm, my Xbox live works 100% on a MTU of 1492. Same router, do you use a PPPoE connection to your router? Let me know if you're having troubles connecting, I can try to help since I have the same router.

Yip put my router in bridge mode and dial a PPPoE. I can make the connection, but when it queries Xbox Live connection, it gives some error about the MTU rate.
 
Yip put my router in bridge mode and dial a PPPoE. I can make the connection, but when it queries Xbox Live connection, it gives some error about the MTU rate.

Oof, my setup is different. The router is in routing mode, so the isp details and whatnot are entered into the router and I dont have to dail, I'm afraid I dont quite know how to set Live up with bridge mode, but I figure you'd have to enter the isp details on the Xbox, since it would need to dail to connect. The router setup pages are also different for Bridge/PPPoE only connections. ;\
 
Oof, my setup is different. The router is in routing mode, so the isp details and whatnot are entered into the router and I dont have to dail, I'm afraid I dont quite know how to set Live up with bridge mode, but I figure you'd have to enter the isp details on the Xbox, since it would need to dail to connect. The router setup pages are also different for Bridge/PPPoE only connections. ;\

Hmmm, I might have to swap back to routing mode than ;/
 
I posted an example showing that the problem is likely on the Telkom circuit (tracert shows where is congestion is).
http://mybroadband.co.za/vb/showthr...4mb-uncapped&p=4118645&viewfull=1#post4118645

Tracing route to mweb.co.za [196.2.63.110] over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 13 ms 9 ms 41-133-108-1.dsl.mweb.co.za [41.133.108.1]
3 164 ms 165 ms 165 ms tengig-0-0-0-104.vic-ipc-2.mweb.co.za [196.22.163.218]
4 187 ms 188 ms 187 ms vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
5 174 ms 181 ms 182 ms tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
6 141 ms 139 ms 142 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.8.249]
7 226 ms 229 ms 208 ms 196.43.39.58
8 253 ms 255 ms 256 ms tiscali-gw.telkom-ipnet.co.za [196.25.55.178]
9 * * * Request timed out.
10 * * * Request timed out.
11 * * ^C


It is MWEB's circuit... (It might be Telkom who owns the infrastructure, but who is operating it)
 
Last edited:
Tracing route to mweb.co.za [196.2.63.110] over a maximum of 30 hops:

I'm not sure what's supposed to indicate. We all know that mweb.co.za is hosted on a separate backbone, and that it does not respond to pings. Try www.mweb.com or pop.mweb.co.za or www.dstv.com.

We know that the MWeb backbone is sometimes congested, but when I test it now I get 30-50ms (from CT-Jhb).

Probably both networks are congested this week, leading to the bad user experience, but it's not clear who is going to ever fix the problem...
 
is the mweb news server working? been trying to connect for over an hour and so far nothing
 
Top
Sign up to the MyBroadband newsletter
X