Telkom Internet Capped/Uncapped User Feedback (Pt2)

BradleyKZN said:
Google services are down again. Its happening 3-4 times a day.

Ranger, any news on when this will be fixed?
Click to expand...

Experienced this first time today in Outlook asking me to enter my password and nearly fell off my chair as i thought i was hacked :eek: so this just confirms it is not just me and they are aware of it. :)
 
ponder said:
You guys work via CT as far as I'm aware.

TI has IPC connectivity (POPs) in JHB, CT & DBN
Click to expand...

Thanks, I thought so. Just wonder why I always get allocated the Durban and Rosebank DNS servers when I leave it on auto.

When I specify the Cape Town Telkom DNS I swear things seem better. So you kind of confirmed that, thanks.
 
AntiGanda said:
Once again you are so keen to troll, you aren't reading the post or the context.

TI announced that torrents and gaming were not desired, which is why they implemented a very tough shaping regime.

Now ranger says it was not meant to be like that.

Whilst I hope the service does revert to how it was, let's not confuse why and how it came to be like that.
Click to expand...

Nothing is out of context.


AntiGanda said:
So these changes you talk about ("limiting P2P" which manifests itself as a block here in the cape) were implemented as a workaround, and nothing to do with the FUP?

I recall some press releases on this forum about how online gaming was bad, and torrents were going to be restricted. Were they not from TI?

And Telkom will revert to how it was in January and before?
Click to expand...

This is the press release you are referring to http://mybroadband.co.za/news/adsl/107752-telkom-uncapped-adsl-usage-warning.html
There was also an email saying gaming and video streaming is affected, yet this press release says otherwise & they encourage it http://mybroadband.co.za/news/adsl/107752-telkom-uncapped-adsl-usage-warning.html

And the response here by ranger (yes he's not an official TI spokesperson or anything like that) was that the marketing/PR department has the cat by the tail and have no idea what they are talking about. Gaming traffic is actually prioritised contrary to what that press release says. Torrents are shaped during the day depending on network utilisation. Yet you keep going on about this being part of the FUP as if it's fact. If it was part of the FUP then surely the whole country would be affected but somehow KZN is fine. KZN had it's issues (IPC & equipment related) but that has been fixed.

You have also been told that the reason for the current issues in CT & JHB is due to lack of IPC capacity and transmission not being able to provide said capacity timeously (CT) and the current slow or non-existent torrents is a restriction they put in place to alleviate things a bit. Now it's not only TI complaining IPC capacity there are also other ISPs waiting for capacity which you read about on a regular basis when you go look at their feedback threads.

But each time you keep on mentioning that press release & that this must be related to the enforcement of the FUP.

But now Telkom has also said in a press release that they do not have issues getting sufficient IPC capacity. They have also said there they don't have DSLAM backhaul congestion issues.
http://mybroadband.co.za/news/adsl/95373-no-adsl-exchange-congestion-telkom.html

But we all know they have DSLAM backhaul issues on many DSLAMs as there are threads dedicated to this and it's been proven over and over again by people here. It's also been confirmed by Telkom support staff when faults are logged. So do you also believe this article/press release?

The bottom line is the telkom marketing & PR people are completely out of sync with their technical guys, if those in marketing/PR would consult with the technical department(s) before going to press this confusion would not be happening.

Does this look like FUP enforcement to you? (2Mb/s ADSL Line + TI Uncapped bundle)
transmission.png


If you don't believe the above screenshot I'll give you ssh access to my torrent box and you can try it for yourself and that will include the dynamic dns name for my router interface which identifies it as an adsl line so there's no cheating.
 
Last edited:
ponder said:
You guys work via CT as far as I'm aware.

TI has IPC connectivity (POPs) in JHB, CT & DBN
Click to expand...

Not necessarily... Sedgefield will work to George, from a switching and transmission perspective, and then back to Linton Grange in PE. From there it could route to CTN, Durban or JHB. iirc the primary route is to CTN but on the data side it normally routes to the DBN.
 
MickeyD said:
Not necessarily... Sedgefield will work to George, from a switching and transmission perspective, and then back to Linton Grange in PE. From there it could route to CTN, Durban or JHB. iirc the primary route is to CTN but on the data side it normally routes to the DBN.
Click to expand...

Fair enough. I was referring purely to the IP traffic routing. This could easily be determined with a traceroute to see the hops from the ESR to the POP used. If he's routed via DBN he should be fine.

@Grouter, gooi us a traceroute there we can look at.
 
MickeyD said:
Not necessarily... Sedgefield will work to George, from a switching and transmission perspective, and then back to Linton Grange in PE. From there it could route to CTN, Durban or JHB. iirc the primary route is to CTN but on the data side it normally routes to the DBN.
Click to expand...

Hmmm...

I spoke to a telkom tech here a few years ago and he said Sedgefield routes through Knysna. I know we have a fibre link from our exchange through to knysna because I saw it being laid. I also recall an outage here which was due to the whole knysna exchange being down (during the time we were having a lot of load-shedding years ago) and George was unaffected but here in Sedgfield we had no internet.

Whilst I believe what you say MickeyD, as I have no evidence to the contrary and you seem to have "inside knowledge" ;) , I'd still be very interested to know what ipc / pop / whatever serves this little corner of the telkom world.

