From: Oleksij Rempel <linux@rempel-privat.de>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ath9k_htc: station unable to authenticate
Date: Thu, 20 Jun 2013 08:47:03 +0200 [thread overview]
Message-ID: <51C2A567.2010409@rempel-privat.de> (raw)
In-Reply-To: <20130620063925.GA3885@zenon.in.qult.net>
Am 20.06.2013 08:39, schrieb Ignacy Gawedzki:
> On Thu, Jun 20, 2013 at 07:33:30AM +0200, thus spake Oleksij Rempel:
>> Am 19.06.2013 21:33, schrieb Ignacy Gawedzki:
>>> I tested the thing with at least three different APs:
>>>
>>> - Netgear DG834Gv4 with latest firmware.
>>
>> this one is BG with Broadcom BCM4318. Is here original firmware or openwrt?
>
> Original firmware, since OpenWRT doesn't support the ADSL chip.
>
>>> - Netgear DG834Gv5 (don't know which firmware and can't check at this time).
>>
>> this is BG with Conexant CX94610
>>
>>> - hostapd (can't say which version at this time either) with the same
>>> ath9k_htc.
>>
>> this one is actually BGN, did you configured it for N? Can you
>> please provide your hostapd.conf.
>
> I'll manage to get the configuration as soon as possible. It seems the
> association problem went away since I patched the drivers on the AP too, so
> "unpatching" the drivers on the station is not enough to reproduce the
> problem. I'll unpatch the drivers on the AP and re-run the test.
>
>> Do you have problems on all 3 configurations?
>
> On both Netgears for sure. For hostapd I'll confirm that in a little while.
>
>> Can you please test it
>> with some N (HT) capable AP. But please, not with N-draft certified
>> AP.
>
> Is ath9k_htc N-capable?
Yes, if hostapd configured properly.
Question to Corey,
i assume your old AP was supporting only BG networks. And your new one,
which is working fine, supports N?
--
Regards,
Oleksij
WARNING: multiple messages have this Message-ID (diff)
From: Oleksij Rempel <linux@rempel-privat.de>
To: Ignacy Gawedzki <i@lri.fr>,
Johannes Berg <johannes@sipsolutions.net>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
Corey Richardson <corey@octayn.net>
Subject: Re: [ath9k-devel] ath9k_htc: station unable to authenticate
Date: Thu, 20 Jun 2013 08:47:03 +0200 [thread overview]
Message-ID: <51C2A567.2010409@rempel-privat.de> (raw)
In-Reply-To: <20130620063925.GA3885@zenon.in.qult.net>
Am 20.06.2013 08:39, schrieb Ignacy Gawedzki:
> On Thu, Jun 20, 2013 at 07:33:30AM +0200, thus spake Oleksij Rempel:
>> Am 19.06.2013 21:33, schrieb Ignacy Gawedzki:
>>> I tested the thing with at least three different APs:
>>>
>>> - Netgear DG834Gv4 with latest firmware.
>>
>> this one is BG with Broadcom BCM4318. Is here original firmware or openwrt?
>
> Original firmware, since OpenWRT doesn't support the ADSL chip.
>
>>> - Netgear DG834Gv5 (don't know which firmware and can't check at this time).
>>
>> this is BG with Conexant CX94610
>>
>>> - hostapd (can't say which version at this time either) with the same
>>> ath9k_htc.
>>
>> this one is actually BGN, did you configured it for N? Can you
>> please provide your hostapd.conf.
>
> I'll manage to get the configuration as soon as possible. It seems the
> association problem went away since I patched the drivers on the AP too, so
> "unpatching" the drivers on the station is not enough to reproduce the
> problem. I'll unpatch the drivers on the AP and re-run the test.
>
>> Do you have problems on all 3 configurations?
>
> On both Netgears for sure. For hostapd I'll confirm that in a little while.
>
>> Can you please test it
>> with some N (HT) capable AP. But please, not with N-draft certified
>> AP.
>
> Is ath9k_htc N-capable?
Yes, if hostapd configured properly.
Question to Corey,
i assume your old AP was supporting only BG networks. And your new one,
which is working fine, supports N?
--
Regards,
Oleksij
next prev parent reply other threads:[~2013-06-20 6:47 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 11:58 [ath9k-devel] ath9k_htc: station unable to authenticate Ignacy Gawedzki
2013-06-19 13:06 ` Oleksij Rempel
2013-06-19 13:08 ` Berg, Johannes
2013-06-19 13:08 ` Berg, Johannes
2013-06-19 13:38 ` Oleksij Rempel
2013-06-19 13:38 ` Oleksij Rempel
2013-06-19 14:09 ` Ignacy Gawedzki
2013-06-19 14:09 ` Ignacy Gawedzki
2013-06-19 14:11 ` Johannes Berg
2013-06-19 14:11 ` Johannes Berg
2013-06-19 15:08 ` Oleksij Rempel
2013-06-19 15:08 ` Oleksij Rempel
2013-06-19 15:11 ` Corey Richardson
2013-06-19 15:11 ` Corey Richardson
2013-06-19 18:36 ` Oleksij Rempel
2013-06-19 18:36 ` Oleksij Rempel
2013-06-19 18:44 ` Corey Richardson
2013-06-19 18:44 ` Corey Richardson
2013-06-19 17:59 ` Ignacy Gawedzki
2013-06-19 17:59 ` Ignacy Gawedzki
2013-06-19 18:03 ` Ignacy Gawedzki
2013-06-19 18:03 ` Ignacy Gawedzki
2013-06-19 18:37 ` Oleksij Rempel
2013-06-19 18:37 ` Oleksij Rempel
2013-06-19 18:39 ` Ben Greear
2013-06-19 18:39 ` Ben Greear
2013-06-19 18:55 ` Oleksij Rempel
2013-06-19 18:55 ` Oleksij Rempel
2013-06-19 19:36 ` Ignacy Gawedzki
2013-06-19 19:36 ` Ignacy Gawedzki
2013-06-19 19:33 ` Ignacy Gawedzki
2013-06-19 19:33 ` Ignacy Gawedzki
2013-06-20 5:33 ` Oleksij Rempel
2013-06-20 5:33 ` Oleksij Rempel
2013-06-20 6:39 ` Ignacy Gawedzki
2013-06-20 6:39 ` Ignacy Gawedzki
2013-06-20 6:47 ` Oleksij Rempel [this message]
2013-06-20 6:47 ` Oleksij Rempel
2013-06-21 23:34 ` Corey Richardson
2013-06-21 23:34 ` Corey Richardson
2013-06-20 7:09 ` Sujith Manoharan
2013-06-20 8:25 ` Ignacy Gawedzki
2013-06-20 8:28 ` Sujith Manoharan
2013-06-20 10:32 ` Oleksij Rempel
2013-06-20 10:54 ` Sujith Manoharan
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=51C2A567.2010409@rempel-privat.de \
--to=linux@rempel-privat.de \
--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.