For what it's worth, I too am having the same problem. B-Mode only
fails to work while Mixed will communicate with 802.11b devices.
However, I spoke w/Linksys tech support just yesterday and their
suggestion was to reflash firmware -- give me a break. Apparently
there's no fix for this as of yet and I didn't get the indication from
the support rep that they were even working on a correction for this
problem. Had I not already sent in my UPC from my WRT54G for a Best
Buy rebate, I'd consider buying another 802.11g router - maybe the
D-Link but don't know that you can do that once the box has been
altered.
On Thu, 9 Oct 2003 14:55:53 -0700, "Yves Konigshofer"
<(E-Mail Removed)> wrote:
>Well, I have the same equipment and can tell you that I have the same
>problem regarding B-only mode. I did e-mail Linksys about that, got a
>"thank you for bringing that matter to us" reply, but as far as I know there
>is no solution yet.
>
>Just out of curiosity, have you tried using any other access cards with
>B-only mode? Also, have you tried using WPA-PSK on the WRT54G with the
>WPC11v3? That seems to crash the router when I try it (64/128-bit WEP works
>fine).
>
>-Yves
>
>"Cindy" <(E-Mail Removed)> wrote in message
>news:bNfhb.30846$(E-Mail Removed).. .
>> Am using Linksys WRT54G ver. 1.1 with newest firmware.
>>
>> When I set it in B mode only, Linksys WPC11 ver 3 cards do not connect
>(they
>> are 802.11b). Setting it to Mixed mode allows the WPC11 cards to connect
>> but disconnects non-Linksys cards that are also B mode only.
>>
>> Probably a separate problem (but I don't know): modem seems to "hang"
>> frequently during administration...esp. if done thru wireless connection.
>> Only switching power on and off seems to get it started again.
>>
>> But main problem is that WPC11 ver 3 cards only see router when it is
>> working in Mixed mode, which seems to cut off other cards which only see
>it
>> in B mode. -Tested system by using an 802.11B WAP and all cards worked
>fine
>> in B mode.
>>
>> Is this a known problem and is there a workaround?
>>
>> Thanks
>>
>>
>
|