Tracert on Mweb uncapped

S

suPerb0b

Well-Known Member
Joined
Aug 30, 2005
Messages
205
Reaction score
0
I've been sifting through most of the mweb threads, trying to find out if someone have done a tracert on one of these mweb uncapped accounts, but no luck so far (sooo many pages to go through)

Anyone on mweb uncapped care to do one for me? To google.com would be fine.
 
Something like this:?

Code: 
Tracing route to google.com [74.125.77.147]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    24 ms    20 ms    22 ms  41-132-4-1.dsl.mweb.co.za [41.132.4.1]
  3    33 ms    32 ms    33 ms  ap2522-1-s5-em.mweb.net [196.22.163.206]
  4    32 ms    33 ms    33 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    53 ms    58 ms    69 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  6    34 ms    34 ms    35 ms  tengig-0-3-1-0.mid-1.mweb.co.za [196.22.169.211]
  7   273 ms   255 ms   253 ms  ap2522-1-s7-smg.mweb.net [196.22.163.230]
  8   251 ms   251 ms   251 ms  130.117.136.33
  9   314 ms   407 ms   408 ms  te1-2.ccr01.lon02.atlas.cogentco.com [130.117.50.138]
 10   254 ms   254 ms   254 ms  te4-2.mpd02.lon01.atlas.cogentco.com [130.117.1.18]
 11   250 ms   250 ms   252 ms  google.lon01.atlas.cogentco.com [130.117.14.90]
 12   252 ms   254 ms   251 ms  64.233.175.25
 13   262 ms   261 ms   304 ms  216.239.43.123
 14   264 ms   264 ms   264 ms  72.14.239.199
 15   264 ms   269 ms   270 ms  209.85.255.98
 16   266 ms   268 ms   264 ms  ew-in-f147.1e100.net [74.125.77.147]

Trace complete.
 
I'm an existing MWeb (4Mbps capped) customer in CT, and noticed that I got migrated to the new backbone. All my traffic now goes via Jhb, even to sites hosted in Cape Town (see IOL, below).

I got an identical google tracert as Sheepbot, except my first hop is 29ms (slightly longer distance).

Code: 
Tracing route to www.iol.co.za [196.30.168.79]
over a maximum of 30 hops:

  1     1 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
  2     7 ms     8 ms     7 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  3    28 ms    29 ms    29 ms  ap2621-1-e1-s115-hardcopy.mweb.net [196.22.163.218]
  4    30 ms    29 ms    28 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    33 ms    32 ms    34 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  6    30 ms    29 ms    29 ms  rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.110.73]
  7    29 ms    29 ms    30 ms  rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.43.8.198]
  8    30 ms    31 ms    30 ms  196.43.25.138
  9    31 ms    32 ms    31 ms  ge0-2.br1.jnb6.za.mtnbusiness.net [196.30.16.181]
 10    53 ms    54 ms    54 ms  ge3-0-0.cr1.jnb6.za.mtnbusiness.net [196.30.1.101]
 11    54 ms    54 ms    54 ms  atm4-0-0sub2.cr1.cpt1.za.mtnbusiness.net [196.31.39.30]
 12    53 ms    54 ms    55 ms  srp1-0-0.gw1.cpt1.za.mtnbusiness.net [196.31.249.66]
 13    53 ms    53 ms    53 ms  vlan10.hr1.cpt1.za.mtnbusiness.net [196.30.176.36]
 14    53 ms    54 ms    54 ms  www.iol.co.za [196.30.168.79]

Trace complete.
 
Last edited:
Just to clarify. The MWeb representative pointed out on the Q&A thread, that the new MWeb backbone customers will have IP addresses in the 41.132-135.XX.XX range. I got migrated when I rebooted my modem on 21 March, I didn't ask to be moved. (My IP was previously 41.245.XX.XX).

I also just noticed that tracert to the BBC in London takes 11 hops, which is less than the 14 hops to the IOL site, which is based in the same city as me!?

Code: 
Tracing route to newswww.bbc.net.uk [212.58.226.141]
over a maximum of 30 hops:

  1     1 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
  2     8 ms     9 ms     8 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  3    29 ms    30 ms    30 ms  ap2621-1-e1-s115-hardcopy.mweb.net [196.22.163.218]
  4    29 ms    30 ms    30 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    58 ms    52 ms    45 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  6    30 ms    30 ms    29 ms  rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.110.73]
  7   224 ms   225 ms   224 ms  lon-ip-dir-telecity-gig-4-0-1025.telkom-ipnet.co.za [196.43.18.121]
  8   258 ms   433 ms   432 ms  93-126-245-83.packetexchange.net [83.245.126.93]
  9   242 ms   242 ms   242 ms  212.58.238.129
 10   242 ms   243 ms   242 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
 11   243 ms   243 ms   243 ms  newswww.bbc.net.uk [212.58.226.141]

Trace complete.
 
Uncapped mweb:

Code: 
root@helix:/home/semaphore/Desktop# tracert www.iol.co.za
traceroute to www.iol.co.za (196.30.168.79), 30 hops max, 60 byte packets
 1  10.0.0.2 (10.0.0.2)  1.525 ms  2.283 ms *
 2  * * *
 3  * * *
 4  * * *
 5  * * *
 6  * rndf-ip-hsll-1-wan.telkom-ipnet.co.za (196.25.110.73)  13.548 ms  15.016 ms
 7  rrba-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za (196.43.8.198)  18.350 ms  20.868 ms  22.554 ms
 8  196.43.25.138 (196.43.25.138)  25.510 ms  28.172 ms *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * likitung.iol.co.za (196.30.168.79)  33.652 ms  35.739 ms
 
