Need some info please

P

PoiZoNouZ

Expert Member
Joined
Feb 13, 2004
Messages
1,770
Reaction score
3
Location
Bryanston
Ok, I have done my research a bit, and I am currently using DSL384, with Telkom as my ISP. All in all it works out to R 800p/m, not too bad. The max I have used is 2.6Gb in a month, not really a power user. I play a lot on local CS:S servers, Kazaa a bit and do general browsing and e-mail. D/L speeds are 38-40k/sec my pings average 30-60. What I want to know, because I'm moving and dont want to install a phone line if I dont have to, is:
1. What are D/L and U/L speeds like?
2. What can I expect my pings to be to local servers?
3. How is it for surfing compared to ADSL?
4. Could somebody ping 196.2.128.100 , 196.2.128.99 and 196.4.79.6 for me?

Your help is appreciated, I'll be moving to Sunninghill/Paulshof, whats the signal like there?
 
Last edited:
PoiZoNouZ said:
1. What are D/L and U/L speeds like?
2. What can I expect my pings to be to local servers?
3. How is it for surfing compared to ADSL?
4. Could somebody ping 196.2.128.100 , 196.2.128.99 and 196.4.79.6 for me?
Click to expand...

1. Running multiple threads D/L 80 - 130 KB/s avarage 100 KB/s
2. 50 - 200 on local
3. burst to 60 KB/s on large pages
4. Can do tomorrow night, but I'm sure someone else can help you there.

I'm in Kyalami.
 
The second two kept timing out :confused:

Pinging 196.2.128.100 with 32 bytes of data:

Reply from 196.2.128.100: bytes=32 time=140ms TTL=116
Reply from 196.2.128.100: bytes=32 time=80ms TTL=116
Reply from 196.2.128.100: bytes=32 time=88ms TTL=116
Reply from 196.2.128.100: bytes=32 time=74ms TTL=116

Ping statistics for 196.2.128.100:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 74ms, Maximum = 140ms, Average = 95ms
 
mines much slower than alchamy

last one times out.

###############################
PING 196.2.128.100 (196.2.128.100) 56(84) bytes of data.

--- 196.2.128.100 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19001ms
rtt min/avg/max/mdev = 86.573/260.594/646.046/162.910 ms
###############################
PING 196.2.128.99 (196.2.128.99) 56(84) bytes of data.

--- 196.2.128.99 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19016ms
rtt min/avg/max/mdev = 91.694/292.486/506.672/116.358 ms
###############################
PING 196.4.79.6 (196.4.79.6) 56(84) bytes of data.

--- 196.4.79.6 ping statistics ---
20 packets transmitted, 0 received, 100% packet loss, time 18996ms

###############################
 
ouch

that's what i'm getting. i'm in kyalami, so it's on midrand tower.

here's typical stats to my PPP peer.

PING 196.30.31.100 (196.30.31.100) 56(84) bytes of data.
--- 196.30.31.100 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19013ms
rtt min/avg/max/mdev = 65.177/166.835/419.661/108.399 ms

my iburst device leds are REALLY disco-ing tonight. between 3 and 5 and occasionally lower with yellow coming on in very short intervals.

chz,
kk
 
kuberkoos said:
...my iburst device leds are REALLY disco-ing tonight. between 3 and 5 and occasionally lower with yellow coming on in very short intervals...
Click to expand...
kk, had any red with that? It isn't a proper disco without the red.
 
Code: 
Ping statistics for 196.2.128.100:
    Packets: Sent = 50, Received = 8, Lost = 42 (84% loss),
Approximate round trip times in milli-seconds:
    Minimum = 361ms, Maximum =  1321ms, Average =  131ms
...................
Ping statistics for 196.2.128.99:
    Packets: Sent = 50, Received = 7, Lost = 43 (86% loss),
Approximate round trip times in milli-seconds:
    Minimum = 641ms, Maximum =  1001ms, Average =  112ms
