From: Ben Greear <greearb@candelatech.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Mohammed Shafi <shafi.wireless@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: ath9k 9380: All 5Ghz channels flagged as passive-scanning
Date: Mon, 23 May 2011 14:59:21 -0700 [thread overview]
Message-ID: <4DDAD8B9.8090802@candelatech.com> (raw)
In-Reply-To: <BANLkTimDXqa+67=UFY4KS5zwOBrinH_k8g@mail.gmail.com>
On 05/23/2011 02:46 PM, Luis R. Rodriguez wrote:
> On Mon, May 23, 2011 at 2:42 PM, Luis R. Rodriguez<mcgrof@gmail.com> wrote:
>
>> No. You can only do this by trying to take the card out of compliance
>> purposely or unknowingly in software.
>
> Oh and my point was that "regulatory hacks" fit this description.
Ok. I believe you are right in general, but I can't see how enabling
a device to work on a non-scanned channel can break something, if
it is perfectly legal and appropriate for there to be an AP on that
scanned channel. In other words, if I change my Netgear to be on channel
48, scanned it, and then created a VAP on that channel, that is OK with
un-hacked regdomain stuff, but if instead I change regdomain to 0x0
and use channel 48 without re-configuring my Netgear, somehow that
suddenly causes issues?
At any rate, all I really wanted to do was tie-break an off the
shelf AP that appeared to cause ath9k clients to silently be
unable to ARP after a while. I have something that appears functional
now, so back to real work.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2011-05-23 21:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 22:22 ath9k 9380: All 5Ghz channels flagged as passive-scanning Ben Greear
2011-05-23 11:28 ` Mohammed Shafi
2011-05-23 16:54 ` Ben Greear
2011-05-23 18:39 ` Ben Greear
2011-05-23 18:52 ` Ben Greear
2011-05-23 19:26 ` Luis R. Rodriguez
2011-05-23 20:09 ` Ben Greear
2011-05-23 20:25 ` Luis R. Rodriguez
2011-05-23 20:51 ` Ben Greear
2011-05-23 20:59 ` Luis R. Rodriguez
2011-05-23 21:19 ` Ben Greear
2011-05-23 21:28 ` Luis R. Rodriguez
2011-05-23 21:38 ` Ben Greear
2011-05-23 21:42 ` Luis R. Rodriguez
2011-05-23 21:46 ` Luis R. Rodriguez
2011-05-23 21:59 ` Ben Greear [this message]
2011-05-23 22:15 ` Luis R. Rodriguez
2011-05-24 4:48 ` Ben Greear
2011-05-24 11:33 ` Luis R. Rodriguez
2011-05-24 13:00 ` Brian Prodoehl
2011-05-24 13:11 ` Luis R. Rodriguez
2011-05-24 13:18 ` Brian Prodoehl
2011-05-24 21:39 ` Luis R. Rodriguez
2011-05-24 14:06 ` Mohammed Shafi
2011-05-24 14:08 ` Mohammed Shafi
2011-05-24 15:05 ` 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=4DDAD8B9.8090802@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=shafi.wireless@gmail.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 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.