Quick Technical Poll

Peon

Peon

Expert Member
Joined
Sep 28, 2006
Messages
3,835
Reaction score
1,123
Location
In my burrow
Hi People

I would please like to gauge quickly some stats.

Im on a 4MB dsl line. The ping to my first gateway is 40ms. On a 384k line im getting 110ms.


I would like to see what other people on other connections are getting. I know our DSLAM is wrotten. Im looking for the numbers to see how bad it is though.

Hartebeespoort:

4MB = 40 ms to gateway.
384k = 110 ms to gateway.
 
Peon said:
Your adsl gateway
Click to expand...

That has absolutely nothing to with the speed of your ADSL line, it has to do with your NIC (Network Interface Card) and speed of your pc.

If you give me a URL to ping, sure, that will be valid, but my ADSL gateway is my router and ofcourse it's going to differ on each single pc out there.
 
no, please just try understand.

Not your lan gateway. *#&(*@&% Your dslam gateway.

Example my dsl gateway is 41.244.0.1, your might be a little different. Just log into you router and see your dsl gateway. Then ping it.
 
Oh... and... Alberton...4 Mbps

Pinging 165.146.204.1 with 32 bytes of data:

Reply from 165.146.204.1: bytes=32 time=10ms TTL=254
Reply from 165.146.204.1: bytes=32 time=13ms TTL=254
Reply from 165.146.204.1: bytes=32 time=13ms TTL=254
Reply from 165.146.204.1: bytes=32 time=8ms TTL=254

Ping statistics for 165.146.204.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 8ms, Maximum = 13ms, Average = 11ms
 
Connection speed has nothing to do with ping rates.
 
Well Supasta, thats why I am doing this because its looks like it is.

It looks like in Telkoms infinite wisdom they are prioritizing connections at the Xanadu exchange in hartebeespoort. 384k gets the ****test. 4mb gets 40ms, and i know the SDM is faulty. Its all the more data i can use when I make the case at telkom.

Ideally I would like more 384k users to post their data.

Thanks Gary, hopefully more people understand what I mean.
 
4mb line, webafrica, prepaid siax shaped, pta east, dslam is right on my yard


Pinging 41.241.128.1 with 32 bytes of data:

Reply from 41.241.128.1: bytes=32 time=9ms TTL=254
Reply from 41.241.128.1: bytes=32 time=9ms TTL=254
Reply from 41.241.128.1: bytes=32 time=9ms TTL=254
Reply from 41.241.128.1: bytes=32 time=9ms TTL=254

Ping statistics for 41.241.128.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 9ms, Average = 9ms

--------------------------------------------------------------------------

Tracing route to dsl-241-128-01.telkomadsl.co.za [41.241.128.1]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms (from router)
2 9 ms 8 ms 9 ms dsl-241-128-01.telkomadsl.co.za [41.241.128.1]

Trace complete.
 
Last edited:
I assume the gateway is the first external hop on a trace? If so:

WebAfrica Int SAIX said:
Pinging 41.244.0.1 with 32 bytes of data:

Reply from 41.244.0.1: bytes=32 time=24ms TTL=254
Reply from 41.244.0.1: bytes=32 time=23ms TTL=254
Reply from 41.244.0.1: bytes=32 time=24ms TTL=254
Reply from 41.244.0.1: bytes=32 time=24ms TTL=254

Ping statistics for 41.244.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 24ms, Average = 23ms
Click to expand...

Axxess Local-only said:
Pinging 41.244.0.1 with 32 bytes of data:

Reply from 41.244.0.1: bytes=32 time=34ms TTL=255
Reply from 41.244.0.1: bytes=32 time=31ms TTL=255
Reply from 41.244.0.1: bytes=32 time=31ms TTL=255
Reply from 41.244.0.1: bytes=32 time=31ms TTL=255

Ping statistics for 41.244.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 34ms, Average = 31ms
Click to expand...

Can't really see why the WebAfrica one is consistently better:confused: Good 5ms consistently. 384 btw pta east. The Axxess one is a pppoe dial-up though...maybe its that.
 
Mine is also 41.244.0.1, I'm on SAIX, Telkom Internet, 4mbps ADSL.

Pinging 41.244.0.1 with 32 bytes of data:

Reply from 41.244.0.1: bytes=32 time=33ms TTL=254
Reply from 41.244.0.1: bytes=32 time=33ms TTL=254
Reply from 41.244.0.1: bytes=32 time=32ms TTL=254
Reply from 41.244.0.1: bytes=32 time=32ms TTL=254

Ping statistics for 41.244.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 33ms, Average = 32ms
 
384K, PTA West on WA Prepaid.

Pinging 41.242.0.1 with 32 bytes of data:

Reply from 41.242.0.1: bytes=32 time=21ms TTL=254
Reply from 41.242.0.1: bytes=32 time=20ms TTL=254
Reply from 41.242.0.1: bytes=32 time=21ms TTL=254
Reply from 41.242.0.1: bytes=32 time=23ms TTL=254

Ping statistics for 41.242.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 20ms, Maximum = 23ms, Average = 21ms
 
Hmm this is interesting, its seems gateway 41.244.0.1 seems to be where the fault is at, not my exchange, very interesting.
 
Centurion, 384, TelkomInternet

C:\Documents and Settings\Home>ping 41.240.128.1

Pinging 41.240.128.1 with 32 bytes of data:

Reply from 41.240.128.1: bytes=32 time=25ms TTL=255
Reply from 41.240.128.1: bytes=32 time=24ms TTL=255
Reply from 41.240.128.1: bytes=32 time=24ms TTL=255
Reply from 41.240.128.1: bytes=32 time=24ms TTL=255

Ping statistics for 41.240.128.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 25ms, Average = 24ms
Click to expand...


Same line, same place WebAfrica Prepaid International

C:\Documents and Settings\Home>ping 41.240.128.1

Pinging 41.240.128.1 with 32 bytes of data:

Reply from 41.240.128.1: bytes=32 time=24ms TTL=255
Reply from 41.240.128.1: bytes=32 time=24ms TTL=255
Reply from 41.240.128.1: bytes=32 time=24ms TTL=255
Reply from 41.240.128.1: bytes=32 time=24ms TTL=255

Ping statistics for 41.240.128.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 24ms, Average = 24ms
Click to expand...

I got that IP from my PPPoE connection as the server IP, is that the one you are looking for a ping to ?! It's also the first IP to come up in a tracert... (its not my (client) IP don't worry :p)
 
Peon said:
Hmm this is interesting, its seems gateway 41.244.0.1 seems to be where the fault is at, not my exchange, very interesting.
Click to expand...
Well its very difficult to tell (at an IP layer). The DSLAM your port is on could be switched through 1 or more ATM switches before its gets to the ESR (Edge Services Router, 1st IP you see downstream). If any of those interconnecting ATM links or ports are running errors, it will mess with your latency/experience.

Also one never knows how the ATM paths are provisioned. I've seen circustances where due to lack of ESR capacity, DSLAMs in GT have been switched to ESRs in KZN.
 
My inside contact tells me there is something wrong with the SDM. In your opinion Roman, how do I present all of this to telkom?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X