Gordon_R said:
Just to clarify. The MWeb representative pointed out on the Q&A thread, that the new MWeb backbone customers will have IP addresses in the 41.132-135.XX.XX range. I got migrated when I rebooted my modem on 21 March, I didn't ask to be moved. (My IP was previously 41.245.XX.XX).

I also just noticed that tracert to the BBC in London takes 11 hops, which is less than the 14 hops to the IOL site, which is based in the same city as me!?

Code: 
Tracing route to newswww.bbc.net.uk [212.58.226.141]
over a maximum of 30 hops:

  1     1 ms   <10 ms   <10 ms  home.gateway [192.168.1.254]
  2     8 ms     9 ms     8 ms  41-132-48-1.dsl.mweb.co.za [41.132.48.1]
  3    29 ms    30 ms    30 ms  ap2621-1-e1-s115-hardcopy.mweb.net [196.22.163.218]
  4    29 ms    30 ms    30 ms  vl-92.vic-hscore-1.mweb.co.za [196.22.189.2]
  5    58 ms    52 ms    45 ms  tengig-0-0-0-0-11.vic-up-1.mweb.co.za [196.22.169.225]
  6    30 ms    30 ms    29 ms  rndf-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.110.73]
  7   224 ms   225 ms   224 ms  lon-ip-dir-telecity-gig-4-0-1025.telkom-ipnet.co.za [196.43.18.121]
  8   258 ms   433 ms   432 ms  93-126-245-83.packetexchange.net [83.245.126.93]
  9   242 ms   242 ms   242 ms  212.58.238.129
 10   242 ms   243 ms   242 ms  te12-1.hsw0.cwwtf.bbc.co.uk [212.58.239.222]
 11   243 ms   243 ms   243 ms  newswww.bbc.net.uk [212.58.226.141]

Trace complete.
Click to expand...

One of MTNN's datacentres is in Jhb Rosebank, and the other in new doornfontein. jhb
 
Thanks guys. The reason why I wanted to see a tracert, was that every ISP claim they go over Seacom, but in actual fact it is IS (I know IS has a few links onto Seacom). It looks like mweb probably has their own stm1 link to seacom, since its not going over IS.
 
There is nothing in any of those tracerts that indicates IS. Do you mean SAIX/SAT-3?

Edit: Oh, OK, I get what you mean. I can't figure Seacom in the tracert. Is that 130.117.136.33?

I'm pretty sure that the BBC tracert I posted showing a hop from
rndf-ip-hsll-1-wan.telkom-ipnet.co.za
lon-ip-dir-telecity-gig-4-0-1025.telkom-ipnet.co.za
Click to expand...
is SAT-3.
 
Last edited:
MWEB said:
Hi Gordon_R,

Correct, MWEB does utilise international capacity on both Seacom & SAT3.

MWB.
Click to expand...

So, from now on, different internatonal websites may appear to have different speeds, since MWeb traffic will go via different routes, depending on the shortest distance, and varying load patterns. Could be interesting (and puzzling) if dynamic balancing kicks due to congestion and breakdowns...

I was curious which route is Seacom. Can anybody confirm that it is via 130.117.136.33, since that looks vastly different from the SAT-3 route (or maybe its via SAFE too)?
 
Gordon_R said:
I'm an existing MWeb (4Mbps capped) customer in CT, and noticed that I got migrated to the new backbone. All my traffic now goes via Jhb, even to sites hosted in Cape Town (see IOL, below).
Code: 
Tracing route to www.iol.co.za [196.30.168.79]
over a maximum of 30 hops:

  7    29 ms    29 ms    30 ms  [B]rrba[/B]-ip-lir-1-gig-0-0-0.telkom-ipnet.co.za [196.43.8.198]
[/QUOTE]
 
Mweb's IP Connect is located in Rosebank by the looks of things. The IPC gives them access to Telkoms ADSL infrastructure. So all traffic from Mweb adsl users around the country will get routed to JHB in order for it to get connected to the Mweb backbone. 

My ISP's IPC is located in CT so all my traffic first gets routed to CT and then out from there. Nothing one can really about this except establish an IPC in every province which would be costly to say the least. IPC is a kuk product we are stuck with for now I'm sorry to say.
Click to expand...
 
Gordon_R said:
Edit: Oh, OK, I get what you mean. I can't figure Seacom in the tracert. Is that 130.117.136.33?
Click to expand...

Seacom and SAT-3 are Layer-2 services, they won't have any IP address. to distinguish them
 
Actually of all these traceroutes above, none goes over IS.

The google trace goes over seacom and enters Cogentco's (Congentco is the cheapest international Tier1, but don't get me wrong, they are pretty damn decent for their price) network which is the 130.x.x.x ips.

Then the IOL trace goes over SAIX Gold local transit link.

Now the BBC link is interesting, that looks like it is going over SAIX Gold international transit which makes use of SAT3.
 
Tinuva said:
The google trace goes over seacom and enters Cogentco's (Congentco is the cheapest international Tier1, but don't get me wrong, they are pretty damn decent for their price) network which is the 130.x.x.x ips.
Click to expand...

Thanks Tinuva. There were concerns that SEACOM routing would be somewhat slower than SAT3, but this does not appear to be the case in these examples.

There are a few extra hops on the SEACOM route to google (compared to BBC via SAT3), and a different Tier1 may explain some of the changes that users have experienced (see other threads).
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X