From: Luis R. Rodriguez <lrodriguez@atheros.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] AR9280 Force 5ghz or disable 2.4ghz?
Date: Fri, 26 Mar 2010 19:12:08 -0700 [thread overview]
Message-ID: <20100327021208.GC12311@tux> (raw)
In-Reply-To: <1269655360.13004.6.camel@jm-laptop>
On Fri, Mar 26, 2010 at 07:02:40PM -0700, Jouni Malinen wrote:
> On Fri, 2010-03-26 at 16:16 -0700, Pavel Roskin wrote:
> > I confirm that scan_freq is accepted by the current wpa_supplicant but
> > has no reliable effect. Both ath5k and ath9k connected to an AP on the
> > channel 6 when "scan_freq=2412" was in the configuration file.
>
> scan_freq is not supposed to limit the association to specific channels;
> it is only to limit scan requests made by wpa_supplicant. You may still
> find BSSes on other channels either due to scan requests made by other
> programs or by receiving Beacon/Probe Response frames on another
> channel.
>
> If there is interest for limiting the association to specific channels,
> it should be trivial addition to wpa_supplicant (with nl80211). I don't
> know whether I would fully agree on this being a useful thing for
> general use, but I can understand it at least as a testing tool (which
> people may then misuse for other things ;-).
We could add a new command to disable a channel. That would take
care of custom channel configurations.
Luis
next prev parent reply other threads:[~2010-03-27 2:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-20 21:19 [ath9k-devel] AR9280 Force 5ghz or disable 2.4ghz? Curtis Larsen
2010-03-21 15:02 ` Maximi89
2010-03-21 15:41 ` Jouni Malinen
2010-03-21 16:22 ` Curtis Larsen
2010-03-21 17:28 ` Jouni Malinen
2010-03-22 23:19 ` Curtis Larsen
2010-03-24 5:54 ` Curtis Larsen
2010-03-26 23:16 ` Pavel Roskin
2010-03-27 0:14 ` Curtis Larsen
2010-03-27 2:02 ` Jouni Malinen
2010-03-27 2:12 ` Luis R. Rodriguez [this message]
2010-03-27 5:09 ` Curtis Larsen
2010-03-28 7:08 ` Curtis Larsen
2010-03-30 17:10 ` Curtis Larsen
2010-03-30 21:29 ` Jouni Malinen
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=20100327021208.GC12311@tux \
--to=lrodriguez@atheros.com \
--cc=ath9k-devel@lists.ath9k.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.