Re: SMC2662W V.3 Problems

Hi Joerg,

Thanks for your help. 

Late last night I got it to work with the following
commands:

iwconfig eth0 key [1] 1234567890ABCDEF1234567890
iwconfig eth0 key [1]
iwconfig eth0 enc on

That last line was not in the documenation page for
iwconfig (as far as I can tell), I gave it a shot
because the man page mentioned 'enc off' at one point
so I guessed that 'enc on' might be valid. I do not
know if the setting the index '[1]' is really needed
for this to work, I will test that later.

All, I have to do now is figure out how to make it
config properly each tome I reboot and I will be all
set.

So for anyone who wants to know this USB device i.e.
SMC2662W V.3 does in fact work with these drivers.

Thanks again.

Richard
--- [email protected] wrote:
> Hi Richard,
> 
> > OK, if I look in dmesg I have the following:
> > 
> > usb.c: USB device 2 (vend/prod 0xd5c/oxa002) is
> not
> > claimed by any active driver.
> > usb.c: registered new driver usbvnetr
> > usb vendor/product=d5c/a002
> > vnet_kernel.c: Reseting Usb Device
> > vnet_kernel.c: Reset completed.
> > Reg Domain
> > usbvnetr: driver 1.01, compiled Jul 12 2003
> 19:39:11
> > (dbg_mask x0)
> > MAC addr 00:04:E2:79:DE:C8 firmware 1.101.2.84
> > divert: allocating divert_blk for eth0
> > Multicast is enabled
> > divert: allocating divert_blk for eth0
> > divert: freeing divert_blk for eth0
> > vnetusba.c: usb eth0 initialized and registered
> > usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq
> 6
> > len 18 ret -6
> > usbdevfs: USBDEVFS_CONTROL failed dev 2 rqt 128 rq
> 6
> > len 18 ret -6
> > ohci1394: pci_module_init failed
> > ip_tables: (C) 2000-2002 Netfilter core team
> > **********************
> > REASSOCIATION RESPONSE
> > **********************
> 
> IMHO you cvan ignore the ".. not claimed by any
> driver" line above.
> The SF driver loads and reports MAC address and
> firmware version.
> 
> > >From iwconfig I get:
> > 
> > eth0     
> > ATMEL RFMD503A  ESSID:"Myrtoum" Nickname:"Myrtoum"
> > Mode:Managed Channel:1 Access Point:
> 00:05:5D:ED:1F:8A
> > Bit Rate:2Gb/s
> > 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
> >
> 
> Your device has found the AP (if the reported BSSID
> is correct).
> 
> > Notice that the key is listed as ten zeros, I have
> > tried inputing in Red Hat config as (this is NOT
> my
> > real key):
> > 1234567890ABCDEF1234567890
> > or
> > 1234567890abcdef1234567890
> > or 
> > 1234-5678-90ab-cdef-1234-5678-90
> > 
> > In iwconfig I have tried with and without s:
> > 
> > In all cases iwconfig reports key:0000-0000-00
> > 
> > The hardware supports the longer key (I have used
> the
> > long key in win2k.
> 
> I haven't used the SF driver for a long time, I'm 
> using the Berlios driver.
> iwconfig support wasn't complete for the SF driver
> in 2002;
> AFAIR using lvnet / xvnet was suggested at that
> time.
> Search the mailing list archives for hints how to
> set the
> key.
> 
> /Jörg
> 
> -- 
> +++ GMX - Mail, Messaging & more  http://www.gmx.net
> +++
> 
> Jetzt ein- oder umsteigen und USB-Speicheruhr als
> Prämie sichern!
> 


__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com