From: Ben Greear <greearb@candelatech.com>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: Felix Fietkau <nbd@openwrt.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Scanning and channel types.
Date: Mon, 07 Feb 2011 10:03:10 -0800 [thread overview]
Message-ID: <4D5033DE.4070701@candelatech.com> (raw)
In-Reply-To: <AANLkTin=zENpxMQYe65Vxs7oSVqe37Lt3mgiPp=L-jzA@mail.gmail.com>
On 02/06/2011 09:42 PM, Daniel Halperin wrote:
> Right. I think there is a function something like "send_rate_low" that
> sends the lowest entry in the mac80211 enabled rates table for control
> and mgmt packets. If the NIC is associated to an HT Only AP then that
> lowest entry should be HT20 MCS 1, I'd think.
>
> Also, does circumventing "set channel type" code work properly across
> bands? If you start on 5 GHz will it send 6 Mbps probes or 1 Mbps
> probes?
I did some tests with a sniffer set up:
I have 8 STA vifs.
1) AP is setup to run on channel 11, HT40-
Let all associate on channel 11, radio goes to HT40- mode.
Run Scan on operating channel:
Probe request is reported as 1Mbps data rate on ch 11.
2) Scan on all channels:
Probe requests on 2.4Ghz channels are 1Mbps data rate.
Probe requests on 5Ghz channels (channel 40 in this case)
are reported as 6Mbps data rate.
3) Kill AP, no VIFS are associated (radio goes to NO_HT)
Run scan on all channels.
Probe request on channel 40 is 6Mbps data rate.
Please note that with my patches, the channel-type is still set to NO_HT
if we are scanning off the operating channel. Since test 1 appears to
function properly, I think that verifies that we can safely send NO_HT
requests while leaving the radio at HT40-.
Please let me know if this answers your concerns. If you can think of
other combinations I should try, please let me know that as well.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-02-07 18:03 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 [this message]
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
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=4D5033DE.4070701@candelatech.com \
--to=greearb@candelatech.com \
--cc=dhalperi@cs.washington.edu \
--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 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).