From: Johannes Berg <johannes@sipsolutions.net>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: wim torfs <wtorfs@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: cfg80211_ops: deauthentication & disassociation
Date: Fri, 30 Jan 2015 10:30:05 +0100 [thread overview]
Message-ID: <1422610205.1919.5.camel@sipsolutions.net> (raw)
In-Reply-To: <CACna6rzXoVdf_7sD4Fio5793kXco5so7=wRisfCcbWt+U2CLKQ@mail.gmail.com> (sfid-20150130_091741_165664_1EE1B66C)
On Fri, 2015-01-30 at 09:17 +0100, Rafał Miłecki wrote:
> > In hostapd, there is a routine that monitors such netlink messages,
> > process_global_event, which eventually parses the CMD_DEL_STATION event in
> > nl80211_del_station_event, where a call is made to drv_event_disassoc if the
> > current device is indeed in AP mode.
> > So eventually, it is the hostapd that triggers the transmission of the
> > disassociation packet.
>
> I indeed missed the way cfg80211_del_sta works and hostapd's event
> handler for this. That explains a lot.
>
> I've checked ath6kl, brcmfmac and mwifiex and they don't seem to call
> cfg80211_del_sta. AFAIU it's because they handle sending
> disassoc/deauth packet on their own (and the don't want e.g. hostapd
> to do this), is that correct?
There are two ways - AP SME in firmware, and AP SME in hostapd.
They work differently - in the former case (firmware) the AP station is
added there and hostapd gets notifications about it.
In the latter case, hostapd adds/removes all the stations.
johannes
prev parent reply other threads:[~2015-01-30 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-29 22:55 cfg80211_ops: deauthentication & disassociation Rafał Miłecki
2015-01-30 6:22 ` wim torfs
2015-01-30 8:17 ` Rafał Miłecki
2015-01-30 9:30 ` Johannes Berg [this message]
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=1422610205.1919.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wtorfs@gmail.com \
--cc=zajec5@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.