Routing Protocols

kmclellan

Active Member
Joined
Jan 27, 2005
Messages
33
Hi ladies and gents

I think I can explain the up and down behavior of my UTD. It would seem that whatever routing protocol they use with these devices(maybe some sort of RIP?), it advertises the available base stations. It also assigns a cost to these based on number of users or some sort of weighting algorithm. I get this when my UTD is connected and I run a terminal session to see the consol output. Just before a reset happens I get “uplink failed, desired BCH not found during BS scan”. This can be because the BS that looks most favorable is not allowing me to connect to it, or it’s not there. This does happen quite often, so it might have something to with the load on the station. I found this in the Gold Reef City area and Weltevreden park.

If this makes any sense please feel free to elaborate.

Kenny
 

jmn

Senior Member
Joined
Feb 19, 2005
Messages
551
Started noticing the uplink failures as well this past weekend, not before
 

Crash

Senior Member
Joined
Nov 15, 2004
Messages
942
It's contention on the towers guys.
When I was living in RadioKop, I got terrible speeds. Had Northcliff and Roodepoort Tower (Roodepoort is miles away).

Move to Roodepoort and now I get excellent speeds. I think everything comes down to base station contention.
 

GRES

Well-Known Member
Joined
Apr 20, 2005
Messages
284
Uplink Failed - it's mean that tower can't see your modem. Strange - second half of the message means than it's no enough good signal FROM tower. In this case tower signal fall below -100-105dB.
What is your signal lewel?
Uplink Failed message is the reason for Northcliff bad connection.
 

regardtv

Expert Member
Joined
Sep 1, 2003
Messages
1,537
what I find fun currently is that Linden tower does something similar...

I stay connected to if for a while, get uplink failed and then my modem tries to connect to JHB CBD which is >12KM away ... then modem get stuck in Uplink failed loop... even if Linden is then seen the modem does not recover till a full power cycle ... a "modem reboot" is not enough to fix it .... also only a recent problem....
 
Top