Search Linux Wireless

Re: Problem with IEEE80211_MONITORING_INTERVAL

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 2009-04-16 at 01:21 +0200, Marcel Holtmann wrote:

> After a long debugging session with Reinette we finally tracked down
> what is going on here. A full scan with this card takes 7-9 seconds and
> that seems to be too long and trigger IEEE80211_MONITORING_INTERVAL
> which then deauthenticates us with the AP (reason=6).

Note to everybody: _Please_ provide the exact output. This text above
makes it sound like we deauth from the AP, when in reality the AP has
deauth'ed us.

Maybe your AP is just buggy and can't handle you going away for more
than a couple of seconds? It _looks_ like it sends you a deauth frame
while you're scanning (please verify using wireshark or similar), we
miss that deauth because we're off the channel, and then when we get
back and start sending data again the AP complains that we're no longer
authenticated.

Sorry, but there's not enough information here to tell what really is
going wrong. The known bug shouldn't be able to cause this behaviour.

johannes

Attachment: signature.asc
Description: This is a digitally signed message part


[Index of Archives]     [Linux Host AP]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Linux Kernel]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux