From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <j@w1.fi>
Cc: Kalle Valo <Kalle.Valo@nokia.com>,
Li YanBo <dreamfly281@gmail.com>, Ben Gamari <ben@mw0.ath.cx>,
linux-wireless@vger.kernel.org,
Jose Ignacio Naranjo Hernandez <joseignacio.naranjo@gmail.com>,
Michael Wu <flamingice@sourmilk.net>,
Stefano Brivio <stefano.brivio@polimi.it>
Subject: Re: Suspend/Resume support
Date: Mon, 19 Nov 2007 15:44:33 +0100 [thread overview]
Message-ID: <1195483473.8642.7.camel@johannes.berg> (raw)
In-Reply-To: <20071119035943.GJ8672@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
> > mac80211 has a comment that NULL frames are just for PS control
> > operation and otherwise ignored. So no idea.
>
> Please note that this comment in ieee80211_rx_h_sta_process() is only
> after having went through association state validation in
> ieee80211_rx_h_check().
Oh good point.
> However, it looks like the sending of
> deauth/disassoc based on Class 2/3 frames being received in wrong state
> (IEEE 802.11, Clause 5.5) has been broken at some point..
>
> mac80211 is supposed to notify userspace (hostapd) of this and hostapd
> would then reply with disassoc/deauth depending on the current state of
> the STA. The current mac80211 implementation is just silently dropping
> the frames. The way this used to work was by sending the
> ieee80211_msg_sta_not_assoc message with ieee80211_rx_mgmt() in
> ieee80211_rx_h_check().
Yes. This was removed along with the mgmt iface, it needs to be added
back.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2007-11-19 14:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 0:51 Suspend/Resume support Ben Gamari
2007-11-15 3:37 ` Li YanBo
2007-11-16 0:11 ` Johannes Berg
2007-11-16 13:24 ` Kalle Valo
2007-11-16 14:41 ` Johannes Berg
2007-11-19 3:59 ` Jouni Malinen
2007-11-19 14:44 ` Johannes Berg [this message]
2007-11-16 14:49 ` Stefano Brivio
2007-11-19 4:08 ` Jouni Malinen
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=1195483473.8642.7.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=Kalle.Valo@nokia.com \
--cc=ben@mw0.ath.cx \
--cc=dreamfly281@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=j@w1.fi \
--cc=joseignacio.naranjo@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=stefano.brivio@polimi.it \
/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).