From: Johannes Berg <johannes@sipsolutions.net>
To: Nicolas Cavallari <Nicolas.Cavallari@lri.fr>
Cc: Will Hawkins <hawkinsw@opentechinstitute.org>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] mac80211: add support for userspace to handle auth frames on adhoc ifaces
Date: Thu, 14 Jun 2012 13:24:55 +0200 [thread overview]
Message-ID: <1339673095.4461.2.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4FD99A24.3020907@lri.fr>
On Thu, 2012-06-14 at 10:00 +0200, Nicolas Cavallari wrote:
> I just have a question here : when auth frames are not delivered to
> userspace, mac80211 will respond to them, and also uses them to detect
> node reboot. If you register for auth frames, mac80211 will still send
> auth frames as soon as a new station is seen, which might be confusing
> for user space. Is that ok to do this ? Or should userspace have more
> control over how mac80211 sends auth frames ?
Please read the code. If userspace registers for them, mac80211 will
never do anything with the frame.
> There is also another thing to consider if you want to send auth frames
> from userspace, as CMD_FRAME requires a frequency, which in IBSS mode,
> can change anytime without userspace being notified. If you only have to
> answer to received auth frames, this is easier as you can reuse the
> frequency given by nl80211 when receiving the auth frame. But if you
> want to send a auth frame independently, how do you get the frequency to
> use ?
You check the BSS info, that's trivial.
johannes
next prev parent reply other threads:[~2012-06-14 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 15:46 [PATCH] mac80211: add support for userspace to handle auth frames on adhoc ifaces Will Hawkins
2012-06-14 7:13 ` Johannes Berg
2012-06-14 16:45 ` Will Hawkins
2012-06-14 8:00 ` Nicolas Cavallari
2012-06-14 11:24 ` Johannes Berg [this message]
2012-06-14 12:46 ` Nicolas Cavallari
2012-06-14 16:48 ` Will Hawkins
2012-06-14 16:53 ` Johannes Berg
2012-06-14 16:55 ` Will Hawkins
2012-06-14 17:08 ` Johannes Berg
2012-06-14 18:26 ` Will Hawkins
2012-06-14 18:51 ` Johannes Berg
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=1339673095.4461.2.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Nicolas.Cavallari@lri.fr \
--cc=hawkinsw@opentechinstitute.org \
--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).