Richard Perkin <(E-Mail Removed)> wrote:
>(E-Mail Removed) (Floyd L. Davidson) wrote:
>
>> Well, the other side of that is the situation where you have a
>> permanently located client which just happens to be in a fringe
>> area for both the AP and the repeater. Using the same SSID you
>> cannot select which one it connects to
>
>With the facilities of WinXP, that is correct. But most (?) wireless
>card utilities allow explicit selection between access points with
>the same SSID by using the BSSID.
My experience has been that my client hardware can be given the
MAC address of the AP... and it will be totally ignored if
there is another AP with the same SSID and a better signal!
That is with Broadcom based hardware, YMMV of course.
>> and it might well flip
>> back and forth between them with odd results.
>
>I've not seen this in practice. Most (?) wireless card drivers seem
>reluctant to change...
One example I've seen was where an AP and a repeater were both
within range. The client was directly across the road from the
AP, while the repeater was down the road several yards. Usually
the AP would have a 20 dB better signal than the repeater;
however, frequently a vehicle driving on the road between the AP
and the client would result in a path fade, and the client would
switch to the repeater, with a barely but usable signal.
Indeed the client was reluctant to switch... and would remain
associated with the repeater until its signal would also take a
severe enough hit. In the mean time, performance would be
seriously degraded compared to what would have been available
from the AP (the repeater of course would at best have half the
data rate).
In essence, it avoided the momentary hit by switching, which
indeed resulted in avoiding a total loss of signal perhaps, but
also provided noticeably lower performance for a significant
length of time too.
>> If the two had
>> different SSID's the client would be able to chose one or the
>> other.
>
>This is what I do in mixed 802.11g and 802.11b networks - use
>different APs with SSID specific to each. It improves performance,
>even though it would be possible to have a single large Extended
>Service Set.
>
>> (That can be done when a WRT54G is used as a repeater
>> with 3rd party firmware.)
>
>Ah. I didn't know that - many thanks. Is this the Sveasoft firmware,
>or a different variety?
I'm pretty sure I've tried it with both HyperWRT and Sveasoft firmware,
but can only positively recall checking that with Sveasoft.
--
Floyd L. Davidson <http://web.newsguy.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska)
(E-Mail Removed)