...................
Ping statistics for 196.4.79.6:
    Packets: Sent = 50, Received = 0, Lost = 50 (100% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum =  0ms, Average =  0ms
 
PoiZoNouZ. just get ADSL in your new place again for now.
Wireless is not suited for stable latency at all - not yet, anyway. Possibly WiMax will be better ?

Your pings may be stable for 2 minutes, but they are going to b0rk out your FPS game without a shadow of a dought. That much is indisputable.
 
On Iburst

ping www.google.com -n 50

Pinging www.google.akadns.net [64.233.187.99] with 32 bytes of data:

Reply from 64.233.187.99: bytes=32 time=416ms TTL=241
Reply from 64.233.187.99: bytes=32 time=459ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=367ms TTL=241
Reply from 64.233.187.99: bytes=32 time=341ms TTL=241
Reply from 64.233.187.99: bytes=32 time=339ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=337ms TTL=241
Reply from 64.233.187.99: bytes=32 time=337ms TTL=241
Reply from 64.233.187.99: bytes=32 time=341ms TTL=241
Reply from 64.233.187.99: bytes=32 time=470ms TTL=241
Reply from 64.233.187.99: bytes=32 time=349ms TTL=241
Reply from 64.233.187.99: bytes=32 time=398ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=341ms TTL=241
Reply from 64.233.187.99: bytes=32 time=570ms TTL=241
Reply from 64.233.187.99: bytes=32 time=339ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=337ms TTL=241
Reply from 64.233.187.99: bytes=32 time=337ms TTL=241
Reply from 64.233.187.99: bytes=32 time=340ms TTL=241
Reply from 64.233.187.99: bytes=32 time=334ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=342ms TTL=241
Reply from 64.233.187.99: bytes=32 time=337ms TTL=241
Reply from 64.233.187.99: bytes=32 time=335ms TTL=241
Reply from 64.233.187.99: bytes=32 time=339ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=333ms TTL=241
Reply from 64.233.187.99: bytes=32 time=332ms TTL=241
Reply from 64.233.187.99: bytes=32 time=340ms TTL=241
Reply from 64.233.187.99: bytes=32 time=339ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=337ms TTL=241
Reply from 64.233.187.99: bytes=32 time=336ms TTL=241
Reply from 64.233.187.99: bytes=32 time=352ms TTL=241
Reply from 64.233.187.99: bytes=32 time=340ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=448ms TTL=241
Reply from 64.233.187.99: bytes=32 time=332ms TTL=241
Reply from 64.233.187.99: bytes=32 time=357ms TTL=241
Reply from 64.233.187.99: bytes=32 time=340ms TTL=241
Reply from 64.233.187.99: bytes=32 time=409ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=337ms TTL=241
Reply from 64.233.187.99: bytes=32 time=337ms TTL=241
Reply from 64.233.187.99: bytes=32 time=341ms TTL=241
Reply from 64.233.187.99: bytes=32 time=340ms TTL=241
Reply from 64.233.187.99: bytes=32 time=338ms TTL=241
Reply from 64.233.187.99: bytes=32 time=337ms TTL=241

Ping statistics for 64.233.187.99:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 332ms, Maximum = 570ms, Average = 355ms

Not perfect but equally good as anything i got with my isdn line
 
Daveogg said:
Pinging [64.233.187.99] ......
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Minimum = 332ms, Maximum = 570ms, Average = 355ms
Click to expand...

mine: (with serious disco-ing (no red tough))

ping -c50 -q 64.233.187.99
PING 64.233.187.99 (64.233.187.99) 56(84) bytes of data.
--- 64.233.187.99 ping statistics ---
50 packets transmitted, 47 received, +3 duplicates, 6% packet loss, time 49048ms
rtt min/avg/max/mdev = 299.922/556.074/1480.474/258.677 ms, pipe 2

chz,
kk
 
Try pinging www.saix.net, PoiZoNouZ indicates he plays a lot of CS:S and the main servers are of course SGS.

This is home ADSL 384 :-

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

I'd be interested to see if iBurst can hold a steady ping to saix - those Google figures look pretty good. What your looking for is not only average ms, but also packet loss.

Here's my Google ping, the ms is higher, but this is 8:30am in the morning.
Note there's no packet loss.

Ping statistics for 216.239.59.99:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 482ms, Maximum = 517ms, Average = 496ms
Click to expand...
 
I'm keeping my eye on iBurst as an option later in the year - possibly when I move house again. If they can sustain themselves, despite the odd things such as the activation fee and some people having a rotten connection, they may just be worth looking at - time will tell. Once burnt, twice shy.
 
Code: 
Ping statistics for 196.25.1.200:
    Packets: Sent = 50, Received = 46, Lost = 4 (8% loss),
Approximate round trip times in milli-seconds:
    Minimum = 90ms, Maximum =  1292ms, Average =  368ms
...............................
Ping statistics for 216.239.59.99:
    Packets: Sent = 50, Received = 39, Lost = 11 (22% loss),
Approximate round trip times in milli-seconds:
    Minimum = 461ms, Maximum =  1392ms, Average =  573ms
...............................
Ping statistics for 64.233.187.99:
    Packets: Sent = 50, Received = 46, Lost = 4 (8% loss),
Approximate round trip times in milli-seconds:
    Minimum = 370ms, Maximum =  1392ms, Average =  599ms
 
IC:-

Ping statistics for 196.25.1.200:
Packets: Sent = 50, Received = 46, Lost = 4 (8% loss),
Approximate round trip times in milli-seconds:
Minimum = 90ms, Maximum = 1292ms, Average = 368ms
Click to expand...


Eeek ! - that's bad for Saix !
368ms, 8% loss

But how many other iBurst users would get the same and what's the reliability here, in fact, what's the guarantee that if you do get good latency, that it'll last ?

Hmmm.
 
Personally, I suspect that TTL need some serious adjusting on the iBurst network, but I'm tired of trying to figure all this out- it is boggling my mind.
 
Just a ping result for you guys

--- ftp.is.co.za ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4003ms
rtt min/avg/max/mdev = 52.471/64.444/70.675/6.611 ms
 
Code: 
Ping statistics for 196.25.1.200:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 90ms, Maximum =  911ms, Average =  207ms
(TTL=247)
...................
Ping statistics for 216.239.59.99:
    Packets: Sent = 50, Received = 34, Lost = 16 (32% loss),
Approximate round trip times in milli-seconds:
    Minimum = 441ms, Maximum =  882ms, Average =  389ms
(TTL=229)
...................
Ping statistics for 64.233.187.99:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 331ms, Maximum =  671ms, Average =  453ms
(TTL=234)
...................
Ping statistics for 196.4.160.12:
    Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 90ms, Maximum =  400ms, Average =  158ms
(TTL=57)
 
bb_matt said:
Eeek ! - that's bad for Saix !
368ms, 8% loss

But how many other iBurst users would get the same and what's the reliability here, in fact, what's the guarantee that if you do get good latency, that it'll last ?

Hmmm.
Click to expand...

Ping statistics for 196.25.1.200:
Packets: Sent = 96, Received = 96, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 93ms, Maximum = 390ms, Average = 142ms
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X