Oh wow! What a launch!

pwab · Apr 1, 2005

This is just way too bad for ssh, email, www ... just about everything that I use this connection for to make money with!

Code:

C:\Documents and Settings\Pwab>ping -n 20 smtp.wbs.co.za

Pinging smtp.wbs.co.za [196.30.31.203] with 32 bytes of data:

Reply from 196.30.31.203: bytes=32 time=[COLOR=Sienna]2023[/COLOR]ms TTL=252
Reply from 196.30.31.203: bytes=32 time=1248ms TTL=252
Reply from 196.30.31.203: bytes=32 time=358ms TTL=252
Reply from 196.30.31.203: bytes=32 time=237ms TTL=252
Reply from 196.30.31.203: bytes=32 time=855ms TTL=252
Reply from 196.30.31.203: bytes=32 time=1473ms TTL=252
Reply from 196.30.31.203: bytes=32 time=114ms TTL=252
Reply from 196.30.31.203: bytes=32 time=631ms TTL=252
Reply from 196.30.31.203: bytes=32 time=294ms TTL=252
Reply from 196.30.31.203: bytes=32 time=92ms TTL=252
Reply from 196.30.31.203: bytes=32 time=315ms TTL=252
Reply from 196.30.31.203: bytes=32 time=349ms TTL=252
Reply from 196.30.31.203: bytes=32 time=167ms TTL=252
Reply from 196.30.31.203: bytes=32 time=175ms TTL=252
Reply from 196.30.31.203: bytes=32 time=[COLOR=Sienna]3643[/COLOR]ms TTL=252
Reply from 196.30.31.203: bytes=32 time=217ms TTL=252
Reply from 196.30.31.203: bytes=32 time=170ms TTL=252
Reply from 196.30.31.203: bytes=32 time=282ms TTL=252
Reply from 196.30.31.203: bytes=32 time=356ms TTL=252
Reply from 196.30.31.203: bytes=32 time=[COLOR=Sienna]3590[/COLOR]ms TTL=252

Ping statistics for 196.30.31.203:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 92ms, Maximum = [COLOR=Sienna][B]3643[/B][/COLOR]ms, Average = [COLOR=Sienna][B]829[/B][/COLOR]ms

LethalChicken · Apr 1, 2005

Oi that's bad ... compared to my 512 Home uncapped ADSL ....

Code:

ping -n 20 smtp.wbs.co.za

Pinging smtp.wbs.co.za [196.30.31.203] with 32 bytes of data:

Reply from 196.30.31.203: bytes=32 time=44ms TTL=247
Reply from 196.30.31.203: bytes=32 time=36ms TTL=247
Reply from 196.30.31.203: bytes=32 time=36ms TTL=247
Reply from 196.30.31.203: bytes=32 time=37ms TTL=247
Reply from 196.30.31.203: bytes=32 time=36ms TTL=247
Reply from 196.30.31.203: bytes=32 time=37ms TTL=247
Reply from 196.30.31.203: bytes=32 time=38ms TTL=247
Reply from 196.30.31.203: bytes=32 time=36ms TTL=247
Reply from 196.30.31.203: bytes=32 time=37ms TTL=247
Reply from 196.30.31.203: bytes=32 time=35ms TTL=247
Reply from 196.30.31.203: bytes=32 time=37ms TTL=247
Reply from 196.30.31.203: bytes=32 time=35ms TTL=247
Reply from 196.30.31.203: bytes=32 time=37ms TTL=247
Reply from 196.30.31.203: bytes=32 time=36ms TTL=247
Reply from 196.30.31.203: bytes=32 time=38ms TTL=247
Reply from 196.30.31.203: bytes=32 time=35ms TTL=247
Reply from 196.30.31.203: bytes=32 time=36ms TTL=247
Reply from 196.30.31.203: bytes=32 time=35ms TTL=247
Reply from 196.30.31.203: bytes=32 time=36ms TTL=247
Reply from 196.30.31.203: bytes=32 time=37ms TTL=247

Ping statistics for 196.30.31.203:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 35ms, Maximum = 44ms, Average = 36ms

w1z4rd · Apr 1, 2005

yeah thats cause ure fixed line, were wireless, theres a mild latency, but our top speeds kick that ass outta yours

Crash · Apr 1, 2005

/me thinks I should go get some diginet latency tests and post them on the ADSL forum. Cause it's annoying when people keep comparing ADSL ping to Iburst ping. WE KNOW ADSL ping is lower.... go away evil man

slimothy · Apr 2, 2005

lol i hate when adsl people come to gloat about thier pings HEY ADLO I CAN DOWNLOAD 100 MB IN 13 MINUTES

iburstuser · Apr 2, 2005

slimothy said:
lol i hate when adsl people come to gloat about thier pings HEY ADLO I CAN DOWNLOAD 100 MB IN 13 MINUTES

lol

Razer0 · Apr 2, 2005

adlo said:
What?

I am on 384 Home ADSL and did the same ping and got an average of 15ms.

You're probably closer to your exchange than he is to his.. tis my educated guess

Decotey · Apr 2, 2005

