Re: Problem with IEEE80211_MONITORING_INTERVAL

[Marcel Holtmann <marcel@holtmann.org>]

Hi Johannes,

> So far so good
> 
> > wlan0: deauthenticated (Reason: 2)
> 
> This is confusing. And it keeps happening:
> 
> > wlan0: associated
> 
> > wlan0: deauthenticated (Reason: 2)
> 
> > wlan0: RX ReassocResp from 00:1f:3f:19:d8:b7 (capab=0x431 status=0 aid=2)
> > wlan0: associated
> 
> > wlan0: deauthenticated (Reason: 2)
> 
> > wlan0: RX ReassocResp from 00:1f:3f:19:d8:b7 (capab=0x431 status=0 aid=2)
> > wlan0: associated
> 
> > wlan0: deauthenticated (Reason: 2)
> 
> > Do you need anything else? I have really no idea what happens here and I
> > like to get it fixed.
> 
> Can you do the kernel log with timing please? It seems strange to get
> "previous authentication is no longer valid" from the AP as a reason
> code while associated.

I can try but I am not home anymore. So no promises. However it keeps
happening in a pretty constant rate. Like every 2-5 seconds interval.

Could be the iwlagn driver for 5350 hardware doing something wrong here.
And I also forced it to use sw_crypto.

Do you have any ideas so far or want me to put some extra debug code in
there. Not sure if I get that kernel up before tomorrow morning.

Regards

Marcel