This doesn't work, because the exchange doesn't respond to the tracerts.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
I find that rather hard to believe...This doesn't work, because the exchange doesn't respond to the tracerts.
I find that rather hard to believe...
Whats the exchange IP?
1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.1]
2 * * * Request timed out.
3 7 ms 6 ms 7 ms 41.181.221.253
As per feedback previously received the mentioned BNG is an Alcatell unit and it does not respond to the ICMP request. Third hop should however be an indication for will be directly impacted by higher latency on the ESR port.
I find that rather hard to believe...
Whats the exchange IP?
Well thats a rather lame development....Lots of exchanges now don't respond to tracerts.
It looks like this now:
Code:1 <1 ms <1 ms <1 ms home.gateway.pace.net [192.168.1.1] 2 * * * Request timed out. 3 7 ms 6 ms 7 ms 41.181.221.253
Well thats a rather lame development....
I heard this phenomena is caused by their new software. The package causing the other problems.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.
Does anybody know of a way for me to test if my exchange is congested?
Does ping 155.239.255.250 work?
Users are reporting that exchanges no longer respond to pings. What response did you get? Your best bet is to compare your overall latency during peak and off-peak times. If your latency goes to hell in the evenings then your exchange is probably congested. Your ISP might also be able to help.
Basically telkoms new hardware/profiles at the exchanges block ping requests by default. I'm busy editing my LineTool to work around this.
Z![]()
Well thats a rather lame development....
Does ping 155.239.255.250 work?
Basically telkoms new hardware/profiles at the exchanges block ping requests by default. I'm busy editing my LineTool to work around this.
Z![]()