How does one now detect exchange congestion?

[giggity]

Hiya,

Seeing as Telkom now blocks their exchanges from responding to ICMP, TCP and UDP packets, it is impossible to detect whether or not it is the second or the third hop with a high latency. You could always guess and just say, "well the third hop is usually fine...", but often it might actually be the third hop (in my case, I believe it is the Durban MTN CDN -- something that could very likely be congested, especially when Apple releases an update ).

So, is there an actual method to detect congestion (or any problems between you and the exchange for that matter) that isn't an utter guess, other than wasting countless hours on the phone or bugging a busy Telkom technician from the area?

Thanks

 

[Crystal Web]

There are ways. We have a few techniques on our support desk but we'd prefer to keep it quiet for the time being lest those tools are also removed from us as well.

 

[iJasper]

<magic>

 

[adsl2]

<magic>

Keoma, why did you edit your post?

 

[iJasper]

Keoma, why did you edit your post?

Keeping it hostage until Keoma comes back from his holiday

 

[AdrianH]

There are ways. We have a few techniques on our support desk but we'd prefer to keep it quiet for the time being lest those tools are also removed from us as well.

Sharing is caring!

 

[adsl2]

Keeping it hostage until Keoma comes back from his holiday

Luckily the internet never forgets..

 

[iJasper]

Luckily the internet never forgets..

Never forget!

Openweb is the best ISP for crowd funding my new Aston.

 

[Bryn]

Well the initial excuse of avoiding a DDoS attack doesn't hold water anymore. Is Telkom blocking pings solely to prevent exchange issues being detected?

 

[Sinbad]

Well the initial excuse of avoiding a DDoS attack doesn't hold water anymore. Is Telkom blocking pings solely to prevent exchange issues being detected?

I'd suspect that

 

[th0rn]

If first hop does not reply on traceroute, ping 155.239.255.250 . This will give you first hop latency.

 

[Crystal Web]

If first hop does not reply on traceroute, ping 155.239.255.250 . This will give you first hop latency.

Will only work for some exchanges. But yes, this will help, although it remains unclear if this will detect congestion as it moves out from the backhaul side which a normal trace will. If it sits before the backhaul link routers then it's not going to always highlight an issue. May only show possible port problems.

 

[iJasper]

Well the initial excuse of avoiding a DDoS attack doesn't hold water anymore. Is Telkom blocking pings solely to prevent exchange issues being detected?

When was the issue of DDoS first brought up?

 

[ghostR]

If first hop does not reply on traceroute, ping 155.239.255.250 . This will give you first hop latency.

Will only work on new BRAS and certain BNG units.

So will only work about 30-40% of the time.

 

[ghostR]

Will only work for some exchanges. But yes, this will help, although it remains unclear if this will detect congestion as it moves out from the backhaul side which a normal trace will. If it sits before the backhaul link routers then it's not going to always highlight an issue. May only show possible port problems.

Somewhat incorrect, this is the gateway IP for the BNG/BRAS which sits after the exchange so it will test everything between your router, line and exchange for issues.

 

[Crystal Web]

Somewhat incorrect, this is the gateway IP for the BNG/BRAS which sits after the exchange so it will test everything between your router, line and exchange for issues.

Ah it is too. My mistake.

 

[ghostR]

Ah it is too. My mistake.

Although if an exchange doesn't link up to a BRAS/BNG then it won't test anything

 

[Bryn]

When was the issue of DDoS first brought up?

Not sure. Soon after the issue appeared two or three people here claimed to have phoned Telkom about it and were told that it was a measure to prevent a suspected DDoS attack.

 

[giggity]

There are ways. We have a few techniques on our support desk but we'd prefer to keep it quiet for the time being lest those tools are also removed from us as well.

Suppose that it's best that the ISPs keep that rather than the public causing it to be banned.

Well the initial excuse of avoiding a DDoS attack doesn't hold water anymore. Is Telkom blocking pings solely to prevent exchange issues being detected?

Exchanges are practically DDoSed 24/7 since they are the prime hub of thousands of homes to pass through. Can't be the only reason.

Will only work for some exchanges. But yes, this will help, although it remains unclear if this will detect congestion as it moves out from the backhaul side which a normal trace will. If it sits before the backhaul link routers then it's not going to always highlight an issue. May only show possible port problems.

Somewhat incorrect, this is the gateway IP for the BNG/BRAS which sits after the exchange so it will test everything between your router, line and exchange for issues.

Thanks for the clarification.

 

[HavocXphere]

http://mybroadband.co.za/vb/showthread.php/621501-Detecting-a-congested-ADSL-exchange-Guide