"compared to my 512 Home uncapped ADSL "
BlobNow is on uncapped whereas Adlo Im guessing is on standard.
The uncapped pings are worse than standard accounts from what I hear

pwab · Apr 2, 2005

missing the point

Three things:

1) I realise that a copper cable would get better pings. That's physics. But the day that I signed up (1 week ago) I did the same thing and got an average of 350ms (not 800ms). Even 350 seems little bit slow, I think one should be able the get half of that...

2) The point was raised that our download speed will kick the ass of a copper line. Well, sadly, for me this is not true. I donwloaded the java jre last night. I got a top downloading speed of 15Kb/s and an average of 8.5Mb/s... This kicks nothing, not even a landline modem. And even worse, this /is/ typical behaviour for my connection.

3) My modem usually has four of the five green lights on, which (I think) means I sit in a reasonable well covered area.

Regards,
p!

slimothy · Apr 2, 2005

pwab said:
Three things:

1) I realise that a copper cable would get better pings. That's physics. But the day that I signed up (1 week ago) I did the same thing and got an average of 350ms (not 800ms). Even 350 seems little bit slow, I think one should be able the get half of that...

2) The point was raised that our download speed will kick the ass of a copper line. Well, sadly, for me this is not true. I donwloaded the java jre last night. I got a top downloading speed of 15Kb/s and an average of 8.5Mb/s... This kicks nothing, not even a landline modem. And even worse, this /is/ typical behaviour for my connection.

3) My modem usually has four of the five green lights on, which (I think) means I sit in a reasonable well covered area.

Regards,
p!

It has nothign to do with copper cable that ADSL has better pings, it has better latecy for 2 reasons, firstly the data goes one way all the time, down the line and onto the network where as with iburst you have to send a signal to a base station and the way it travels can be affected by all types of things thanks to draw backs in radio technology, secondly, iburst has an invisible switching mechanism for mobility this means while sending stuff your iburst unit has to figure where its sending it to, that adds more overhead, while downloading and maxing your connection your pings will be higher, around 300 seems average if you are maxing it, but the pings can get as slow as 1000 soemtimes and worse and 5 minutes later you can have 40ms, its just the way it is and will always be.

with your second point, it has NOTHING to do with copper again i'm not sure why you keep mentioning copper. now since you are new I want to explain some things about iburst, if using international servers you NEED to multithread, if not most of the time you will only get a quarter or just above your total capacity on one thread, so maybe 25/30KBs. and I can assure you that your statement:

15Kb/s and an average of 8.5Mb/s

is pretty unbelieveable since 8.5Mbit/s is almost 1 megabyte a second transfer, and also you should know that sun servers (where java is downloaded from) are really slow for us, even old time tech heads on iburst have said this before with regards to downloading the java sdk, so it comes as no suprise.

My last point is something we need to mention to every new user who wants to bash the product, iburst is not as effective if you just take your modem out and plop it anywhere, you need to find a sweet spot so you get the highest signal imaginable with the lowest frame error rate and MULTITHREEAD EVERYTHING.

once you do that you will be able to have it running at 130/140KB/s and some people have gone above that too.

pwab · Apr 2, 2005

slimothy,

Your post cleared some things up for me. I am not really bashing iburst, as such. Yesterday I tried to do a cvs up. My setup has me using cvs over a ssl tunnel, so latency affects the whole thing. And yesterday I had very bad performance. I was comenting on that.

Sorry for the typo... I do know the difference between Mb/s and Kb/s

Maybe some kind of tutorial will be in order for how to go about setting up the location of the modem? When I set up my modem I was using the USB interface on windows, so I had the terminal to check on how it went. The first place I tried to connect from (on top of my pc box) had me a signal strength of 80-100% and almost no packet loss. This seems to be the case still.

However, I have not ever achieved > 20Kb/s sustained traffic on any downloading application. I downloaded the ubuntu linux iso last week from a local server using ftp. I was experimenting and had 10 threads working at it. When I was finished my average downloading speed was just over 12.5 Kb/s; with /bursts/ of 25Kb/s. Again that is what I was refferring to.

Regards,
p!

slimothy · Apr 2, 2005

ok well 80% signal is not ideal but you should be able to get 90KB/s to 100KB/s with that assuming you are downloading froma good server and in a good area. The only way to find your sweet spot is with trial and error, however remember the connection needs to be contantly in use while finding the sweet spot, so starta a multithread download (use a download manager like flashget or download accelorator) and if you're in windows start a "ping -t www.iburst.co.za" in the command prompt so you can watch ping times.

Then open the iBurst terminal and start moving it, move it a bit see if the numbers improved, if they did keep moving it in that way till it peaks, if not try the opposite, I found my sweet spot after half an hour, which felt like a waste of time but you really feel it once it works, its that simple you either have it in the sweet spot and it rocks or it sucks big time. The speeds you are experience are in no way normal.

Any latency dependant tasks like gaming or using CVS over an SSL tunnel are not ideal on wireless, they can be OK but that can change any minute for any number of reasons which is enough to piss anyone off.

jpd · Apr 2, 2005

My iBurst results:

Code:

