From: Larry Finger <Larry.Finger@lwfinger.net>
To: wireless <linux-wireless@vger.kernel.org>
Subject: Deauthentication cycles
Date: Fri, 09 Nov 2007 10:53:52 -0600 [thread overview]
Message-ID: <473490A0.2050403@lwfinger.net> (raw)
In my network using WPA-PSK TKIP with mac80211 and b43, I see several of these cycles per day:
eth1: RX deauthentication from 00:1a:70:46:ba:b1 (reason=7)
eth1: deauthenticated
eth1: authenticate with AP 00:1a:70:46:ba:b1
eth1: RX authentication from 00:1a:70:46:ba:b1 (alg=0 transaction=2 status=0)
eth1: authenticated
eth1: associate with AP 00:1a:70:46:ba:b1
eth1: RX ReassocResp from 00:1a:70:46:ba:b1 (capab=0x431 status=0 aid=1)
eth1: associated
eth1: switched to short barker preamble (BSSID=00:1a:70:46:ba:b1)
In searching through the various 802.11-related header files, the only reason code of 7 that I could
find is
WLAN_REASON_CLASS3_FRAME_FROM_NONASSOC_STA
Is this the correct code? If so, any ideas on why this deauthentication is happening? As can be
seen, it isn't fatal and the system always recovers.
Thanks,
Larry
next reply other threads:[~2007-11-09 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 16:53 Larry Finger [this message]
2007-11-09 20:19 ` Deauthentication cycles Johannes Berg
2007-11-09 22:21 ` Michael Wu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=473490A0.2050403@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).