All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: j@w1.fi, 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 16:38:51 -0800	[thread overview]
Message-ID: <4D50909B.1020005@candelatech.com> (raw)
In-Reply-To: <AANLkTimybx2pQGsy908ZOKCUndQX55vOQy1aToingWSY@mail.gmail.com>

On 02/07/2011 03:53 PM, Daniel Halperin wrote:
> On Mon, Feb 7, 2011 at 1:02 PM, Ben Greear<greearb@candelatech.com>  wrote:
>> On 02/07/2011 12:10 PM, Daniel Halperin wrote:
>>>
>>> On Mon, Feb 7, 2011 at 12:04 PM, Ben Greear<greearb@candelatech.com>
>>>   wrote:
>>>>>
>>>>> Start on 5 GHZ AP with HT Only set.  Scan.  What rate are probes sent
>>>>> at for 2.4 GHz?
>>>
>>> No HT20 is not the same as HT-Only.  I'm not sure how to set that. Jouni?
>>
>> I found a post from a year or so ago that indicates hostapd doesn't
>> support this type of thing (that could have changed, of course).
>>
>> Do you know of any commercial APs that support the HT-only feature?
>> (And/Or a general strategy for configuring it?)
>>
>>>> On 5Ghz channels, they are sent at 6Mbps
>>>> On channel 3 (2.4Ghz), they are sent at 1Mbps
>>>>
>>>>
>>>> That seem right?
>>>
>>> Yes, for a HT20 but not HT Only AP.
>>
>> Seems to me that the probe-request is to any/all APs,
>> so how could we possibly know that we should send it
>> at 6Mbps v/s 1Mbps until we discovered and communicated
>> with it?
>
> 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.

Well, I don't think my changes would have made this any worse,
so if it worked before, it probably still works.

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.

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2011-02-08  0:39 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 [this message]
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=4D50909B.1020005@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=dhalperi@cs.washington.edu \
    --cc=j@w1.fi \
    --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.