Mweb IPC problems ?

[kilos]

Can anyone traceroute 41.133.64.1 (their gateway)

Target Name: 41-133-64-1.dsl.mweb.co.za
IP: 41.133.64.1
Date/Time: 2011/07/06 11:44:39 AM

4 13 ms 196-209-0-1.dynamic.isadsl.co.za [196.209.0.1]
5 55 ms [196.38.73.85]
6 45 ms cdsl2-rba-vl150.ip.isnet.net [196.38.73.9]
7 43 ms [168.209.1.140]
8 43 ms [196.26.0.10]
9 45 ms mweb-2.jinx.net.za [198.32.142.25]
10 47 ms TenGigE0-2-0-0.vic-up-1.mweb.co.za [196.22.163.2]
11 127 ms gig-1-0-2.cpt-hscore-3.mweb.co.za [196.22.169.42]
12 98 ms Vlan11.cpt-hscore-1.mweb.co.za [196.28.178.99]
13 68 ms Te1-1-0.92.cpt-ipc-1.mweb.co.za [196.28.179.15]
14 * [-]
15 * [-]
Destination not reached in 35 hops

 

[Tinuva]

kilos, that is actually not a problem, you won't be able to trace that IP from a network other than M-Webs, and even then only from the routers connected to the half duplex MPLS-VPN which provides them them the IPC connectivity.

That IP is actually a IP inside the Half Duplex MPLS-VPN, and while it receives the packets, it doesn't have a route back to where you sending packets from. You can however ping it while you are connected to a M-Web ADSL account.

The Half Duplex MPLS-VPN is not M-Web's idea, its just how Telkom sets up the IPC product.


and no I don't work for M-Web, I just have a very good idea how the IPC product works

 

[kilos]

That IP is actually a IP inside the Half Duplex MPLS-VPN, and while it receives the packets, it doesn't have a route back to where you sending packets from. You can however ping it while you are connected to a M-Web ADSL account.

The Half Duplex MPLS-VPN is not M-Web's idea, its just how Telkom sets up the IPC product.

thanks for the explanation on MPLS & IPC ,another reason could be their firewalls blocking icmp
packets too
Some Mweb clients in George area had problems connecting, was not DSLAM/IMAX as other
ADSL clients were operational.

Cheers
Justin