I had no issues at all whilst Durban guys were suffering with lack of ipc. I have no issues at the moment either, despite there supposedly now being ipc issues in CT. Perhaps some senior telkom exec has a holiday house here in Sedgefield and has made sure that our little fibre link connects directly to Centurion... :D
 
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Grouter>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 192.168.1.1
2 17 ms 17 ms 16 ms ti-224-4-01.telkomadsl.co.za [105.224.4.1]
3 43 ms 41 ms 40 ms ti-226-0-246.telkomadsl.co.za [105.226.0.246]
4 41 ms 41 ms 41 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
5 40 ms 40 ms 40 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.
153]
6 33 ms 33 ms 33 ms 196.43.11.234
7 41 ms 41 ms 40 ms 196.43.25.206
8 42 ms 49 ms 43 ms 196.25.247.26
9 36 ms 35 ms 36 ms css1-ctn-gi0-1.ip.isnet.net [168.209.2.10]
10 41 ms 42 ms 42 ms 196.36.84.154
11 52 ms 52 ms 51 ms CORE.GP-CN-HET-MEE-1.TO.GP-HV-ICT-MEE-1.DFA.P2P.
10G.za [41.84.13.66]
12 52 ms 54 ms 52 ms 41-66-132-246-f6.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.246]
13 53 ms 53 ms 53 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
14 53 ms 58 ms 54 ms row-access-switch1-row3-4.jnb1.host-h.net [197.1
89.193.36]
15 59 ms 59 ms 59 ms 197.242.89.170

Trace complete.

C:\Users\Grouter>
 
Grouter said:
Hmmm...

I spoke to a telkom tech here a few years ago and he said Sedgefield routes through Knysna. I know we have a fibre link from our exchange through to knysna because I saw it being laid. I also recall an outage here which was due to the whole knysna exchange being down (during the time we were having a lot of load-shedding years ago) and George was unaffected but here in Sedgfield we had no internet.

Whilst I believe what you say MickeyD, as I have no evidence to the contrary and you seem to have "inside knowledge" ;) , I'd still be very interested to know what ipc / pop / whatever serves this little corner of the telkom world.

I had no issues at all whilst Durban guys were suffering with lack of ipc. I have no issues at the moment either, despite there supposedly now being ipc issues in CT. Perhaps some senior telkom exec has a holiday house here in Sedgefield and has made sure that our little fibre link connects directly to Centurion... :D
Click to expand...
Knysna works to George as well, so your route will go through the Knysna exchange to George.

I must look around for a routing map...
 
Grouter said:
5 40 ms 40 ms 40 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.153]
Click to expand...

You are being routed via Barrack Street in CT.

