Telkom Internet Capped/Uncapped User Feedback (Pt2)

So, breaking down my traceroute, can I assume I'm looking at:

1 <1 ms <1 ms <1 ms 192.168.1.1 -My Router

2 17 ms 17 ms 16 ms ti-224-4-01.telkomadsl.co.za [105.224.4.1] - Sedgefield Exchange

3 43 ms 41 ms 40 ms ti-226-0-246.telkomadsl.co.za [105.226.0.246] - Knysna

4 41 ms 41 ms 41 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13] - George

5 40 ms 40 ms 40 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.153] - Barrack Street Cape Town

Oui?

You would have to as ranger or TelkomZA where hops 3-4 are physically located to be 100% certain but that could be right except hop two is your routers interface on the wan side.
 
Last edited:
You would have to as ranger or TelkomZA where hops 3-4 are physically located to be 100% certain but that could be right except hop two is your routers interface on the wan side.

Doh - of course. Not thinking. Taa.
 
Router LAN port---192.168.1.1
|
Router WAN/ADSL port---ti-224-4-01.telkomadsl.co.za [105.224.4.1]
|
ti-226-0-246.telkomadsl.co.za [105.226.0.246]---What happens next depends on whether you have a old DSLAM using ATM to the ESR ('Multiplexing' the circuits) or a newer Ethernet/IP-DSLAM that can actually pass the IP traffic on to the ESR
 
Last edited:
Router LAN port---192.168.1.1---Router WAN/ADSL port---ti-224-4-01.telkomadsl.co.za [105.224.4.1]---ti-226-0-246.telkomadsl.co.za [105.226.0.246]---What happens next depends on whether you have a old DSLAM using ATM to the ESR ('Multiplexing' the circuits) or a newer Ethernet/IP-DSLAM that can actually pass the IP traffic on to the ESR

D-Link dsl-2750u reports thus:

Mode: ADSL_G.dmt

Type: ATM

Status: Up

Downstream Upstream
Line Coding(Trellis): On On
SNR Margin (dB): 221 120
Attenuation (dB): 195 125
Output Power (dBm): 51 22
Attainable Rate (Kbps): 12064 1148
Rate (Kbps): 4096 512
D (interleaver depth): 1 1
Delay (msec): 0.13 0.25
 
My understanding is that if the DSLAM uses ATM for it's backhaul to the ESR you have a PVC between the DSLAM & ESR and all the PPP sessions then terminate on the ESR. This type of DSLAM works at Layer 2.

If it's a IP based DSLAM you have IP-IP coms between the DSLAM & ESR.
This type of DSLAM would work at Layer 3 as it has some routing functionalities built in.

Hopefully ranger comes along and elaborates more on how the termination between DSLAM & ESR works.
 
My understanding is that if the DSLAM uses ATM for it's backhaul to the ESR you have a PVC between the DSLAM & ESR and all the PPP sessions then terminate on the ESR. This type of DSLAM works at Layer 2.

If it's a IP based DSLAM you have IP-IP coms between the DSLAM & ESR.
This type of DSLAM would work at Layer 3 as it has some routing functionalities built in.

Hopefully ranger comes along and elaborates more on how the termination between DSLAM & ESR works.
Sounds correct, though. Seems we both need a refresher course with all this new technology being installed! :o
 
My understanding is that if the DSLAM uses ATM for it's backhaul to the ESR you have a PVC between the DSLAM & ESR and all the PPP sessions then terminate on the ESR. This type of DSLAM works at Layer 2.

If it's a IP based DSLAM you have IP-IP coms between the DSLAM & ESR.
This type of DSLAM would work at Layer 3 as it has some routing functionalities built in.

Hopefully ranger comes along and elaborates more on how the termination between DSLAM & ESR works.

Thanks. In the meantime you have condemned me to a couple of hours on wikipedia... :D
 
Thanks. In the meantime you have condemned me to a couple of hours on wikipedia... :D

DSLAM - Where all are adsl lines terminate
ESR - Edge Services Router, which the DSLAMs connect to (as well as other services)
ATM - Asynchronous Transfer Mode
PVC - Permanent Virtual Circuit, used by ATM, think of it as a fat pipe all the PPP sessions get carried in.
IP- Internet Protocol, IP-IP basically just means two devices communicate via IP

