From: Ben Greear <greearb@candelatech.com>
To: "hostap@lists.shmoo.com" <hostap@lists.shmoo.com>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: Scanning all 5Ghz channels with AC NIC.
Date: Tue, 25 Mar 2014 08:50:42 -0700 [thread overview]
Message-ID: <5331A5D2.3030004@candelatech.com> (raw)
In-Reply-To: <20140325144255.GA30784@w1.fi>
On 03/25/2014 07:42 AM, Jouni Malinen wrote:
> On Mon, Mar 24, 2014 at 11:10:44AM -0700, Ben Greear wrote:
>> I notice this issue while trying to scan specific channels with
>> an ath10k NIC.
>>
>> If I configure supplicant to use a specific freq list, it will fail:
>>
>> 1395683887.458813: nl80211: Scan frequency 5170 MHz
>> 1395683887.458823: nl80211: Scan frequency 5180 MHz
> ...
>
> You need to be quite careful when using freq_list. wpa_supplicant will
> use exactly what is provided there and if cfg80211 does not like what it
> sees, it will reject this. Apparently duplicate entries would hit that
> and so would channels that the driver does not support.
>
> In general, it is much easier to just do "wpa_cli scan freq=4900-6000"
> if you just want to scan all the enabled 5 GHz channels.
I use the freq_list to effectively disable 2.4Ghz, for instance when trying
to force a station to act like /a only instead of /a/b/g.
Maybe there is a better way? (I don't often use wpa_cli directly,
so that won't help my case...)
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2014-03-25 15:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 18:10 Scanning all 5Ghz channels with AC NIC Ben Greear
2014-03-24 19:33 ` Janusz Dziedzic
2014-03-24 19:47 ` Ben Greear
2014-03-24 20:04 ` Ben Greear
2014-03-24 20:06 ` Janusz Dziedzic
2014-03-25 14:42 ` Jouni Malinen
2014-03-25 15:50 ` Ben Greear [this message]
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=5331A5D2.3030004@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=hostap@lists.shmoo.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.