Sign up with Google
Roman4604
Executive Member
- Joined
- Jun 27, 2005
- Messages
- 5,554
Hi All,
Like many of the rest of you I've experienced the slow speed on iBurst (~ 1-4 KB/Sec). This is while being UN-CAPPED.
Also I'm on the Kyalami BS and don't believe I've been having any radio related problems (e.g. pings & http to www.iburst.co.za always good), so I'm not sure if this applies to the PTA/Northcliff problems which seem more radio or capacity related.
So I've been experimenting a bit, and the more I test the more this problem seems to be with the Auth system interacting with the BW Mgmt system. If I keep logging out & in I will get some slow sessions (1-4 KB/Sec) & some fast sessions (~ 105 KB/Sec for me).
It has nothing to do with the IP I get (get slow & fast on same IP range) or how many times I log in & out (sometimes 1 login/out to get from slow to fast, sometimes takes up to 5). Also there does not seem to be any correlation to how long you wait between logout & in (tried 1 sec to 30min).
My guess is that every IP assigned by Auth sys relates to a BW rule on BW Mgr. As you login an IP is assigned & its associated rule in the BW Mgr is updated.
But what happens when the two systems loose sync. Lets say I login in and get assigned an IP which was being used by another user shortly before me, and that user didnt logout ... they just switched off their UTD or ejected UTC?
Maybe the BW Mgr now doesnt get updated and I get the IP with the other user's CAPPED BW rule? Or possibly (my suspicion) that the BW Mgr has all users capped unless the Auth sys injects an un-capped rule for the IP it just dished out, and the rule update failed. The session would then seem capped.
Anyway this is my theory. The question I have for others with the slow bandwidth problems is, have you persevered to keep login in & out to try and get a fast session? Are your experiences similar, or is this something local to my BS or just my setup?
Like many of the rest of you I've experienced the slow speed on iBurst (~ 1-4 KB/Sec). This is while being UN-CAPPED.
Also I'm on the Kyalami BS and don't believe I've been having any radio related problems (e.g. pings & http to www.iburst.co.za always good), so I'm not sure if this applies to the PTA/Northcliff problems which seem more radio or capacity related.
So I've been experimenting a bit, and the more I test the more this problem seems to be with the Auth system interacting with the BW Mgmt system. If I keep logging out & in I will get some slow sessions (1-4 KB/Sec) & some fast sessions (~ 105 KB/Sec for me).
It has nothing to do with the IP I get (get slow & fast on same IP range) or how many times I log in & out (sometimes 1 login/out to get from slow to fast, sometimes takes up to 5). Also there does not seem to be any correlation to how long you wait between logout & in (tried 1 sec to 30min).
My guess is that every IP assigned by Auth sys relates to a BW rule on BW Mgr. As you login an IP is assigned & its associated rule in the BW Mgr is updated.
But what happens when the two systems loose sync. Lets say I login in and get assigned an IP which was being used by another user shortly before me, and that user didnt logout ... they just switched off their UTD or ejected UTC?
Maybe the BW Mgr now doesnt get updated and I get the IP with the other user's CAPPED BW rule? Or possibly (my suspicion) that the BW Mgr has all users capped unless the Auth sys injects an un-capped rule for the IP it just dished out, and the rule update failed. The session would then seem capped.
Anyway this is my theory. The question I have for others with the slow bandwidth problems is, have you persevered to keep login in & out to try and get a fast session? Are your experiences similar, or is this something local to my BS or just my setup?
