Re: signal strength problem for multiple ap's w/ the same essid

[Sven <sr12 duke edu>]

checked out the CVS. sorry to report that: a few restarts of NM produced
2 bars, 43%, and 39%, while everything else says ~80%... the applet
seems not to change the %, ever... unless i restart NM, so it seems. i
guess it's fair to say that it shows the signal quality correctly "most
of the time" ;-) also, locking the card to a certain AP, staying
connected etc, does not change the % either...

Sven

On Mon, 2005-01-31 at 16:04 -0500, Dan Williams wrote:
> On Mon, 2005-01-31 at 15:39 -0500, Sven wrote:
> > related to multiple AP's: i'm just trying out NM again, forcing the card
> > in b-mode with at least 4 ap broadcasting in b-mode, all with the same
> > essid. the signal strengths of the ap's are 
> >     ...:D2 : Quality=7/94  Signal level=-88 dBm  Noise level=-95 dBm
> >     ...:CB : Quality=23/94  Signal level=-72 dBm  Noise level=-95 dBm
> >     ...:27 : Quality=37/94  Signal level=-58 dBm  Noise level=-95 dBm
> >     ...:E1 : Quality=2/94  Signal level=-93 dBm  Noise level=-95 dBm
> > 
> > iwconfig says
> > ath0      IEEE 802.11b  ESSID:"xxx"  Nickname:"laptop.localdomain"
> >           Mode:Managed  Frequency:2.437 GHz  Access Point: ...:27   
> >           Bit Rate:11 Mb/s   Tx-Power:50 dBm   Sensitivity=0/3  
> >           Retry:off   RTS thr:off   Fragment thr:off
> >           Power Management:off
> >           Link Quality=38/94  Signal level=-57 dBm  Noise level=-95 dBm
> >           Rx invalid nwid:913  Rx invalid crypt:0  Rx invalid frag:0
> >           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
> > 
> > and my wireless link monitor says the signal strength is ~80%
> > 
> > but: the NM applet shows only 1 bar, and tells me "Wireless network
> > connection (24%)"
> > 
> > not quite correct, i would say...
> 
> Nope, but that should be fixed already in CVS.  I've quietly ignored
> signal strength for some time and decided to clear it up a bit this
> weekend.  It reported mostly correct signal strength for prism54, airo,
> and atmel drivers though, which just goes to show you what a mess the
> current situation is.
> 
> Dan