Problems accessing TENET network

[battletoad]

Everyone of uct.ac.za, sun.ac.za, uwc.ac.za, wits.ac.za times out for me. Traceroute tells me that the last node before the timeout is 168.209.6.131, which I will post shortly, but this is the weirdest:

user@user-pc:~$ traceroute 192.11.235.44 (UWC ip)
traceroute to 192.11.235.44 (192.11.235.44), 30 hops max, 60 byte packets
1 laptop.local (192.168.1.10) 5.788 ms 5.763 ms 106.264 ms
2 * * *
3 172.17.32.9 (172.17.32.9) 106.227 ms 106.236 ms *
4 * * *
5 192.168.102.2 (192.168.102.2) 377.991 ms 377.977 ms 377.966 ms
6 172.17.32.17 (172.17.32.17) 377.914 ms 55.418 ms 55.410 ms
7 8ta-150-177-02.telkomadsl.co.za (41.150.177.2) 125.081 ms 125.036 ms 185.108 ms
8 196.25.10.85 (196.25.10.85) 188.242 ms 188.259 ms 188.236 ms
9 nngy-ip-hsll-1-gig-4-0-0.telkom-ipnet.co.za (196.43.51.254) 188.240 ms 132.912 ms 132.868 ms
10 if-3-0-1.core1.cov-cochin.as6453.net (116.0.85.1) 378.438 ms 378.376 ms 318.407 ms
11 if-14-0-0.core2.mlv-mumbai.as6453.net (209.58.105.37) 418.015 ms 417.993 ms 417.936 ms
12 if-10-3-1-0.tcore2.mlv-mumbai.as6453.net (180.87.39.61) 336.673 ms 336.626 ms 336.633 ms
13 if-2-2.tcore1.mlv-mumbai.as6453.net (180.87.38.1) 419.347 ms 419.346 ms 419.265 ms
14 if-9-5.tcore1.wyn-marseille.as6453.net (80.231.217.17) 397.884 ms * 397.746 ms
15 * if-8-1600.tcore1.pye-paris.as6453.net (80.231.217.6) 330.331 ms 330.252 ms
16 if-2-2.tcore1.pvu-paris.as6453.net (80.231.154.17) 399.257 ms 399.261 ms 399.169 ms
17 80.231.153.66 (80.231.153.66) 399.186 ms 399.152 ms 385.576 ms
18 vlan80.csw3.paris1.level3.net (4.69.168.190) 417.591 ms^C

Seriously, you send me to France by way of Mumbai just to get to UWC? Anycase, the other traceroute:

user@user-pc:~$ traceroute www.uct.ac.za
traceroute to www.uct.ac.za (137.158.158.44), 30 hops max, 60 byte packets
1 laptop.local (192.168.1.10) 3.273 ms 3.258 ms 3.251 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 * 172.17.32.17 (172.17.32.17) 418.744 ms 418.703 ms
7 8ta-150-177-02.telkomadsl.co.za (41.150.177.2) 418.627 ms 614.870 ms 614.842 ms
8 196.25.10.85 (196.25.10.85) 614.648 ms 614.559 ms 614.558 ms
9 196.43.11.218 (196.43.11.218) 614.551 ms 614.544 ms 614.507 ms
10 196.43.25.206 (196.43.25.206) 614.425 ms 614.450 ms 614.428 ms
11 196.25.247.26 (196.25.247.26) 614.491 ms 614.470 ms 614.384 ms
12 168.209.6.131 (168.209.6.131) 614.375 ms * 168.209.2.131 (168.209.2.131) 525.008 ms
13 * * *
14 * * *
15 * * *
.
.
.
30 * * *

Also, I seem to have a new IP, one in the 154 range that I've never seen before.

 

[Tinuva]

Uh, you tracing the wrong ip for UWC.

Instead of tracing to 192.11.235.44 try tracing to 196.11.235.5.

Big difference between 192.x and 196.x

 

[battletoad]

Missed that! :O
Still times out though to any uni.

 

[Tinuva]

Ok you are not the 1st case I know off having problems on TelkomMobile. There may actually be a routing issue somewhere, because we have a client having issues to access their website hosted by Web Africa from their TelkomMobile internet connection.

Not 100% sure where and how to troubleshoot this one yet.

 

[ginggs]

Also see:
http://mybroadband.co.za/vb/showthread.php/624555-8ta-Killing-Banks

 

[battletoad]

Ok, everything works fine now, and I'm on the 154 range.

Seems reminiscent of the very same issue last year when TelkomMobile started moving subscribers to the 41.15x range. They fixed it quickly enough though.

EDIT: this issue only affect those in Cape Town. Their helpdesks in Jozi had no probs.