Co-ordinated effort to determine extent of problems

ic

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,805
Look this has gone far enough - WBS have to recognise the extent of the problems that we are all experiencing. That in mind, I propose that we launch a co-ordinated Line Speed Meter evidence monster attack. What do we have to loose: nothing! What do we have to gain: a decent amount of automated research & hopefully some attention in the form of communication & bandwidth from WBS.

noone said:
throttled a bit? I can't even get my kb/s up more than 12? browsing seems fine though
Click to expand...
Noone, et al [post=154298]please could you install LSM as per RPM's post[/post], I think we iBursters & Burst-iz all need to compare notes [i.e. speed test results], same goes for Daveogg :).

Noone, I assume u must be on Windoze if you're still an IE fan (LSM ins't available for ??nux || ?nix). Those that have a Windoze box behind ??nux || ?nix, please install on your Windoze as well.

Also, please publish your LSMTestResutsURL in your siggies.
 
ic

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,805
Ok, to allow LSM to test your iBurst connection's latency, you will have to make sure that your firewall isn't blocking ICMP Echo Requests (<edited old_text="subtype 8">type 8, subtype 0</edited>) from 203.147.129.11.

In my case, I have created an exception rule to allow ICMP Echo Requests for that IP address. As to your own h/w or s/w firewall config - read the help file. If you use CA's eTrust EZ Firewall then I can help you - just ask, altho I'm sure most here will already know-how :)
 
Last edited:
K

kuberkoos

Active Member
Joined
Jan 7, 2005
Messages
90
ic, i'm still running smokeping. in fact i'm getting average RTT of 770ms to you over the last 12hrs but, with an over 75% packet loss.

if there is an iburster with decent connection and dynamic DNS i'll add him/her and we can check your connection compares to better ones.

chz,
kk
 
Last edited:
L

limnos

Expert Member
Joined
Dec 24, 2004
Messages
2,234
I'd love to help with the LSM testing, but HOW THE HELL DO I DOWNLOAD THE 4.7M FILE AT 400 BYTES/SEC!!!!!!????!!!! And it keeps on dropping!!

Im so close to throwing the modem off my balcony...

Eveything about this product is sh*t!
 
ic

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,805
If you've got a download manager program of sorts that can suspend & resume downloads let that run overnight or something.

Limnos, r u still connected to the Bryanston-bs or are you back in Midrand now, i.e. which bs is giving you hell - Bryanston-bs got a lot worse for me about 45mins back, this is what my background ping says right now:
Code: 
[size=3]Ping statistics for 196.25.1.200:
    Packets: Sent = 9019, Received = 2256, Lost = 6763 ([b][color=red]74% loss[/color][/b]),
Approximate round trip times in milli-seconds:
    Minimum = 60ms, Maximum =  1472ms, Average =  82ms
Control-Break[/size]
Don't even ask whatzup with the average ms - in a word it is Windoze...

I cannot wait to get SmoothWall going & hopefully SmokePing can test things from my side as well.
 
Last edited:
D

Daveogg

Expert Member
Joined
Nov 11, 2003
Messages
2,311
ic i have serious reservations about lsm. I have just downloaded it using flashget at an ave rate of 55KB/s. ( have screen cap if you are interested ). Just installed and done a test. First thing - Pop up screen Norton firewall detected may affect accuracy of test therefore will only test download or something like that. Disable norton get the same message. Do test anyway here is the result. http://www.tcpiq.com/tcpIQ/LineSpee...ountryId=196&ConnectionId=11302&UserId=148954.
Anyway 155kbps, but 2 mins ago was downloading at 440kbps!!
Latency according to test 571ms.
Just pinged www.tcpiq.com.
Pinging www.tcpiq.com [67.19.7.150] with 32 bytes of data:

Reply from 67.19.7.150: bytes=32 time=348ms TTL=110
Reply from 67.19.7.150: bytes=32 time=347ms TTL=110
Reply from 67.19.7.150: bytes=32 time=346ms TTL=110
Reply from 67.19.7.150: bytes=32 time=350ms TTL=110

Ping statistics for 67.19.7.150:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 346ms, Maximum = 350ms, Average = 347ms
Make you own conclusions.

Note to WBS this can work. Damn well make it work for everyone.
 
ic

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,805
Hi Dave,

I apreciate that you installed LSM - thanks :)

No idea what the problem was with Norton, can you elaborate bcos I'm losing the plot there...

Assuming that Norton didn't interfere too much with the Upload test, it looks like you might be experiencing the 0 Upload Speed problem.

If you don't mind, let it run 48 times a day for today & tomorrow or longer, lets see what happens over time & hopefully we can get a big picture view of this iBurst network :)
Code: 
[size=3]D:\Documents and Settings\...>ping 67.19.7.150

