Re: [Madwifi-users] no signal? stumped

[David W. <dav...@gm...>]

[ Please CC replies to me - thankyou! ]

On 4/26/05, Sebastian Weitzel <to...@to...> wrote:

> Your client did not connect to the ap.=20

Yes, seemed like that was the case....

> There are several possibilities, e.g. wrong wep key set or capability mis=
match. You will have to debug
> things with the athdebug and 80211debug tool and the correct debug
> parameters (see list with -?)

Ok, well here's what I've found so far:

Apr 26 19:16:16 medford kernel: ieee80211_recv_mgmt: algorithm 0 seq 2 from=
 00:0
3:2f:1d:3e:eb
Apr 26 19:16:16 medford kernel: open authentication failed (reason 13) for =
00:03
:2f:1d:3e:eb

I asked the admin here, and he says it's a "shared key".  Some more
googling turns up this:

medford:~# iwpriv ath0 authmode 2=20

Now the error messages are different:

Apr 26 19:17:10 medford kernel: ath0: [00:03:2f:1d:3e:eb] received auth rss=
i 50
Apr 26 19:17:10 medford kernel: ieee80211_recv_mgmt: algorithm 42699 seq 4 =
from=20
00:03:2f:1d:3e:eb
Apr 26 19:17:10 medford kernel: ieee80211_recv_mgmt: unsupported auth
algorithm 42699 from 00:03:2f:1d:3e:eb

That seems really odd given that the definitions of the algorithms is like =
so:

#define=09IEEE80211_AUTH_ALG_OPEN=09=090x0000
#define=09IEEE80211_AUTH_ALG_SHARED=090x0001
#define=09IEEE80211_AUTH_ALG_LEAP=09=090x0080

Hrm... will look some more....

Thankyou,
--=20
David N. Welton
 - http://www.dedasys.com/davidw/

Apache, Linux, Tcl Consulting
 - http://www.dedasys.com/