Hi, > > > 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. Ok. The thing I don't understand is why the AP would deauth you. And with that reason code to boot. > Could be the iwlagn driver for 5350 hardware doing something wrong here. > And I also forced it to use sw_crypto. I suppose I could try 5350. But I see no reason it would influence the auth/assoc handshake. > 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. Sorry, not really. A parallel monitor capture might help: iw dev wlan0 interface add moni0 type monitor flags none ip link set moni0 up tcpdump -s 10000 -w /tmp/dump.pkt -i moni0 -p # now leave that running and do whatever as usual johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