Pinging 67.19.7.150 with 32 bytes of data:

Reply from 67.19.7.150: bytes=32 time=951ms TTL=109
Reply from 67.19.7.150: bytes=32 time=891ms TTL=109
Reply from 67.19.7.150: bytes=32 time=922ms TTL=109
Reply from 67.19.7.150: bytes=32 time=981ms TTL=109

Ping statistics for 67.19.7.150:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 891ms, Maximum =  981ms, Average =  936ms[/size]
 
D

Daveogg

Expert Member
Joined
Nov 11, 2003
Messages
2,311
ic sorry maybe did not explain myself to well. After installing i got a pop up which said that Norton was detected on your system. This will prevent LSM from acurately measuring your upload speed therefore LSM will only measure download speed. ie it did not do the Me to LSM test. Definately do have upload, well put it this way when i video conference they can see my ugly mutt!
I will leave it running for a while but plan on (ab)using the connection as much as possible until the cap so dont read too much into it!! Any ideas on the difference in the results of speed test compared to my "real world" situation.
Also been pondering why iburst does not come clean on the problems. I think we can assume that it is a tower problem (or at least signal problem ) not a general network problem like sentech. Could it be that iburst has run into a problem with addaptive antanae technology and arraycom don't want that known hence the deaffening silence??
 
ic

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,805
Hmmm, now that you mention Norton again & I am slowly waking up (still want to go back to sleep though) there was something in the LSM FAQs, here's the link for people afflicted with Norton:
http://www.tcpiq.com/tcpIQ/LineSpeed/Resources/FAQs/#FAQ17

Anyways, so we won't be able to find out if you're experiencing the 0 Upload Speed problem, oh well hopefully LSM will provide some useful info - even if you're using all of my bandwidth :D
 
S

slimothy

Banned
Joined
Jan 14, 2005
Messages
4,808
ic said:
Look this has gone far enough - WBS have to recognise the extent of the problems that we are all experiencing.
Click to expand...

I'm not experiencing the same problems as you guys.. when everyone was talking some crap about UUNET I was still downloading at 120KBps.
 
ic

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,805
By "all experiencing" I meant all of us Burst-i people that actually are not getting decent connectivity. I would like as many peeps as possible to participate with the LSM testing - even those that don't have a problem, why - so we can compare notes at the base-station level & look for trends etc.
 
minkukel

minkukel

Expert Member
Joined
Dec 27, 2004
Messages
2,371
Kuberkoos, will dig out a box behind me in the storeroom 2 replace the smooth wall box, to do u funny trix wiff debian, then we can do the smoke pingy
 
J

jamieb

Well-Known Member
Joined
Dec 13, 2004
Messages
228
This is what you get from iBUST

