wvlan_cs/orinoco_cs & linksys wap11 AP
Roger Larsson
roger.larsson at norran.net
Fri Dec 14 08:43:08 EST 2001
On Thursdayen den 13 December 2001 14.25, kiss the sun and walk on air wrote:
> I am writing in reference to the potential problems in the message at
> http://lists.samba.org/pipermail/wireless/2001-May/002499.html
> relating to the linksys wap11 AP.
>
> I have an Intersil PRISM2 card built into my laptop (toshiba tecra
> 8200), and it works fine with either the wvlan_cs or the orinoco_cs
> drivers. I am currently using pcmcia-cs v3.1.29, which has orinoco_cs
> v0.06a / orinoco 0.08a. I also observed the same problems using the kernel
> 2.4.16 PCMCIA support which has orinoco_cs v0.08a.
>
> I move between two Linksys WAP11 APs, one at home and one at
> work. Whenever I reach the other location I must always cycle the
> power on the AP otherwise I get the 44:44:44:44:44:44 for the Access
> Point under iwconfig. This is after a cold boot, I always shut down my
> machine when moving between the office and home.
>
> Here is iwconfig eth0 when I'm at home:
> eth0 IEEE 802.11-DS ESSID:"girl" Nickname:"leela"
> Mode:Managed Frequency:2.432GHz Access Point:
> 00:04:5A:CD:D2:9C
> Bit Rate=11Mb/s Tx-Power=15 dBm Sensitivity:1/3
> Retry limit:4 RTS thr:off Fragment thr:off
> Power Management:off
> Link Quality:39/92 Signal level:-54 dBm Noise level:-93
> dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
Isn't this a situation where you should use
# cardctl scheme home
# cardctl scheme work
To be able to specify different ESSID, etc...
(The scheme name gets passed into wireless.opts)
/RogerL
--
Roger Larsson
Skellefteå
Sweden
More information about the wireless
mailing list