From: "Tomas Winkler" <tomasw@gmail.com>
To: "Jouni Malinen" <j@w1.fi>
Cc: "Johannes Berg" <johannes@sipsolutions.net>,
"Ron Rindjunsky" <rindjon@googlemail.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: HT action frame code
Date: Mon, 8 Sep 2008 23:48:34 +0300 [thread overview]
Message-ID: <1ba2fa240809081348n17a3b4c5o4d67e989dfd79030@mail.gmail.com> (raw)
In-Reply-To: <48C5868B.8060103@w1.fi>
On Mon, Sep 8, 2008 at 11:09 PM, Jouni Malinen <j@w1.fi> wrote:
> Johannes Berg wrote:
>>
>> When we're an AP, shouldn't we also in some way honour the block-ack
>> action frames? Or will that be done in hostapd, which then sets up
>> block-ack via some unspecified way?
>
> The current design assumes that hostapd takes care of all management frames,
> so eyes, these would need to go to hostapd for processing and then setup
> back to mac80211 through some new command..
>
Enable BA in AP mode is really trivial. It definitely worked in our AP project.
Tomas
next prev parent reply other threads:[~2008-09-08 20:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 14:22 HT action frame code Johannes Berg
2008-09-08 20:09 ` Jouni Malinen
2008-09-08 20:48 ` Tomas Winkler [this message]
2008-09-09 6:30 ` Johannes Berg
2008-09-09 6:33 ` Johannes Berg
2008-09-09 8:14 ` Tomas Winkler
2008-09-09 8:20 ` Johannes Berg
2008-09-09 8:46 ` Tomas Winkler
2008-09-09 8:52 ` Johannes Berg
2008-09-09 9:41 ` Tomas Winkler
2008-09-09 9:42 ` Johannes Berg
2008-09-09 9:52 ` Tomas Winkler
2008-09-09 9:55 ` Johannes Berg
2008-09-09 10:21 ` Tomas Winkler
2008-09-09 10:25 ` Johannes Berg
2008-09-09 10:27 ` Johannes Berg
2008-09-09 10:53 ` Tomas Winkler
2008-09-09 11:01 ` Johannes Berg
2008-09-09 11:29 ` [RFC] mac80211: make BA session handling independent of STA mode Johannes Berg
2008-09-09 12:28 ` 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=1ba2fa240809081348n17a3b4c5o4d67e989dfd79030@mail.gmail.com \
--to=tomasw@gmail.com \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=rindjon@googlemail.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