Re: Problem with TEW-USB WEP ?

Hi Jörg,

at this time I've corrected set parameters for shared secrets + put
corrected wep64 keys
and than join with AP !

After this TEW-USB send/receive data from AP (dmesg debug), but network
don't work.

I setting my ip on wlan0 at 10.0.0.4 and AP is 10.0.0.254, network mask is
the same 255.255.255.0 (setting is like on windows that working!)

If I try to ping 10.0.0.254 never came back, but if I looking dmesg from
wlan0 more data recevived.

dmesg after ping:

 at76c503.c: wlan0 tx  wlen x74 pad x0 rate 1 hdr
0841000000904B0B1AF80002DD30146C00A0C96F0AF00000
 at76c503.c: wlan0 data 00000000000008004500005400004000
 at76c503.c: wlan0 received data packet:
 at76c503.c:  rxhdr: 74 00 03 00 00 0a 08 00
 at76c503.c:  rxhdr: 8a ce e5 d0
 at76c503.c: wlan0 tx  wlen x74 pad x0 rate 1 hdr
0841000000904B0B1AF80002DD30146C00A0C96F0AF00000
 at76c503.c: wlan0 data 00000000000008004500005400004000
 at76c503.c: wlan0 received data packet:
 at76c503.c:  rxhdr: 74 00 02 00 00 06 12 00
 at76c503.c:  rxhdr: c7 f8 f4 d0
 at76c503.c: wlan0 tx  wlen x4e pad x1c rate 1 hdr
0841000000904B0B1AF80002DD30146C00A0C96F0AF00000
 at76c503.c: wlan0 data 00000000000008060001080006040001
 at76c503.c: wlan0 received data packet:
 at76c503.c:  rxhdr: 4e 00 03 00 00 06 11 00
 at76c503.c:  rxhdr: 20 fd 31 d1

On etherner port after AP  there is a PC with ip 10.0.0.7.

I try to ping 10.0.0.7 and looking packet received on PC 10.0.0.7, there is
a corretecd ping frame from 10.0.0.4,
than 10.0.0.7 reply but on 10.0.0.4 not receive ping-reply.

Still, if looking arp on 10.0.0.4 I've see correctly fisical and network
address for 10.0.0.254 and 10.0.0.7 !

My device is labeled TEW-USB (I believe is first USB wireless device from
TRENDWARE) and inside there is:

 AT76C503A uP
 AT29LV010A Flash
 HFA3863A Conv. and Synt.
 HFA3783 Mod./Demod.
 HFA3861B  Baseband proc.
 HFA3983IV Power Ampl.

FCC ID is O6M2000I and, after your request, I'm looking it corresponds to
Bromax BUW-211I !

dmesg with debug=0x104003 is:

 hub.c: new USB device 00:03.2-1, assigned address 4
 usb.c: USB device 4 (vend/prod 0xb3b/0x1612) is not claimed by any active
driver.
 at76c503.c: $Id: at76c503.c,v 1.25 2003/06/01 19:42:28 jal2 Exp $ compiled
Jul  7 2003 17:45:49
 at76c503.c: firmware version 0.84.0 #0
 at76c503.c: device's MAC 00:02:dd:30:14:6c
 at76c503.c: registered wlan0
 at76c503.c: wlan0 params: ssid okuwlan (6F6B75776C616E) mode adhoc wep
disabled key 0 keylen 0 preamble long rts 1536 frag 1536 txrate 4 excl 0
pm_mode 1 pm_period 0
 at76c503.c: wlan0: state 0 -> 1 (SCANNING)

Best regards Luca.

----- Original Message ----- 
From: "Joerg Albert" <[email protected]>
To: <atmel-wlan-usb-ikZNBd7uB5wQUIZIPwn63sWURRETrGNnG9Ur7JDdleE@public.gmane.org>
Sent: Monday, July 07, 2003 10:49 PM
Subject: Re: [Atmel-WLAN-USB] Problem with TEW-USB WEP ?


> Hi Ingegno,
>
> On Mon, 7 Jul 2003, Ingegno di Luca Macciò wrote:
>
> > I've try setting open key on AP and as you pronosticare my TEW-USB link
to
> > bss, but data exchange fail !
> >
> > My surprise is that the same problem as on Windows when setting open key
on
> > AP, only link with Wep off on driver for TEW-USB but data exchange fail
!
> >
> > Win98 version driver for TEW-USB not have setting for open or share key
but
> > only Wep64, Wep128, or Wep OFF and I know from winhelp that key are in
HEX.
>
> Don't get confused:
> WEP 64/128 is the key length used to encrypt data packets but
> "open system" / "shared secret" is the authentication method used to
> authenticate the client to the access point. Sorry if I ever called it
> "shared key" - that's not correct. The only link between both:
> "shared secret" auth. requires a WEP key set and WEP enabled, because it
> uses WEP (the WEP key is used as the shared secret).
>
> If you got the same problem with the windows drivers (device links to the
> AP, but no data exchange), you may have the problem to get the same key
> into the AP and the USB adapter. If keys are in HEX for the Windows driver
> of the USB adapter, maybe there are not for the config program of the AP?
>
> > I believe only problem is inside firmware of my TEW-USB (AT76C503A +
i3861,
> > version is 0.84.0.0 vey old ?)
>
> What kind of adapter is this?? I only know these two:
> - http://www.trendware.com/products/TEW-224UB.htm (RFMD based acc. to
> Jason's table)
> - http://www.trendware.com/products/TEW-204UB.htm (no Atmel chipset, but
> Prism2 acc. to the driver package from TEW's website)
>
> Please post the name and the FCC ID, if avail.
> Seems like yours got its firmware inside a flash, because otherwise the
> driver (v0.10) will load firmware 0.90.0#44 into devices with Intersil
> radios, which is the latest one for them.
>
> Firmware 0.84.0.0 is really rather old, I've never seen it in any device.
>
> Could you please post the syslog from the first lines detecting the
> device, after setting the module parameter debug=0x104003 for at76c503.o,
> e.g. by putting
> options at76c503 debug=0x104003
> into /etc/modules.conf? I just wonder how the initialization looks like
> for a adapter with flash inside.
>
> /Jörg
>
> _______________________________________________
> Atmel-wlan-usb mailing list
> Atmel-wlan-usb-ikZNBd7uB5wQUIZIPwn63sWURRETrGNnG9Ur7JDdleE@public.gmane.org
> https://iprserv.jura.uni-leipzig.de/mailman/listinfo/atmel-wlan-usb
>