Pinging smtp.wbs.co.za [196.30.31.203] with 32 bytes of data

Reply from 196.30.31.203: bytes=32 time=83ms TTL=248
Reply from 196.30.31.203: bytes=32 time=88ms TTL=248
Reply from 196.30.31.203: bytes=32 time=100ms TTL=248
Reply from 196.30.31.203: bytes=32 time=79ms TTL=248
Reply from 196.30.31.203: bytes=32 time=86ms TTL=248
Reply from 196.30.31.203: bytes=32 time=89ms TTL=248
Reply from 196.30.31.203: bytes=32 time=83ms TTL=248
Reply from 196.30.31.203: bytes=32 time=86ms TTL=248
Reply from 196.30.31.203: bytes=32 time=83ms TTL=248
Reply from 196.30.31.203: bytes=32 time=91ms TTL=248
Reply from 196.30.31.203: bytes=32 time=83ms TTL=248
Reply from 196.30.31.203: bytes=32 time=107ms TTL=248
Reply from 196.30.31.203: bytes=32 time=86ms TTL=248
Reply from 196.30.31.203: bytes=32 time=79ms TTL=248
Reply from 196.30.31.203: bytes=32 time=91ms TTL=248
Reply from 196.30.31.203: bytes=32 time=90ms TTL=248
Reply from 196.30.31.203: bytes=32 time=84ms TTL=248
Reply from 196.30.31.203: bytes=32 time=91ms TTL=248
Reply from 196.30.31.203: bytes=32 time=87ms TTL=248
Reply from 196.30.31.203: bytes=32 time=86ms TTL=248

Ping statistics for 196.30.31.203:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 79ms, Maximum = 107ms, Average = 87ms

nocilah · Apr 2, 2005

hrm I get an average of 68ms on iburst when pinging iburst.co.za.
pwab you MUST get 100% signal to get good speeds. When experimented
when I first got iBurst 80%-92% gave me bad results...

Since I have moved I am getting 1MB speeds and I am over the moon and I p1ss on ADSL.

DFantom · Apr 2, 2005

5 lights on right now...

Code:

C:\Documents and Settings\a>ping -n 20 smtp.wbs.co.za

Pinging smtp.wbs.co.za [196.30.31.203] with 32 bytes of data:

Reply from 196.30.31.203: bytes=32 time=136ms TTL=251
Reply from 196.30.31.203: bytes=32 time=67ms TTL=251
Reply from 196.30.31.203: bytes=32 time=89ms TTL=251
Reply from 196.30.31.203: bytes=32 time=61ms TTL=251
Reply from 196.30.31.203: bytes=32 time=54ms TTL=251
Reply from 196.30.31.203: bytes=32 time=57ms TTL=251
Reply from 196.30.31.203: bytes=32 time=55ms TTL=251
Reply from 196.30.31.203: bytes=32 time=58ms TTL=251
Reply from 196.30.31.203: bytes=32 time=61ms TTL=251
Reply from 196.30.31.203: bytes=32 time=94ms TTL=251
Reply from 196.30.31.203: bytes=32 time=116ms TTL=251
Reply from 196.30.31.203: bytes=32 time=75ms TTL=251
Reply from 196.30.31.203: bytes=32 time=124ms TTL=251
Reply from 196.30.31.203: bytes=32 time=53ms TTL=251
Reply from 196.30.31.203: bytes=32 time=55ms TTL=251
Reply from 196.30.31.203: bytes=32 time=109ms TTL=251
Reply from 196.30.31.203: bytes=32 time=79ms TTL=251
Reply from 196.30.31.203: bytes=32 time=76ms TTL=251
Reply from 196.30.31.203: bytes=32 time=132ms TTL=251
Reply from 196.30.31.203: bytes=32 time=57ms TTL=251

Ping statistics for 196.30.31.203:
    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 136ms, Average = 80ms

nocilah · Apr 2, 2005

if you have five lights your signal can be anything between 80-100%
use the usb terminal UTL to establish that.

slimothy · Apr 2, 2005

yeah, you need to use the terminal to fine tune it because 80% is crap, so 5 lights may be misleading.

scavern · Apr 2, 2005

full strength signal, walking distance from tower

Code:

Pinging smtp.wbs.co.za [196.46.70.2] with 32 bytes of data:



Reply from 196.46.70.2: bytes=32 time=73ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=77ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252

Reply from 196.46.70.2: bytes=32 time=62ms TTL=252



Ping statistics for 196.46.70.2:

    Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 62ms, Maximum = 77ms, Average = 63ms

slimothy · Apr 2, 2005

Can Everyone Stop Posting Thier Flipping Pings Or At Least Only Paste Like A Snippet, No One Cares Your Ping Is Whatever The Hell It Is Or How Many Lights You Have On

nocilah · Apr 2, 2005

Join the MyBroadband community

Get started

Oh wow! What a launch!

Member

Expert Member

Karmic Sangoma

Senior Member

Banned

Well-Known Member

Expert Member

Expert Member

Member

Banned

Member

Banned

Well-Known Member

Banned

Expert Member

Banned

Banned

Well-Known Member

Banned

Banned