wbs = Western Cape, Barrack Street which is one of the DPSU's for the Western Cape.


EDIT: If I do a traceroute to your next hop address my routing looks like this,
Code: 
traceroute 105.224.4.1
traceroute to 105.224.4.1 (105.224.4.1), 30 hops max, 60 byte packets
 1  10.0.0.2 (10.0.0.2)  0.453 ms  0.763 ms  0.754 ms
 2  ti-224-16-01.telkomadsl.co.za (105.224.16.1)  17.166 ms  17.495 ms  21.199 ms
 3  105-229-0-22.dsl.telkomsa.net (105.229.0.22)  24.015 ms  26.124 ms  26.609 ms
 4  105-229-0-13.dsl.telkomsa.net (105.229.0.13)  31.990 ms  45.324 ms  53.909 ms
 5  ndn-ip-hsll-1.telkom-ipnet.co.za (165.165.233.249)  56.359 ms  56.825 ms  75.066 ms
 6  wbs-ip-hsll-2-gig-15-1-0.telkom-ipnet.co.za (196.43.52.154)  82.989 ms  61.456 ms  40.409 ms
 7  165.165.214.214 (165.165.214.214)  59.863 ms  66.510 ms  67.224 ms
 8  * * *
 9  ti-226-0-25.telkomadsl.co.za (105.226.0.25)  159.151 ms *  159.519 ms
10  * ti-224-4-01.telkomadsl.co.za (105.224.4.1)  668.847 ms *

As you can see I get routed via ndn which is one of the DPSUs in KZN, from there the traffic goes via wbs.

So,
You----wbs---ndn---Me

If you were being routed via KZN you would also be going via ndn and not wbs.
 
Last edited:
ponder said:
You are being routed via Barrack Street in CT.

wbs = Western Cape, Barrack Street which is the one of the DPSU's for the Western Cape.


EDIT: If I do a traceroute to your next hop address my routing looks like this,
Code: 
traceroute 105.224.4.1
traceroute to 105.224.4.1 (105.224.4.1), 30 hops max, 60 byte packets
 1  10.0.0.2 (10.0.0.2)  0.453 ms  0.763 ms  0.754 ms
 2  ti-224-16-01.telkomadsl.co.za (105.224.16.1)  17.166 ms  17.495 ms  21.199 ms
 3  105-229-0-22.dsl.telkomsa.net (105.229.0.22)  24.015 ms  26.124 ms  26.609 ms
 4  105-229-0-13.dsl.telkomsa.net (105.229.0.13)  31.990 ms  45.324 ms  53.909 ms
 5  ndn-ip-hsll-1.telkom-ipnet.co.za (165.165.233.249)  56.359 ms  56.825 ms  75.066 ms
 6  wbs-ip-hsll-2-gig-15-1-0.telkom-ipnet.co.za (196.43.52.154)  82.989 ms  61.456 ms  40.409 ms
 7  165.165.214.214 (165.165.214.214)  59.863 ms  66.510 ms  67.224 ms
 8  * * *
 9  ti-226-0-25.telkomadsl.co.za (105.226.0.25)  159.151 ms *  159.519 ms
10  * ti-224-4-01.telkomadsl.co.za (105.224.4.1)  668.847 ms *

As you can see I get routed via ndn which is one of the DPSUs in KZN, from there the traffic goes via wbs.

So,
You----wbs---ndn---Me

If you were being routed via KZN you would also be going via ndn and not wbs.
Click to expand...
Correct, but as you know traffic is routed from DPSU to DPSU.

Sedgefield routes to its DSSU in George and then to its DPSU in PE (Linton Grange) and then to the DPSU in Barrack Street.

Remember the numbering... Sedgefield, Knysna, George are all 044-xxx xxxx. It will route to the primary 04x-DPSU which is Linton Grange and then to the 02x-DPSU.
 
MickeyD said:
Correct, but as you know traffic is routed from DPSU to DPSU.

Sedgefield routes to its DSSU in George and then to its DPSU in PE (Linton Grange) and then to the DPSU in Barrack Street.

