From: Johannes Berg <johannes@sipsolutions.net>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Bjoern Czybik <wlfw@gmx.com>, linux-wireless@vger.kernel.org
Subject: Re: Vendor specific data within a beacon frame
Date: Thu, 07 Oct 2010 20:35:22 +0200 [thread overview]
Message-ID: <1286476522.20974.27.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTimzwhBCVKFnx1vhM4A939_kgixEpw5RLTe8JJb0@mail.gmail.com>
On Thu, 2010-10-07 at 11:31 -0700, Luis R. Rodriguez wrote:
> On Thu, Oct 7, 2010 at 11:15 AM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Thu, 2010-10-07 at 11:11 -0700, Luis R. Rodriguez wrote:
> >
> > Let me quote what you wrote, but just partially:
> >
> >> This can be done from userspace. This is from nl80211.h:
> >
> >> * Note: This command has been removed and it is only reserved at this
> >> * point to avoid re-using existing command number. The functionality this
> >> * command was planned for has been provided with cleaner design with the
> >> * option to specify additional IEs in NL80211_CMD_TRIGGER_SCAN,
> >> * NL80211_CMD_AUTHENTICATE, NL80211_CMD_ASSOCIATE,
> >> * NL80211_CMD_DEAUTHENTICATE, and NL80211_CMD_DISASSOCIATE.
> >
> > :P
>
> Yeah just noticed *after* I pasted it and sent it. Does hostapd use
> this currently?
No, hostapd transmits frames via injection and the data it puts into the
beacon is conveyed with the beacon cmd -- it has never used this
command.
Really, what the OP is looking for is the annotated hostapd
configuration file or the hostapd source code -- he should be able to
figure that out for himself.
johannes
next prev parent reply other threads:[~2010-10-07 18:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-07 9:31 Vendor specific data within a beacon frame Bjoern Czybik
2010-10-07 18:11 ` Luis R. Rodriguez
2010-10-07 18:15 ` Johannes Berg
2010-10-07 18:31 ` Luis R. Rodriguez
2010-10-07 18:35 ` Johannes Berg [this message]
2010-10-08 10:50 ` Bjoern Czybik
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=1286476522.20974.27.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=wlfw@gmx.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 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).