Another dead IP...

T

The_Unbeliever

Honorary Master
Joined
Apr 19, 2005
Messages
103,193
Reaction score
10,233
Location
Nkaaaaandla
41.208.203.159 - can ping it, but can't VPN to it... and VPN was working previously. Hardware/software wise, there's nothing wrong on our side of things, as I was able to log in to the PC in question over the weekend, but come Monday, I am unable to.
 
Well, restart the modem, not a hard problem to fix, but granted an irrtating one.

They sorted out our dead IP problems in CPT, so maby if you make some noise about yours..
 
Ekhaatvensters said:
They sorted out our dead IP problems in CPT, so maby if you make some noise about yours..
Click to expand...

Not quite as I've noticed in the past few days that any IP with 64 in the position shown is not working again:

xxx.xx.64.xxx

They did seem to have sorted it out after I/we complained last time but now it's back to "dead" again.:eek:
 
Dead IP's!

Hi there MrH

Please complain on mybehalf as well, had two today took me a while before I realised WTF was going on.

Wasn't expecting it to happen again, really annoying!

Thanks
 
Be aware of xxx.xxx.65.xxx IP range...

Seems xxx.xxx.65.xxx should be added to the IP's of death range.

EDIT: reconnect on 64
 
Last edited:
Good IP's in CTN 68-70

If you get xxx.xxx.68.xxx or xxx.xxx.69.xxx and xxx.xxx.70.xxx, keep em - connection seems to be very stable and speed flies! VPN, feels like you are on the same network.

EDIT: include 66
 
Last edited:
who.is.michael said:
If you get xxx.xxx.68.xxx or xxx.xxx.69.xxx and xxx.xxx.70.xxx, keep em - connection seems to be very stable and speed flies! VPN, feels like you are on the same network.

EDIT: include 66
Click to expand...

I agree those ranges are the best that I've had, in fact an IP with 70 is the best you can get on the iBurst network from the tests I've done.:cool:
 
The only IP ranges I ever had as "dead" were with 64 in that position.

I had "dying or slow" IPs with 65 and at times 66 in that position, but that was before I reported it the last time.

Last month I only had problems with 64 in that position.
 
Interesting that the IP range actually affects performance, you would expect iBurst to keep them all equal.

What do you think could cause this?

Getting an IP is basically just assigning you a slot on the network, out of a pool of IP's. It shouldnt change where you bandwidth comes from as everything goes through the same connection surely? I guess it doesnt really, but still weird that some IP's are worse.. and some even dead??

EDIT: I just check and im infact on a .66 IP now, it has been a bit slow today and yesterday.. maby ill try changing until I get around 68-70 and see if I get the same results.
Okay I got a .69 IP with my first change, im not sure if it realyl is better or if I just think so because im expecting it, but it does seem a bit faster. Ping times look better too, but maby thats be cause I tested the old IP a while ago, during business hours..
 
Last edited:
I've no idea why it should be different with another IP but maybe someone else who knows more about these things could explain as to how/why it does affect the speed.

I only found out awhile back as I kept notes as to speed, dead and dying IPs and I noticed that it followed a pattern, eg. 64 always been the "dead" and 65 - 66 dying or slow.

This only applied if they were in the position shown: xxx.xx.64.xxx
 
Don’t forget that it is intermittent…

Hi there

I’ve found 64 to be slower even when you can connect. Then suddenly your connection just dies, especially if you are transferring large amounts of data, it occurs more frequently.

So best not to use 64-66 at all.
 
who.is.michael said:
Hi there

I’ve found 64 to be slower even when you can connect. Then suddenly your connection just dies, especially if you are transferring large amounts of data, it occurs more frequently.

So best not to use 64-66 at all.
Click to expand...

That is so, but there has to be a reason for it that is why I'm hoping an expert reading these forums could give us an answer as to why that should happen.

What about the users that do not know about these unstable IPs, some time ago we asked Ed about it but we never got any real answers from him, hmmmm thats about the time he disapeared from these forums.:rolleyes:

Ideal IPs are with either a 69 or 70 in that position.
 
Do the Basestations map to the ip ranges? Has anyone check this?

So what you guys want is:
1. iburst to fix the problem
2. Something to reconnect until an appropriate ip range is given?

How do you change the ip? Does only powering on and off fix the problem or can you disconnect and reconnect the dial up.
Does the telnet reboot command work?
 
Prevent the UTD to connect to 64-66 range..

Well iBurst has "fixed" this several times in the past, however it reoccurs. When the UTD uses these IP’s your connection either times out or your speed plummets.

I have four UTD’s, two where I am located, one on my desk and one on a mast outside, that one’s IP I can renew via a Netgear router.

The two others are with clients which I / they use to connect via a VPN. Once the remote UTD’s utilise the 64-66 range I am unable to Remote Desktop to reset the connection.

So what I would require is to control the UTD’s remotely, either to reset them, or renew the IP since the clients have minimal IT knowledge and I can’t expect them to go and fiddle with a modem. This won’t be necessary if I could prevent the UTD’s from utilising the 64-66 IP range, or if iBurst could solve the issue. The latter doesn’t seem possible at this stage.

How do you change the ip? - Currently by asking someone in the office to switch the power off and back on. Needless to say not always successful, as it might be allocated another IP in that same range.

Does only powering on and off fix the problem or can you disconnect and reconnect the dial up. - Disconnect & reconnect works; however it has happed that the client disconnects the wrong NIC with disastrous consequences.

Does the telnet reboot command work – I haven’t tried it, concerned that it might damage the router as it is too complex for a basic user to execute.

A solution would be welcomed.
 
Last edited:
The best way around this "64" problem is for iBurst to either fix that IP range or remove it from service altogether since that range serves no usefull purpose the way it is right now.
Maybe talk to Ed and see if they are willing to remove that useless IP range.
 
Well I am on a .64 IP right now and it seems fine. Maby all our talk about it in the last few days got them to fix it again?

Why dont you guys try getting an IP in the .64 range and try it out.
 
No thank you...

Can’t afford to be disconnected! Also as I mentioned before the issue is intermittent and there is no clear indication when the IP64 of death will strike.

Scary, isn’t it, LOL
 
Ja, I have hit bad times with that before.

Once I tried changing my IP and three times in a row I got a dead .64 IP!!

I guess sometimes once it locks onto a IP it like to keep that range for a while?
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X