From: Will Keaney <keaneyw@gmail.com>
To: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: [Fwd: Re: Trouble Associating with ath5k on AR5212]
Date: Fri, 03 Apr 2009 07:46:56 -0400 [thread overview]
Message-ID: <49D5F730.5020205@gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Forwarding back to the list, as I was silly and sent as HTML originally...
-------- Original Message --------
Bob Copeland wrote:
> On Thu, Apr 2, 2009 at 10:12 AM, Will Keaney <keaneyw@gmail.com> wrote:
>
>> Hello,
>> I have been following the wireless-testing branch for a few months,
>> hoping with each revision that my Atheros card would finally work
>> properly with ath5k. �So far, I've been able to scan for and see nearby
>> networks, but I haven't been able to associate to them.
>>
>
> Does limiting wpa_supplicant to only scan the 2 GHz channels help?
>
> e.g. setting "scan_freq=2412 2437 2462" in your wpa_supplicant.conf
> scans 1 6 and 11.
>
Thanks for the suggestion. It appears that my installed version of
wpa_supplicant does not support the scan_freq parameter. A google
search found precisely one example of it being used, in a sample
wpa_supplicant.conf in the epitest git repo.
For what it's worth, I have also tried using iwconfig to associate to
the neighbor's network under ath5k without success. So I don't think
it's related to wpa_supplicant's scanning algorithm.
Will Keaney
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 271 bytes --]
next reply other threads:[~2009-04-03 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 11:46 Will Keaney [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-04-03 11:47 [Fwd: Re: Trouble Associating with ath5k on AR5212] Will Keaney
2009-04-08 13:38 Will Keaney
2009-04-08 14:58 ` Bob Copeland
2009-04-08 15:44 ` Will Keaney
2009-04-08 16:20 ` Bob Copeland
2009-04-08 16:27 ` Will Keaney
2009-04-08 17:43 ` Will Keaney
2009-04-17 20:02 ` Will Keaney
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=49D5F730.5020205@gmail.com \
--to=keaneyw@gmail.com \
--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 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.