[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: wpa_supplicant and ral(4): RTM_IEEE80211: disassoc (102)
On Sun, Feb 07, 2010 at 10:57:02PM +0100, Torsten Harenberg wrote:
> Dear list,
> sorry for self-replying.
> After setting net.link.ieee80211.vap0.debug = -1 and
> net.link.ieee80211.debug = -1, I got the following lines in syslog.
> Maybe that helps to find the source of the problem. Anybody has some
> experience in interpreting the output?
In the kernel, net80211's state transitions (SCAN -> INIT, ..., INIT
-> INIT) make me wonder, what states is wpa_supplicant in, and what
commands does it send the kernel, at the same time?
FWIW, I have seen APs disassociate clients for several reasons,
including an out-of-order crypto sequence number, or the client's
failure to complete re-keying before the AP timed out (after 200ms,
I do not remember whether you use ral@cardbus, or whether ral uses
hardware crypto, but I have seen drivers do silly things like try to
read/write a crypto register while the Cardbus slot was powered down.
Usually it was harmless.
David Young OJC Technologies
dyoung%ojctech.com@localhost Urbana, IL * (217) 278-3933
Main Index |
Thread Index |