From: Ben Greear <greearb@candelatech.com>
To: Janusz Dziedzic <janusz.dziedzic@tieto.com>
Cc: Adrian Chadd <adrian@freebsd.org>,
Kalle Valo <kvalo@qca.qualcomm.com>,
ath10k <ath10k@lists.infradead.org>
Subject: Re: Trouble connecting to broadcom AC APs?
Date: Fri, 21 Mar 2014 10:41:47 -0700 [thread overview]
Message-ID: <532C79DB.7010505@candelatech.com> (raw)
In-Reply-To: <CALhHN=qYuOY8v__HX3=Y7CeZseC7GA5-epfj+zQXcruG6R2BAA@mail.gmail.com>
On 03/21/2014 12:07 AM, Janusz Dziedzic wrote:
> On 21 March 2014 07:01, Janusz Dziedzic <janusz.dziedzic@tieto.com> wrote:
>> On 20 March 2014 20:23, Ben Greear <greearb@candelatech.com> wrote:
>>> On 03/20/2014 12:17 PM, Adrian Chadd wrote:
>>>> Did the per-rate transmit statistics ever make it into the firmware / driver?
>>>>
>>>> I'd start by looking at what rate(s) it's trying and what the transmit
>>>> completion statistics say. It could be doing something exceedingly
>>>> dumb like transmitting on an invalid rate or stream setup.
>>>>
>>>> Same deal with STBC/LDPC. Try disabling those; see what happens.
>>>
>>> It appears the packets get to the AP, and AP at least tries to
>>> respond.
>>>
>>> If we bring up stations one at a time instead of multiple at once
>>> it works better, and using ddwrt works better than stock firmware
>>> on the AP too.
>>>
>>> Anyone know how well monitor mode works on ath10k? Would be nice
>>> to see what is actually on the air.
>>>
>> With AP firmware, works fine. Could you send airlogs?
>>
> BTW, I have same problem with WRT54G and orginal linksys SW - my home router.
> Problem disappears when will use FW 636 :)
> So, seems AP (389, 467) FW is not the best choice for STA mode.
> I suspect PS problem here - but didn't check this yet ...
Here is another data point...if we make br0 on the AP promisc,
then suddenly it works fine.
(we noticed this because starting tcpdump on br0 also
'fixes' the problem).
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-03-21 17:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 17:01 Trouble connecting to broadcom AC APs? Ben Greear
2014-03-20 6:36 ` Kalle Valo
2014-03-20 15:59 ` Ben Greear
2014-03-20 19:17 ` Adrian Chadd
2014-03-20 19:23 ` Ben Greear
2014-03-20 19:26 ` Adrian Chadd
2014-03-20 23:27 ` Ben Greear
2014-03-20 23:34 ` Adrian Chadd
2014-03-21 6:01 ` Janusz Dziedzic
2014-03-21 7:07 ` Janusz Dziedzic
2014-03-21 17:41 ` Ben Greear [this message]
2014-03-24 19:45 ` Janusz Dziedzic
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=532C79DB.7010505@candelatech.com \
--to=greearb@candelatech.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=janusz.dziedzic@tieto.com \
--cc=kvalo@qca.qualcomm.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.