Remember the numbering... Sedgefield, Knysna, George are all 044-xxx xxxx. It will route to the primary 04x-DPSU which is Linton Grange and then to the 02x-DPSU.
Click to expand...

Yes 100% correct but that's transparent to the tcp/ip routing, it does not concern itself with the sdh network layout although it still follows that path due to the underlying transport network layout but it's blind to it's workings & layout. His query was related to IPC capacity for Knysna. The IPC capacity sits between the POP (JHB, CT, DBN for TI) and the closest ESR, in this case wbs.

Example,
Telkom-IPC-ADSL-traffic.jpg


Where there could be possible issues for him is between dslam-esr backhaul & esr-esr capacity but he's still going to use the same IPC as the CT guys for example.
 
Last edited:
What fountains of knowledge we have here on MyBB. Thanks guys!
 
ponder said:
Nothing is out of context.




This is the press release you are referring to http://mybroadband.co.za/news/adsl/107752-telkom-uncapped-adsl-usage-warning.html
There was also an email saying gaming and video streaming is affected, yet this press release says otherwise & they encourage it http://mybroadband.co.za/news/adsl/107752-telkom-uncapped-adsl-usage-warning.html

And the response here by ranger (yes he's not an official TI spokesperson or anything like that) was that the marketing/PR department has the cat by the tail and have no idea what they are talking about. Gaming traffic is actually prioritised contrary to what that press release says. Torrents are shaped during the day depending on network utilisation. Yet you keep going on about this being part of the FUP as if it's fact. If it was part of the FUP then surely the whole country would be affected but somehow KZN is fine. KZN had it's issues (IPC & equipment related) but that has been fixed.

You have also been told that the reason for the current issues in CT & JHB is due to lack of IPC capacity and transmission not being able to provide said capacity timeously (CT) and the current slow or non-existent torrents is a restriction they put in place to alleviate things a bit. Now it's not only TI complaining IPC capacity there are also other ISPs waiting for capacity which you read about on a regular basis when you go look at their feedback threads.

But each time you keep on mentioning that press release & that this must be related to the enforcement of the FUP.

But now Telkom has also said in a press release that they do not have issues getting sufficient IPC capacity. They have also said there they don't have DSLAM backhaul congestion issues.
http://mybroadband.co.za/news/adsl/95373-no-adsl-exchange-congestion-telkom.html

But we all know they have DSLAM backhaul issues on many DSLAMs as there are threads dedicated to this and it's been proven over and over again by people here. It's also been confirmed by Telkom support staff when faults are logged. So do you also believe this article/press release?

The bottom line is the telkom marketing & PR people are completely out of sync with their technical guys, if those in marketing/PR would consult with the technical department(s) before going to press this confusion would not be happening.

Does this look like FUP enforcement to you? (2Mb/s ADSL Line + TI Uncapped bundle)
transmission.png


If you don't believe the above screenshot I'll give you ssh access to my torrent box and you can try it for yourself and that will include the dynamic dns name for my router interface which identifies it as an adsl line so there's no cheating.
Click to expand...
I have reported this issue to Telkom Internet via several sources, including the elusive Charl.

Ranger says no faults are open at TI.

The press releases match exactly what we see on the ground in the Cape. This week has been a bit different wrt torrents though.

Since this has been going on since February, it seems unlikely to be a fault under repair as you suggest. Please stop arguing about what we experience. You publish your feedback and I publish mine. OK?
 
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?
 
AntiGanda said:
I have reported this issue to Telkom Internet via several sources, including the elusive Charl.

Ranger says no faults are open at TI.

The press releases match exactly what we see on the ground in the Cape. This week has been a bit different wrt torrents though.

Since this has been going on since February, it seems unlikely to be a fault under repair as you suggest. Please stop arguing about what we experience. You publish your feedback and I publish mine. OK?
Click to expand...
Did you take up ranger's offer of assistance?
 
Grouter said:
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?
Click to expand...
The second one is your IP isn't it?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X