Peering to MWEB

Durandal said:
This whole thing just confuses the heck out of me, to be honest. All I know is that our speeds at work have plummeted and WA can't explain it. My iBurst is great in comparison. Am thinking of bringing modem to work and using it as backup.
Click to expand...

Same here dude. I am just recommending the MWEB R79 special or Afrihost R29 special now to my friends. Then I know they are save, with CODBO at least.

I bought my game yesterday and installed it, did the update @ +-100KB/s and got around 60-140 pings, depending on which server I played. All the servers say they are in jhb, but some where a lot less laggy than others. Don't know if it has anything to do with the poor telkom guys that tried to play as well... 999pings. :wtf:

r00igev@@r said:
OK, finally got to the bottom of the MWEB config from our shoeless friend. MWEB has a seperate ASN for Cape Town and Johannesburg (effectively two networks).
Click to expand...

Meaning? JHB guys goes through MTN and CPT guys through VC?
 
just got my copy of COD BO this morning wondering if its worth installing over the weekend to play or if the
servers are gonna be stong enough to keep up ... sigh back to BFBC2 with new maps soon :}
 
Deep78 said:
just got my copy of COD BO this morning wondering if its worth installing over the weekend to play or if the
servers are gonna be stong enough to keep up ... sigh back to BFBC2 with new maps soon :}
Click to expand...

Sense: This makes none. ;)

r00igev@@r said:
No, In JHB you will attach to the MWEB JHB network via JINX and in Cape Town you will attach to the MWEB Cape Town network via CINX.
Click to expand...

Kewl, I have yet to test after the fix was released, but will only be able to test on sunday.
 
Sorry but this issue have not been sorted out yet, I'm in Centurion.

1 2 ms 1 ms 1 ms 192.168.10.10
2 70 ms 44 ms 143 ms iburst-41-213-16-1.iburst.co.za [41.213.16.1]
3 66 ms 49 ms 51 ms 192.168.0.97
4 69 ms 44 ms 43 ms 192.168.0.113
5 85 ms 56 ms 53 ms iburst-41-213-126-19.iburst.co.za [41.213.126.19

6 71 ms 68 ms 69 ms ge2-24.gw14.jnb6.za.mtnbusiness.net [66.8.42.21]

7 111 ms 89 ms 94 ms 196.41.133.177
8 112 ms 105 ms 108 ms 196.41.144.36
9 112 ms 99 ms 94 ms www.mweb.co.za [196.2.63.110]
 
Gimli said:
Sorry but this issue have not been sorted out yet, I'm in Centurion.

1 2 ms 1 ms 1 ms 192.168.10.10
2 70 ms 44 ms 143 ms iburst-41-213-16-1.iburst.co.za [41.213.16.1]
3 66 ms 49 ms 51 ms 192.168.0.97
4 69 ms 44 ms 43 ms 192.168.0.113
5 85 ms 56 ms 53 ms iburst-41-213-126-19.iburst.co.za [41.213.126.19

6 71 ms 68 ms 69 ms ge2-24.gw14.jnb6.za.mtnbusiness.net [66.8.42.21]

7 111 ms 89 ms 94 ms 196.41.133.177
8 112 ms 105 ms 108 ms 196.41.144.36
9 112 ms 99 ms 94 ms www.mweb.co.za [196.2.63.110]
Click to expand...

www.mweb.co.za is accessible via the Cape Town data centre. Rather try a tracert to www.news24.com
 
What l want to know is what is the deal between lburst and mtn? Or is it completely up to mweb. Surely they can't decide that mtn should carry traffic from lburst

Sent from my HTC Desire using MyBroadband Android App
 
@r00igev@@r. surely by now you have had enough time to figure this one out, or are you still shrugging your shoulders?
 
This looks better.


tracert www.mweb.com

Tracing route to www.mweb.com [196.28.79.33]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.10.10
2 67 ms 43 ms 45 ms iburst-41-213-16-1.iburst.co.za [41.213.16.1]
3 65 ms 57 ms 53 ms 192.168.0.97
4 66 ms 54 ms 54 ms 192.168.0.114
5 72 ms 53 ms 163 ms iburst-41-213-126-26.iburst.co.za [41.213.126.26
]
6 72 ms 48 ms 48 ms 41.160.155.177
7 70 ms 43 ms 43 ms mweb-2.jinx.net.za [198.32.142.25]
8 70 ms 48 ms 49 ms ap3660-1-S0-0-JINX.mweb.net [196.22.163.2]
9 71 ms 43 ms 48 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]
10 76 ms 53 ms 54 ms tengig-3-1.vic-core-sw1.mweb.co.za [196.22.169.6
6]
11 72 ms 51 ms 51 ms 135.75.28.196.netactive.net [196.28.75.135]
12 80 ms 74 ms 69 ms viking2.mweb.net [196.28.75.7]
13 68 ms 49 ms 49 ms bc-wwwcl.mwebhosting.net [196.28.79.33]

Trace complete.



tracert www.mweb.co.za

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

1 1 ms 1 ms 1 ms 192.168.10.10
2 165 ms 54 ms 54 ms iburst-41-213-16-1.iburst.co.za [41.213.16.1]
3 66 ms 44 ms 43 ms 192.168.0.97
4 68 ms 46 ms 53 ms 192.168.0.114
5 71 ms 49 ms 173 ms iburst-41-213-126-26.iburst.co.za [41.213.126.26
]
6 69 ms 59 ms 58 ms iburst-41-213-126-22.iburst.co.za [41.213.126.22
]
7 74 ms 49 ms 59 ms mweb-2.jinx.net.za [198.32.142.25]
8 86 ms 69 ms 59 ms ap3660-1-S0-0-JINX.mweb.net [196.22.163.2]
9 77 ms 59 ms 50 ms vl-11.vic-hscore-1.mweb.co.za [196.22.169.227]
10 71 ms 48 ms 49 ms tengig-1-1-0.vic-hscore-3.mweb.co.za [196.22.169
.62]
11 115 ms 108 ms 94 ms gig-1-0-3.cpt-hscore-3.mweb.co.za [196.22.169.46
]
12 131 ms 94 ms 93 ms 196-28-178-99.adsl.mweb.co.za [196.28.178.99]
13 116 ms 94 ms 103 ms 196-28-178-66.adsl.mweb.co.za [196.28.178.66]
14 110 ms 109 ms 94 ms 196.41.144.36
15 118 ms 93 ms 109 ms www.mweb.co.za [196.2.63.110]

Trace complete.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X