Wikipedia would be a good start for an overview, if you want to get down to frame,cell, packet level stuff etc just ask and I'll point you in the right direction :D
 
DSLAM - Where all are adsl lines terminate
ESR - Edge Services Router, which the DSLAMs connect to (as well as other services)
ATM - Asynchronous Transfer Mode
PVC - Permanent Virtual Circuit, used by ATM, think of it as a fat pipe all the PPP sessions get carried in.
IP- Internet Protocol, IP-IP basically just means two devices communicate via IP

Wikipedia would be a good start for an overview, if you want to get down to frame,cell, packet level stuff etc just ask and I'll point you in the right direction :D

Mentor me oh great one :). You not far from Stanger :D.

CC me too
 
Come 5pm I get timeout on the second hop (first one after the router) - google services are not accessible when this happens. Everything else seems to work but super slow. What course of action to take? Log a fault? Been like this since yesterday (that I'm aware of).

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\reactor>tracert www.google.co.za

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

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 9 ms 8 ms 8 ms ti-224-0-05.telkomadsl.co.za [105.224.0.5]
4 9 ms 9 ms 8 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
5 9 ms 8 ms 8 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
6 9 ms 9 ms 8 ms cen-pr-01-te7-22-vl2.net.telkomsa.net [105.187.2
49.98]
7 9 ms 11 ms 9 ms jb1-pr-01-te8-3.net.telkomsa.net [105.187.249.2]

8 9 ms 9 ms 10 ms jb1-google-gw.net.telkomsa.net [105.187.249.22]

9 9 ms 9 ms 10 ms 72.14.237.239
10 9 ms 9 ms 10 ms jnb01s07-in-f23.1e100.net [74.125.233.23]

Trace complete.

C:\Users\reactor>tracert www.facebook.com

Tracing route to star.c10r.facebook.com [31.13.90.97]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 21 ms 121 ms 211 ms ti-224-0-05.telkomadsl.co.za [105.224.0.5]
4 9 ms 7 ms 9 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
5 9 ms 9 ms 9 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
6 9 ms 9 ms 8 ms 165.165.216.221
7 177 ms 177 ms 176 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
8 177 ms 178 ms 177 ms ldn-b5-link.telia.net [62.115.35.89]
9 177 ms 177 ms 176 ms facebook-ic-307985-ldn-b5.c.telia.net [213.248.7
3.182]
10 * * * Request timed out.
11 178 ms 177 ms 177 ms msw01.07.lhr3.tfbnw.net [173.252.66.151]
12 177 ms 177 ms 177 ms edge-star-shv-07-lhr3.facebook.com [31.13.90.97]


Trace complete.

C:\Users\reactor>tracert www.mybroadband.co.za

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

1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 10 ms 9 ms 8 ms ti-224-0-05.telkomadsl.co.za [105.224.0.5]
4 9 ms 9 ms 8 ms ti-224-0-06.telkomadsl.co.za [105.224.0.6]
5 9 ms 8 ms 9 ms ti-224-0-13.telkomadsl.co.za [105.224.0.13]
6 10 ms 8 ms 9 ms rrba-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.37]
7 9 ms 9 ms 9 ms rrba-ip-lir-1-gig-7-1-0.telkom-ipnet.co.za [196.
43.52.42]
8 9 ms 9 ms 8 ms rrba-ip-se-2-gig-2-0-0-102.telkom-ipnet.co.za [1
96.43.25.138]
9 9 ms 9 ms 9 ms internet-solutions-gw.telkom-ipnet.co.za [196.25
.127.182]
10 10 ms 9 ms 9 ms ar2-rba-gi0-0.ip.isnet.net [196.26.0.33]
11 10 ms 9 ms 10 ms mi-za-rba-gsrpe2-gi1-1-0.ip.isnet.net [168.209.8
6.250]
12 * * * Request timed out.
13 30 ms 30 ms 30 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
14 31 ms 30 ms 30 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
15 31 ms 32 ms 31 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
16 33 ms 34 ms 33 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
17 29 ms 28 ms 30 ms 197.242.89.170

Trace complete.

C:\Users\reactor>
 
MickeyD, Ponder: Thanks.

Now leave me alone, I have lots of reading to do. :)
 
Top
Sign up to the MyBroadband newsletter
X