From: Ben Greear <greearb@candelatech.com>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: ath10k <ath10k@lists.infradead.org>
Subject: Re: Anyone have a working hostapd conf file for AC?
Date: Tue, 25 Feb 2014 16:51:30 -0800 [thread overview]
Message-ID: <530D3A92.9080503@candelatech.com> (raw)
In-Reply-To: <CAHqTa-0xkrJxiHTRJrc5hnA+-nA3AONOpMXFWS+1wcSuPdaFPA@mail.gmail.com>
On 02/25/2014 04:19 PM, Avery Pennarun wrote:
> On Tue, Feb 25, 2014 at 2:00 PM, Ben Greear <greearb@candelatech.com> wrote:
>> Does anyone have a working hostapd config file for
>> ath10k?
>
> Here's mine (20/40/80 MHz all supported):
Thanks...I managed to get something similar working
(open authentication in my case).
I also had to update the regulatory.bin, which enabled
HT80.
But, when using ath10k as AP, with both my firmware and the official
10.1.467 firmware, my stations (always ath10k with my hacked firmware) can associate
but do not receive any DHCP responses.
When I use my ath10k stations against a Netgear AC AP, then they
associate and get DHCP and pass traffic to each other... The reported
rx encoding rate is never reaches much above 200Mbps, though..seems like
it would train up higher.
My ath10k stations also work fine against an ath9k /n AP.
Hard to know what to blame though...
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
next prev parent reply other threads:[~2014-02-26 0:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-25 22:00 Anyone have a working hostapd conf file for AC? Ben Greear
2014-02-26 0:19 ` Avery Pennarun
2014-02-26 0:51 ` Ben Greear [this message]
2014-02-26 1:08 ` Avery Pennarun
2014-02-26 6:23 ` Bartosz Markowski
2014-02-26 17:37 ` Kalle Valo
2014-02-26 17:46 ` Ben Greear
2014-02-26 22:42 ` Ben Greear
2014-02-27 13:42 ` Yeoh Chun-Yeow
2014-02-27 13:53 ` Kalle Valo
2014-02-27 16:51 ` Ben Greear
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=530D3A92.9080503@candelatech.com \
--to=greearb@candelatech.com \
--cc=apenwarr@gmail.com \
--cc=ath10k@lists.infradead.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.