Re: SMC2662W V.3 Problems

> eth0     
> ATMEL RFMD503A  ESSID:"Myrtoum" Nickname:"Myrtoum"
> Mode:Managed Channel:1 Access Point: 00:05:5D:ED:1F:8A
> Bit Rate:2Gb/s

Wow, I wish I had that kind of throughput. :)

> RTS thr=2347 B Fragment thr=2346 B
> Encryption key:0000-0000-00 Encryption mode:restricted
> Encryption mode:open
> Link Quality:100 Signal level:20 Nosie level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
> 
> Notice that the key is listed as ten zeros, I have
> tried inputing in Red Hat config as (this is NOT my
> real key):

[cut]

> In all cases iwconfig reports key:0000-0000-00
> 
> The hardware supports the longer key (I have used the
> long key in win2k)

I had the same problem with WEP on my Compaq IPAQ Wireless USB Adapter
(HNW-200). I bought three of them a month ago from Radio Shack.
(closeout at US $25 a piece.) I run it in ad-hoc mode and offer DHCP
from my home server on it. The Atmelwlandriver worked at first, (after I
edited the config.h) but WEP never worked. I would put the key in, but
it would show only 0's. As soon as I typed "iwconfig eth2 key
blahblahblah" it would kill the link, show a bunch of "invalid crypt"
and "Rx missing frag" packets (literally the number would instantly go
from 0 to 65439645 or something that big), and show the 0's for the
encryption key. After I redid my kernel (for unrelated reasons) the
atmel drivers would refuse to load at all. (claimed it did not recognize
the adapter.)

I eventually just used the Berlios drivers, since they are still
actively developed for the Intersil radios. WEP works most all of the
time. (seems like it freezes sometimes, and I have to change the mode of
the card to managed and then back to ad-hoc so it will work again.) But
once I do that a few times, it will run for days with no problem.

Tom Barcellona