From: Ben Greear <greearb@candelatech.com>
To: Daniel Halperin <dhalperi@cs.washington.edu>
Cc: linux-wireless@vger.kernel.org
Subject: Re: hti->control_chan is 15??
Date: Fri, 28 Jan 2011 16:58:28 -0800 [thread overview]
Message-ID: <4D436634.3070506@candelatech.com> (raw)
In-Reply-To: <AANLkTimG05o=y2xGXh0YAmRqbuixifKp7xgmU7sH61Uf@mail.gmail.com>
On 01/28/2011 04:48 PM, Daniel Halperin wrote:
> On Fri, Jan 28, 2011 at 4:43 PM, Ben Greear<greearb@candelatech.com> wrote:
>> My AP is an off-the-shelf Netgear:
>> WNDR3700
>>
>> It's only rate configuration option is '300Mbps', which appears to
>> turn on HT40.
>>
>> It is configured for channel 10 (for the packet capture) and actually
>> passes traffic there. It's just this HT Info thing with (primary-channel ==
>> (real_channel + 4))
>> that seems wrong. Note that when I had the channel set to 11, it was
>> reporting
>> 15 for the primary channel in the HT info.
>>
>> Looks like a bug in that AP to me...but would be nice if there were a way to
>> work around it, in case others have similar issues.
>
> Set it to channel 6, then?
It will still fail the control_chan test and so HT will not be enabled.
That's the symptom I've been chasing all day...just turns out that
the cause, for once, appears to not be my system :)
I'll look into adding a hack to allow HT to be enabled
if the channel is off-by-4.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-01-29 0:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-28 22:39 hti->control_chan is 15?? Ben Greear
2011-01-29 0:21 ` Ben Greear
2011-01-29 0:35 ` Daniel Halperin
2011-01-29 0:43 ` Ben Greear
2011-01-29 0:48 ` Daniel Halperin
2011-01-29 0:58 ` Ben Greear [this message]
2011-01-29 13:34 ` Felix Fietkau
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=4D436634.3070506@candelatech.com \
--to=greearb@candelatech.com \
--cc=dhalperi@cs.washington.edu \
--cc=linux-wireless@vger.kernel.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).