This what you get with IBUST. (We are located in Hydepark (right next to Sandton and Rosebank). The iBurst terminal is placed at the top of a double story house, next to an open window.

Code: 
ping -t [url]www.google.com[/url]
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=346ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=3032ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=547ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=3166ms TTL=232
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=390ms TTL=232
Reply from 64.233.171.147: bytes=32 time=423ms TTL=232
Reply from 64.233.171.147: bytes=32 time=3163ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=433ms TTL=232
Reply from 64.233.171.147: bytes=32 time=3319ms TTL=232
Reply from 64.233.171.147: bytes=32 time=629ms TTL=232
Reply from 64.233.171.147: bytes=32 time=348ms TTL=232
Reply from 64.233.171.147: bytes=32 time=3485ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=1725ms TTL=232
Reply from 64.233.171.147: bytes=32 time=3949ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=380ms TTL=232
Reply from 64.233.171.147: bytes=32 time=613ms TTL=232
Reply from 64.233.171.147: bytes=32 time=296ms TTL=232
Reply from 64.233.171.147: bytes=32 time=986ms TTL=232
Reply from 64.233.171.147: bytes=32 time=799ms TTL=232
Reply from 64.233.171.147: bytes=32 time=812ms TTL=232
Reply from 64.233.171.147: bytes=32 time=471ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=4365ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=776ms TTL=232
Reply from 64.233.171.147: bytes=32 time=3122ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=391ms TTL=232
Reply from 64.233.171.147: bytes=32 time=3944ms TTL=232
Reply from 64.233.171.147: bytes=32 time=393ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1118ms TTL=232
Reply from 64.233.171.147: bytes=32 time=554ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1227ms TTL=232
Reply from 64.233.171.147: bytes=32 time=3989ms TTL=232
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=3387ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=842ms TTL=232
Reply from 64.233.171.147: bytes=32 time=316ms TTL=232
Reply from 64.233.171.147: bytes=32 time=732ms TTL=232
Reply from 64.233.171.147: bytes=32 time=300ms TTL=232
Reply from 64.233.171.147: bytes=32 time=526ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1530ms TTL=232
Reply from 64.233.171.147: bytes=32 time=3369ms TTL=232
Reply from 64.233.171.147: bytes=32 time=579ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=533ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=485ms TTL=232
Reply from 64.233.171.147: bytes=32 time=360ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=4025ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=1116ms TTL=232
Reply from 64.233.171.147: bytes=32 time=415ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1749ms TTL=232
Reply from 64.233.171.147: bytes=32 time=2109ms TTL=232
Reply from 64.233.171.147: bytes=32 time=414ms TTL=232
Reply from 64.233.171.147: bytes=32 time=2691ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1328ms TTL=232
Reply from 64.233.171.147: bytes=32 time=399ms TTL=232
Reply from 64.233.171.147: bytes=32 time=684ms TTL=232
Reply from 64.233.171.147: bytes=32 time=2230ms TTL=232
Reply from 64.233.171.147: bytes=32 time=4119ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=3242ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=2369ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=422ms TTL=232
Reply from 64.233.171.147: bytes=32 time=901ms TTL=232
Reply from 64.233.171.147: bytes=32 time=615ms TTL=232
Reply from 64.233.171.147: bytes=32 time=608ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1387ms TTL=232
Reply from 64.233.171.147: bytes=32 time=2929ms TTL=232
Reply from 64.233.171.147: bytes=32 time=518ms TTL=232
Reply from 64.233.171.147: bytes=32 time=476ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=678ms TTL=232
Reply from 64.233.171.147: bytes=32 time=787ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1740ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1600ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=1492ms TTL=232
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=827ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1801ms TTL=232
Request timed out.
Reply from 64.233.171.147: bytes=32 time=823ms TTL=232
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=1019ms TTL=232
Reply from 64.233.171.147: bytes=32 time=969ms TTL=232
Reply from 64.233.171.147: bytes=32 time=1888ms TTL=232
Reply from 64.233.171.147: bytes=32 time=3984ms TTL=232
Request timed out.
Request timed out.
Reply from 64.233.171.147: bytes=32 time=634ms TTL=232
Reply from 64.233.171.147: bytes=32 time=719ms TTL=232
 
Last edited by a moderator:
ic

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,805
jamieb said:
This what you get with IBUST...
ping -t www.google.com
Request timed out.
Request timed out.
Request timed out.
...
Click to expand...
Just back online now after ~60 minutes downtime on Bryanston-bs - amazing how it usually happens when the help-less-desk is not operating :(

Yep, that's basically what I have been getting - pinging locally - initially www.iburst.co.za, now doing www.saix.net bcos I dislike Telkom more than I'm annoyed with WBS & iburst.co.za was unpingable for a while.

JamieB, favour: please could you enclose your ping results in
Code: 
 that way it won't hurt my scrolling finger to read this thread :)

Hi GhostIM, KK said I should ask you about why I cannot get into SWe2 admin after install, but I'm going to do a packet capture with Ethereal first & if I still cannot figure it out I will ask you then.
 
I

Impressed

Member
Joined
Feb 6, 2005
Messages
13
Chris

You guys need better machines...

Your pings above compared to mine....

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\xxx>ping 67.19.7.150

Pinging 67.19.7.150 with 32 bytes of data:

Reply from 67.19.7.150: bytes=32 time=335ms TTL=110
Reply from 67.19.7.150: bytes=32 time=343ms TTL=110
Reply from 67.19.7.150: bytes=32 time=343ms TTL=110
Reply from 67.19.7.150: bytes=32 time=343ms TTL=110

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


Good machine.... good results.... :)

Keep up the good work WBS
 
A

aborg

Senior Member
Joined
Mar 29, 2004
Messages
744
Well tonight the authentication server fell over....mmm stability my ass...redundancy my second ass... - this is the one thing that pisses me off the most and I can do f**kall about it. :( Otherwise things are just peachy....
 
A

aborg

Senior Member
Joined
Mar 29, 2004
Messages
744
Kuberkoos - talk to slimothy I think he laid a cable straight from the tower to his house, he never has problems.... :p
 
ic

ic

MyBroadband
Super Moderator
Joined
Nov 8, 2004
Messages
14,805
aborg said:
Kuberkoos - talk to slimothy I think he laid a cable straight from the tower to his house, he never has problems.... :p
Click to expand...
Yeah, I'm getting all the more suspicious of these "I never have a problem" posters - I am wondering if WBS has decided to skimp on advertising - so they just do it here for free... Could I be on the right track, I wonder :confused:
 
You must log in or register to reply here.
Top