From: Will Keaney <keaneyw@gmail.com>
To: Bob Copeland <me@bobcopeland.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Fwd: Re: Trouble Associating with ath5k on AR5212]
Date: Wed, 08 Apr 2009 13:43:23 -0400 [thread overview]
Message-ID: <49DCE23B.7010400@gmail.com> (raw)
In-Reply-To: <49DCD05B.9050802@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1983 bytes --]
Will Keaney wrote:
> Bob Copeland wrote:
>
>>> I also have to manually set the reg domain to US every time I load the
>>> ath5k module. �I tried configuring wpa_supplicant.conf to do this
>>> itself, but that doesn't seem to work. �It would be nice to have a
>>> module parameter for setting this at load time.
>>>
>>>
>> I may be wrong but I think that only works in wpa_supplicant if you
>> use -Dnl80211 (instead of -Dwext).
>>
>> FWIW in the default world roaming domain you can still connect to most
>> APs. Besides iw/wpa_supplicant, pending patches to ath5k will set the
>> default regdomain automatically based on the value stored in the eeprom.
>>
>>
> Ahh, interesting. I didn't see nl80211 documented in the wpa_supplicant
> example configs or man page. I'll give that a shot.
> I seem to get much better scanning results with the region set properly,
> than on the world roaming domain.
>
I don't know if it's relevant or not, but when using -Dnl80211 I see a
bit of odd behavior:
- wpa_supplicant is able to set the region automatically. Yay!
- scanning produces quite an extensive list of APs, but most of them
don't have SSIDs listed. This isn't in itself too strange, since I know
that there are 2 networks nearby each with several repeaters that do not
broadcast SSID. However, one of them (chmc_guest) is identified in the
scanning output when using -Dwext.
- All of the networks show a signal strength of 0. -Dwext shows varying
signal strengths for each network. Considering that I am unable to
associate with any of them, I have to wonder which driver is producing
spurious output.
I would also like to note that the maximum Tx Power of the card is
significantly different between madwifi and ath5k. In madwifi, it maxes
at 17dBm; in ath5k, it maxes at 27dBm. I don't know if it actually is
using these values, or if one or both drivers are reporting Tx power
incorrectly.
Will
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2009-04-08 17:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 13:38 [Fwd: Re: Trouble Associating with ath5k on AR5212] 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 [this message]
2009-04-17 20:02 ` Will Keaney
-- strict thread matches above, loose matches on Subject: below --
2009-04-03 11:47 Will Keaney
2009-04-03 11:46 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=49DCE23B.7010400@gmail.com \
--to=keaneyw@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.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.