Dead IPs'

MrH

Expert Member
Joined
Jun 4, 2005
Messages
2,193
Reaction score
0
Location
Cape Town
Has anyone else noticed that when you connect to some IPs' they are either very slow or completely "dead" when trying to browse or download?

I have found that the "dead" IPs' normally at the lower end of the range.:confused:
 
This has been going on for quite some time. I had one about a week ago again. Disconnected for a while, and reconnected to get a new IP
 
Hi,

Please advise your base station MrH...I've noticed something that I want to report to iBurst.

Landy I will assume you connecting to Centurion Base station :D
 
same here

Hi .
I am connected to the kempton park tower and i have been getting real bad connections and also dead links ...

This has been going on for a whole month now ..
iBurst cannot see anything wrong!!! :confused:
 
As Ekhaatvensters said I'm on the Plumstead base station, and I also noticed this morning that while I was browsing my IP went dead and I had to change to another, this happened a few times but seems to be working now even though speeds are not as good as they were during last month.:eek:

I don't like complaining as overall iBurst has been good to me connection wise, but I hope that this new fault is sorted out soon.
 
I seem to remember having this happen to me a few times too, and my IP does go dead but only for very short intervals sometimes.

Not really much of a problem for me yet... im still doing pretty good.
 
hmmm.. I can do, but I'll see if it happens to me any time soon again. Then I can get the IP under which it is happening, nothing for now sorry.
 
/me thinks iBurst cap IP's and for some reason those IP's are allocated to uncapped susbcribers
 
BroadbandICTHoldings said:
Can you guys provide me with IP's at the time this happened?
It just happened a few min ago when I was trying to logon to the forum, but I never wrote down the IP.
Next time it happens I will take note of which IPs' go dead.
 
native said:
/me thinks iBurst cap IP's and for some reason those IP's are allocated to uncapped susbcribers
Why should iBurst cap any IP, I would think it was the user account that gets capped when the limit was reached.
 
MrH said:
Why should iBurst cap any IP, I would think it was the user account that gets capped when the limit was reached.

It was just an assumption, I dont have proof to my statement and if I'm wrong I stand to accept that.

But then how does it happen that one get a bad connection when he/she have a particular IP and when they change that IP they have a complelty different connection?
 
native said:
It was just an assumption, I dont have proof to my statement and if I'm wrong I stand to accept that.

But then how does it happen that one get a bad connection when he/she have a particular IP and when they change that IP they have a complelty different connection?
I don't have the answer to that as I am no expert on the subject, and all I can think of is that whoever set the system up does not know what he is doing as I can't see any reason for them capping certain IPs' since any of us can end up with any of the IPs' in the iBurst range.

To my way of thinking I'd think they would cap the user account when you reach your limit and not the IP as such.

Shaun or any other expert could you please respond and clear up this query of the capping and dead IPs'?
 
hi this is the ip's that died on me yesterday:

PPP adapter iBurst:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 196.2.104.197
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 196.2.104.197
PPP adapter iBurst:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 196.2.120.165
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 196.2.120.165
PPP adapter iBurst:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 196.2.112.39
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 196.2.112.39
PPP adapter iBurst:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 196.2.120.154
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 196.2.120.154
PPP adapter iBurst:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 196.2.120.236
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 196.2.120.236
PPP adapter iBurst:
Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 196.2.106.64
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 196.2.106.64
 
i have had this before. One IP would not let me log on to msn, but i could browse. I thought it was MSN... Email also gave problems. However when I turned the modem off and on and got a new IP everything was fine.

Not sure what it could be.
 
I thinki got it today.. well my connection definately went dead for a while, changed the IPs and it was fine, but I forgot to check what the Ip was. I didnt think it was this problem at first so yah..

it was arounf 196.46.x..x
 
native said:
/me thinks iBurst cap IP's and for some reason those IP's are allocated to uncapped susbcribers

Whoa whoa, I doubt the IP's get capped, that doesn't make sense since a company would be aware that most of their IP's are Dynamic!

Although if this is being done.....OMG....then that would be a simple reason for what is currently and annoying anomaly ....glitch in the Matrix. I gather.....that's for iBurst Group to answer...but generally on a Bandwidth Mangement Unit you specify profile for users, hence like things in general perhaps on iBurst you have an account with the contract and the package/s you purchased generally making up what can be considered your iBurst profile.

Scenario:
you are an iburst user you create your PPPoE link and connect, your request for authentication gets handled by a Radius server which,you then load your 'profile' containing information, maybe like the following: the package you are on to determine shaping, how much you have DL,UL, your location and the probably which gateway you would be using, CPT or JHB *depending on where your connection attempt was generated from, etc etc.....let me state for the record that I am not sure what exact processess iBurst Group uses, but generally this is how things are determined *

this gets loaded in a system *most probably their BMU's or whatever they running* and the based on what the profiles calculations of your bandwidth usage and availibility is,within your monthly allowance or over it wll determine if you get normal service , upto 1Mbps, specified by package types or whether you get bummed to 64k....the process they use is obviously confidential and based on my experience with BMU's this is a possible setup.
 
well at the end of the day what's annoying me is customers want to cancel because of this 'glitch' hence my reason to try and troubleshoot it as well.
 
Top
Sign up to the MyBroadband newsletter
X