From: Jouni Malinen <j@w1.fi>
To: Ben Greear <greearb@candelatech.com>
Cc: Daniel Halperin <dhalperi@cs.washington.edu>,
Felix Fietkau <nbd@openwrt.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Scanning and channel types.
Date: Wed, 9 Feb 2011 15:22:18 +0200 [thread overview]
Message-ID: <20110209132218.GA6183@jm.kir.nu> (raw)
In-Reply-To: <4D50909B.1020005@candelatech.com>
On Mon, Feb 07, 2011 at 04:38:51PM -0800, Ben Greear wrote:
> On 02/07/2011 03:53 PM, Daniel Halperin wrote:
> >Just as there are G-only APs that don't advertise 1-11 Mbps in their
> >beacons, there are HT-only APs that don't advertise support for 1-11
> >or 6-54 Mbps in their beacons and *only* support MCS rates.
> If anyone knows how to configure such a beast, I'll run some
> tests. Or, if someone else has an AP like this, please let
> me know if you see any problems with these patches.
As of today, the hostap.git snapshot of hostapd allows you to configure
the AP to require HT PHY support from every station trying to associate
with it. This can be configured with require_ht=1. This by itself does
not change the advertised rate sets, but when set, this allows following
configuration to remove all non-MCS rates to be disabled:
ieee80211n=1
require_ht=1
supported_rates=
basic_rates=
I'm not sure whether we currently handle such configuration correctly
everywhere, but at least this will remove the non-MCS rates from
Beacon/Probe Response frames from the AP. It does not prevent the AP
from actually receiving frames at non-MCS rates, so it may still reply
to Probe Request frames even if they are sent without using MCS rates. I
think I can make hostapd not reply to those frames if they do not
contain HT Capabilities IE, but still, you would likely see a response
to a Probe Request with that IE included even if it is sent at 1 Mbps.
Whether the response goes out using MCS in such a case is unknown to me
at this point, though.
--
Jouni Malinen PGP id EFC895FA
next prev parent reply other threads:[~2011-02-09 13:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-06 19:01 Scanning and channel types Ben Greear
2011-02-06 19:42 ` Felix Fietkau
2011-02-06 19:54 ` Ben Greear
2011-02-06 19:59 ` Felix Fietkau
2011-02-06 20:07 ` Ben Greear
2011-02-06 20:23 ` Daniel Halperin
2011-02-06 21:07 ` Ben Greear
2011-02-06 21:09 ` Felix Fietkau
2011-02-07 5:42 ` Daniel Halperin
2011-02-07 18:03 ` Ben Greear
2011-02-07 18:32 ` Daniel Halperin
2011-02-07 20:04 ` Ben Greear
2011-02-07 20:10 ` Daniel Halperin
2011-02-07 21:01 ` Jouni Malinen
2011-02-07 21:02 ` Ben Greear
2011-02-07 23:53 ` Daniel Halperin
2011-02-08 0:38 ` Ben Greear
2011-02-09 13:22 ` Jouni Malinen [this message]
2011-02-07 18:23 ` Ben Greear
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=20110209132218.GA6183@jm.kir.nu \
--to=j@w1.fi \
--cc=dhalperi@cs.washington.edu \
--cc=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=nbd@openwrt.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 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.