Anyone else having "capped issues"?

C

Crash

Senior Member
Joined
Nov 15, 2004
Messages
941
Reaction score
3
Location
Australia.
Just became capped about 30 mins ago. All hell has broken loose.

Got the infamous "Can only get to iBurst.co.za" sites after being capped.

I've disconnected the modem a couple times and left it off for about 5mins.
When I reconnect a get a different IP address, and I have connectivity for about 5 mins then nothing.

1.) Disconnect.
2.) Unplug for 5 mins.
3.) Plugin Reconnect
4.) Connectivity for 5 mins then back to step one.

When I say no conectivity, it's not entirely true. Funny enough Skype still works and I can perform pings and traceroutes to local and international sites. No HTTP, SMTP and so on.

Anyone else having this fun?
Currently using Vodacom 3G to post this :eek:
 
3 1/2 hours to go for throttled service
My mail just takes forever to download and no HTTPS
 
For 2 months I have been trying to get wbs to fix this issue! Let me tell you they have no damn idea what's causing it! Some times only certain protocols will work. At all times www.iburst.co.za will be accessable. Even uncapped ftp protocols by me don't work! Every other day it's some new problem. I give up.
 
Hows this. While all this crap was going on, I fired up my download manager.
It started going at full speed, even though I couldn't get to any websites or mail servers.

Kept going for a couple hours before it died. The capping system is crappy.
 
At times after being capped I can play games,use mirc,https & even msn messenger sometimes, but not normal http :(

As soon as the prchase 1gb button is pushed everythnig jumps back to normal immediatly, except for ftp :(
 
Crash, I've had this issue for months now, and finally decided to do some tests to see what could be causing it....well no big surprise, 'tis the bandwidth manager. It seems like the bandwidth manager can't cope with throttling you while you are multi-threading, hence your full speed after re-connecting. It also seems like they have instituted a 'quick fix' that will kill downloads AND browsing if the bandwidth manager finds that you are multi-threading while capped. I reached my cap on Sunday while downloading a file. The download got throttled to 8K , as it should, for the remainder of that download. Whilst that was happening I could browse the net without any problem. As soon as that download stopped, and the next one started, everything came to a grinding halt. Re-connecting didn't help, as my IP address stayed the same. After waiting for about five minutes, I reconnected again and browsing was back to normal again, but as soon as the download manager kicked in, the same thing happened again. Then I disconnected, changed the d/l manger to only use 1 thread, and reconnected with a new IP. Only then could I browse and download at the capped speed. So next time you're capped, use one thread to download, and there should be no 'death after cap'. Of course, they should still fix their bandwidth manager to cope with multi-threading after cap.
 
add me to the list, same thing happened, and I mean I must have just got over 3 GB as I didnt do any large downloads, and I was running uncapped almost to the end of the month.
 
No problems here, and over the last 3 days I've been capped and continued with a 1.3GB p2p download, if that counts for something.

I have had problems with FTP though, although updating the firmware seems to have solved that to some extent. FTP uploads are now smooth and quick.
 
The reason www.wbs.co.za et al works is that it's before their cache server and before their bandwidth manager...

From *guestimations* it looks like packets leave (utd-->internet) perfectly but packets comming back (internet-->utd) dissapears into a void....

I personally have a feeling that is has something to do specifically with the tcp/ip stack on their bw manager ... but then I'm not privy to such info so I may simply be smoking the strong stuff....
 
*Sigh*

I've been around this bush now for 4 months with iBURST. EVERY TIME I go over my cap, HTTP,SMTP, FTP stops working completely. Its almost like they null-route my packets!

i've taken it up with Shaun from WBS who says they are aware of it and that they're not sure what causes it.

Yet 4 months later I still sit today with the same problem. I dont know what they do there during office hours but you would think they could put some priority on their bandwidth manager that is OBVIOUSLY broken.

Ps - One way around it is if you're lucky enough to have an internet facing server, load a proxy on it - secure the hell out of it and set it to some arb port like 8889 and surf from iBurst via the proxy. Speeds work fine because it bypasses their NON-Working bandwidth monitor.
 
So what you guys are saying is its a hard-cap? I read on the site it only reduced your speed to 64kps
 
Fudzy said:
So what you guys are saying is its a hard-cap? I read on the site it only reduced your speed to 64kps
Click to expand...

Sometimes it works fine and other days, you need a refund.
 
Last edited:
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X