Re: (no subject)

Hi Graeme,

> Time for iwconfig
> iwconfig eth1 mode ad-hoc
> iwconfig eth1 channel 6
> iwconfig eth1 essid HOME
> iwconfig eth1 mode managed

you can skip the first line, but it does no harm.


> I also tried the at76c503 driver package and added the card id to
> at76c503-i3861. The debug information was a little mode helpful.
> 
> at76c503.c: wlan0: rx AssocResp bssid 00:90:96:48:5b:11 capa x0001 status
> x0001 
> assoc_id x0000 rates 82848B96
> at76c503.c: wlan0: state 3 -> 6 (JOINING)
> at76c503.c: wlan0: kevent 6 scheduled
> at76c503.c: wlan0: kevent flags=x40
> at76c503.c: wlan0 find_matching_bss: try to match ssid home (686F6D65)
> mode 
> infra wep disabled, start at 1, return -1
> at76c503.c: wlan0: state 6 -> 1 (SCANNING)
> at76c503.c: wlan0: kevent 4 scheduled
> at76c503.c: wlan0: kevent flags=x10
> at76c503.c: wlan0: timeout, state 1
> at76c503.c: wlan0: kevent 5 scheduled
> at76c503.c: wlan0 BSS table:
> at76c503.c: 0.BSS 00:90:96:48:5b:11 channel 6 ssid  (4:00000000) capa
> x0001 
> rates 82 84 8B 96 rssi 33 link 3 noise 0
> at76c503.c: wlan0: state 1 -> 6 (JOINING)
> at76c503.c: wlan0: kevent 6 may have been dropped
> at76c503.c: wlan0: kevent flags=x40
> 
> Si in this case it's finding the AP (00:90:96:48:5b:11) but iwconfig
> output still shows that it's still not found the AP.

You seem to use an old version (< 0.10) of the Berlios driver, 0.10
got a number of bugs fixed (and prints more helpful debug). Please
check http://at76c503a.berlios.de/ for the "Known bugs" - you may
prefer the cvs snapshot.

The AssocResp in the first lines failed (status != 0). Code 1 is
"unspecified
error". Any active MAC filter in the AP?

Please post more of the lines before this happened (preferable
with the 0.10 driver) and your AP's configuration.

/Jörg

-- 
+++ GMX - Mail, Messaging & more  http://www.gmx.net +++

Jetzt ein- oder umsteigen und USB-Speicheruhr als Prämie sichern!